| From: | Christopher Browne <cbbrowne(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, Josh Berkus <josh(dot)berkus(at)pgexperts(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, postgres hackers <pgsql-hackers(at)postgresql(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net> |
| Subject: | Re: Why not install pgstattuple by default? |
| Date: | 2011-05-08 14:56:53 |
| Message-ID: | BANLkTi=PTO8yBCdZDt+Bb93Ebu4D7jqTtw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yves Weißig | 2011-05-08 15:18:09 | could not write block & xlog flush request 3FD/0 is not satisfied |
| Previous Message | lee Richard | 2011-05-08 13:31:26 | Re: Questions about the internal of fastpath function call |