Re: pg_control_recovery() return value when not in recovery

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: 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 17:45:22
Message-ID: CA+TgmoattZpPiuV=wumLPB4+XVDfveT8DT8U7Mamt0=t=sS3Dg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-10-14 17:48:20 Re: Extended statistics is not working on Vars hidden under a RelabelType
Previous Message Pavel Stehule 2017-10-14 16:27:50 Re: fresh regression - regproc result contains unwanted schema