Skip site navigation (1) Skip section navigation (2)

Re: machine-readable pg_controldata?

From: Bruce Momjian <bruce(at)momjian(dot)us>
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>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: machine-readable pg_controldata?
Date: 2010-03-07 01:59:39
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane wrote:
> (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.)

pg_migrator reads/parses the output of pg_controldata for cluster
compatibility checking and for setting counters.

  Bruce Momjian  <bruce(at)momjian(dot)us>

  PG East:

In response to

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2010-03-07 15:00:08
Subject: Re: Explicit psqlrc
Previous:From: Tom LaneDate: 2010-03-06 23:13:31
Subject: Re: Repetition of warning message while REVOKE

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group