Re: Postgresql Materialized views

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Sean Utt" <sean(at)strateja(dot)com>
Cc: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Postgresql Materialized views
Date: 2008-01-14 02:18:15
Message-ID: 17343.1200277095@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Sean Utt" <sean(at)strateja(dot)com> writes:
> My point is simply this: The lack of a clear formal process for feature
> requests leads to this degradation in the conversation.

Two comments:

1) The existing informal process has served us very well for more than
ten years now. I'm disinclined to consider replacing it, because that
would risk altering the community's dynamics for the worse.

2) In the end, this is an open source *community*; no amount of formal
feature requesting will have any material impact on what actually gets
implemented, because there isn't any central control. 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.

In short: we haven't got a "road map" and we like it that way.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2008-01-14 02:23:54 Re: Distinguishing autovacuum activity in pg_stat_activity
Previous Message Andrew Dunstan 2008-01-14 01:46:31 Re: Postgresql Materialized views