From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: machine-readable pg_controldata? |
Date: | 2010-03-09 15:18:03 |
Message-ID: | 60489dd7d8ec786ec53e457addd83853@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
> (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 mostly use it to check on the progress of a PITR slave: just curious,
is there a better/preferred way to get that information?
- --
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 201003091016
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAkuWZnAACgkQvJuQZxSWSsiqWgCglhHZ/awR5lSkjPG+yzd05ulz
X6AAn0uvraweuz8pG15OybCyMzgfH3XX
=QI2N
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2010-03-09 16:55:34 | Re: patch (for 9.1) string functions |
Previous Message | Pavel Stehule | 2010-03-09 14:30:58 | patch (for 9.1) string functions |