Re: pg_controldata gobbledygook - Mailing list pgsql-hackers

From Fabrízio de Royes Mello
Subject Re: pg_controldata gobbledygook
Date
Msg-id CAFcNs+qQ7AgLgAyziOHnwRwd68VDn7YQwaGKsRV1GrK7Mu=V9w@mail.gmail.com
Whole thread Raw
In response to Re: pg_controldata gobbledygook  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers

On Fri, Apr 26, 2013 at 12:22 AM, Peter Geoghegan <pg@heroku.com> wrote:
On Thu, Apr 25, 2013 at 8:07 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
> Comments?

+1 from me.

I don't think that these particular changes would break WAL-E,
Heroku's continuous archiving tool, which has a class called
PgControlDataParser. However, it's possible to imagine someone being
affected in a similar way. So I'd be sure to document it clearly, and
to perhaps preserve the old label names to avoid breaking scripts.


Why don't we add options to pg_controldata outputs the info in other several formats like json, yaml, xml or another one?

Best regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pg_controldata gobbledygook
Next
From: Tom Lane
Date:
Subject: Re: pg_controldata gobbledygook