-----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 g...@turnstep.com PGP Key: 0x14964AC8 201003091016 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAkuWZnAACgkQvJuQZxSWSsiqWgCglhHZ/awR5lSkjPG+yzd05ulz X6AAn0uvraweuz8pG15OybCyMzgfH3XX =QI2N -----END PGP SIGNATURE----- -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
