From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com> |
Cc: | 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Sean Utt <sean(at)strateja(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Postgresql Materialized views |
Date: | 2008-01-14 14:38:52 |
Message-ID: | 478B73FC.5090900@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Roberts, Jon wrote:
>> What gets
>> implemented is whatever individual contributors choose to work on,
>> either because they find it interesting or (in some cases) because
>> someone pays them to do something specific. Certainly, some
>> contributors pay attention to what's being requested, but I see no
>> reason to think that increasing the level of formality will help them.
>>
>
> What happens when a person adds a feature or changes the architecture of the
> database that is perceived by some as incorrect or going in the wrong
> direction?
>
>
>
If that's the general perception it doesn't get added to our source
tree. It's very rare that it gets to anything like as formal as a vote.
To avoid the possibility of people spending lots of time doing work
which is ultimately not adopted, we strongly discourage ivory tower
development. For major features especially, developers are encouraged to
discuss early and often.
But that's a different issue from which items people work on, which is
very much a matter of individual choice, or at least something the
community has little control over.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2008-01-14 14:47:23 | Re: Postgresql Materialized views |
Previous Message | Roberts, Jon | 2008-01-14 14:30:53 | Re: Postgresql Materialized views |