Re: [PATCHES] Bitmapscan changes

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Hannu Krosing <hannu(at)skype(dot)net>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] Bitmapscan changes
Date: 2007-03-14 16:26:44
Message-ID: 20070314162644.GI11837@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Joshua D. Drake wrote:

> Allow the community to drive the inclusion by making it as easy as
> possible to allow a proactive argument to take place by the people
> actually using the product.

This seems to be a rather poor decision making process: "Are the users
happy with the new feature? If so, then apply the patch." It leads to
unmanageable code.

Which is why we don't do things that way. The code must fit within the
general architecture before application -- particularly if it's an
internal API change. That's what the review process is for.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Timothy J. Kordas 2007-03-14 16:32:46 hash join hashtable size and work_mem
Previous Message Csaba Nagy 2007-03-14 16:01:49 Re: My honours project - databases using dynamically attached entity-properties

Browse pgsql-patches by date

  From Date Subject
Next Message Joshua D. Drake 2007-03-14 16:43:38 Re: [PATCHES] Bitmapscan changes
Previous Message Stefan Huehner 2007-03-14 16:26:27 Code-Cleanup: char* -> const char*