On Thu, Apr 7, 2011 at 6:31 PM, Josh Berkus wrote:
>> You had better start by getting a clear statement from Pavel as to
>> whether he wishes to release the code in that repository under the
>> PostgreSQL license. I am not sure that he ever formally submitted it.
>
> I don't think it's reasonable
> You had better start by getting a clear statement from Pavel as to
> whether he wishes to release the code in that repository under the
> PostgreSQL license. I am not sure that he ever formally submitted it.
I don't think it's reasonable for a student to do that. That really
needs to be up to
On Thu, Apr 7, 2011 at 4:49 PM, AAMIR KHAN wrote:
> As you people think and may be possible that complete implementation of
> Eager MVs cannot be completed in summer. So maybe i can pick up the work
> left to be done in snapshot MVs. I have cloned the repository of pavel baros
> from https://githu
As you people think and may be possible that complete implementation of
Eager MVs cannot be completed in summer. So maybe i can pick up the work
left to be done in snapshot MVs. I have cloned the repository of pavel baros
from https://github.com/pbaros/postgres.git and i will be looking to find
wha
On 03/31/2011 04:38 PM, AAMIR KHAN wrote:
I would like to implement eager materialized view.An eager
materialized view will be updated whenever the view changes. This is
done with a system of triggers on all of the underlying tables.
Last summer someone worked on snapshot materialized views.
Title: Implementation of Eager Materialized views in postgres
Name of Proposer & Email : Aamir Khan & ak4u2...@gmail.com
Synopsis:
I would like to implement eager materialized view.An eager materialized view
will be updated whenever the view changes. This is done with a system of
triggers on a
