Re: pg_controldata gobbledygook

From: Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_controldata gobbledygook
Date: 2013-04-26 04:25:40
Message-ID: CAFcNs+qQ7AgLgAyziOHnwRwd68VDn7YQwaGKsRV1GrK7Mu=V9w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 26, 2013 at 12:22 AM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:

> On Thu, Apr 25, 2013 at 8:07 PM, Peter Eisentraut <peter_e(at)gmx(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-04-26 04:34:54 Re: pg_controldata gobbledygook
Previous Message Alvaro Herrera 2013-04-26 04:21:58 Re: pg_controldata gobbledygook