Re: machine-readable pg_controldata? - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: machine-readable pg_controldata?
Date
Msg-id 9837222c1003041354v19e7b451xd823e4a8a7489d@mail.gmail.com
Whole thread Raw
In response to machine-readable pg_controldata?  (Josh Berkus <josh@agliodbs.com>)
Responses Re: machine-readable pg_controldata?
Re: machine-readable pg_controldata?
List pgsql-hackers
2010/3/4 Josh Berkus <josh@agliodbs.com>:
> All,
>
> Currently, the only way for admin scripts to get individual data items
> out of pg_controldata (such as the next XID or the catalog version) is
> via grep and regex. Given that people are going to be relying on some of
> this data for replication admin in the future, it seems past time to
> have a form of pg_controldata which either outputs machine-readable text
> (XML or JSON), or (my preference) takes options to output just the
> invididual items, e.g.

Huh? It's fixed with, you don't need regexps for that. Just split the
string apart.

Taking options for single fields might have a better usecase, of course :-)


> pg_controldata --catalog_version
>
> Even better would be the ability to get everything which is in
> pg_controldata currently as part of a system view in a running
> PostgreSQL; I can get most of them, but certainly not all.

+1 for having all the information available from inside the backend,
if that's technically possible (which I assume it should be)

-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: machine-readable pg_controldata?
Next
From: Magnus Hagander
Date:
Subject: Explicit psqlrc