Re: Why not install pgstattuple by default?

Christopher Browne <cbbrowne@gmail.com>

From: Christopher Browne <cbbrowne@gmail.com>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Andrew Dunstan <andrew@dunslane.net>, Euler Taveira de Oliveira <euler@timbira.com>, Josh Berkus <josh.berkus@pgexperts.com>, Greg Smith <greg@2ndquadrant.com>, postgres hackers <pgsql-hackers@postgresql.org>, Magnus Hagander <magnus@hagander.net>
Date: 2011-05-08T14:56:53Z
Lists: pgsql-hackers
My example is of doing "self-discovery" to see if all needful database
components seem to be properly installed.

E.g. - the app needs pgcrypto, intarray, and a custom data type.  The
install script can consequently inform the production folk either "looks
good", or, alternately, "seems problematic!"

Actually, I haven't coded a sample of the "look for custom SPI & types"
part, but it's a natural extension of what I have.

Of course, it only provides a legitimate test when run on the database
server, which isn't always how production folk want to do it, but that's
part of a different argument...