Re: 8.4 release planning
Joshua Brindle <method@manicmethod.com>
From: Joshua Brindle <method@manicmethod.com>
To: Devrim GÜNDÜZ <devrim@gunduz.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Ron Mayer <rm_pg@cheapcomplexdevices.com>, Stephen Frost <sfrost@snowman.net>, Gregory Stark <stark@enterprisedb.com>, Robert Haas <robertmhaas@gmail.com>, Simon Riggs <simon@2ndquadrant.com>, Josh Berkus <josh@agliodbs.com>, "Joshua D. Drake" <jd@commandprompt.com>, Merlin Moncure <mmoncure@gmail.com>, "Jonah H. Harris" <jonah.harris@gmail.com>, Bruce Momjian <bruce@momjian.us>, Bernd Helmle <mailings@oopsware.de>, Peter Eisentraut <peter_e@gmx.net>, pgsql-hackers@postgresql.org
Date: 2009-01-27T21:27:29Z
Lists: pgsql-hackers
Devrim GÜNDÜZ wrote: > On Tue, 2009-01-27 at 15:03 -0500, Tom Lane wrote: >> With my other hat on (the red one) what I'm concerned about is whether >> this patch will ever produce a feature that I could turn on in the >> standard Red Hat/Fedora build of Postgres. > > FWIW, as you know, sepostgresql is already included in Fedora. You can > continue shipping it as a seperate RPM set. That is non-ideal. Getting the capability in to the standard database shipped with RHEL is very important to me and my customers. Since you can turn this off with GUC I don't see why it makes sense to ship 2 databases (nevermind the maintenance issues)