| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: machine-readable pg_controldata? |
| Date: | 2010-03-05 23:03:39 |
| Message-ID: | 4B918DCB.6040400@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> (FWIW, my recollection of the original design intention for
> pg_controldata was that it was meant as a troubleshooting tool if the
> database wouldn't start up. I'm somewhat bemused to hear that people
> are trying to use it as part of production scripts. It wasn't meant to
> produce machine-readable output, much less to give values that you could
> rely on with respect to a running server.)
I'll have a more detailed list when I've gotten further with testing HS/SR.
--Josh Berkus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2010-03-06 09:05:17 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
| Previous Message | Kevin Flanagan | 2010-03-05 22:29:17 | Re: Visual Studio 2005, C-language function - avoiding hacks? |