Re: pg_control_recovery() return value when not in recovery

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Joe Conway <mail(at)joeconway(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_control_recovery() return value when not in recovery
Date: 2017-10-14 18:04:17
Message-ID: 23747.1508004257@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Fri, Oct 13, 2017 at 7:31 PM, Joe Conway <mail(at)joeconway(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2017-10-14 18:14:19 PATCH: enabling parallel execution for cursors explicitly (experimental)
Previous Message Robert Haas 2017-10-14 17:58:01 Re: [PATCH] pageinspect function to decode infomasks