Re: Why not install pgstattuple by default?
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Christopher Browne <cbbrowne@gmail.com>, Magnus Hagander <magnus@hagander.net>, Euler Taveira de Oliveira <euler@timbira.com>, postgres hackers <pgsql-hackers@postgresql.org>
Date: 2011-05-06T22:19:21Z
Lists: pgsql-hackers
On Fri, May 6, 2011 at 5:58 PM, Josh Berkus <josh@agliodbs.com> wrote: > Yeah, I wasn't thinking of including all of contrib. There's a lot of > reasons not to do that. Slightly off-topic, but I really think we would benefit from trying to divide up contrib. Right now it's a mixture of (a) debugging and instrumentation tools (e.g. pgstattuple, pageinspect, pgrowlocks, pg_freespacemap, pg_buffercache), (b) server functionality that is generally useful but considered worth including in core (e.g. hstore, citext, pg_trgm), (c) deprecated modules that we keep around mostly for hysterical reasons (tsearch2, xml2, intagg), and (d) examples and regression test support (dummy_seclabel, spi, start-scripts). I think it would make things a lot easier for both packagers and actual users if we separated these things into different directories, e.g.: debugging and instrumentation tools -> src/debug server functionality -> contrib server functionality (deprecated) -> contrib/deprecated examples & regression test suport -> src/test/examples -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company