Re: [HACKERS] pg_control_recovery() return value when not in recovery - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] pg_control_recovery() return value when not in recovery
Date
Msg-id 23747.1508004257@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] pg_control_recovery() return value when not in recovery  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, Oct 13, 2017 at 7:31 PM, Joe Conway <mail@joeconway.com> wrote:
>> Sorry for the slow response, but thinking back on this now, the idea of
>> these functions, in my mind at least, was to provide as close to the
>> same output as possible to what pg_controldata outputs.

> I think that's a good goal.

>> So if we make a change here, do we also change pg_controldata?

> I think it would make more sense to leave both as they are and
> consider writing more documentation.

+1.  Changing already-shipped behavior seems more disruptive than
this is worth.
        regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] [PATCH] pageinspect function to decode infomasks
Next
From: Tomas Vondra
Date:
Subject: [HACKERS] PATCH: enabling parallel execution for cursors explicitly(experimental)