Re: Turning recovery.conf into GUCs

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>, Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>, Alex Shulgin <ash(at)commandprompt(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Jaime Casanova <jaime(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Turning recovery.conf into GUCs
Date: 2015-01-07 23:41:57
Message-ID: 54ADC445.1030709@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 01/07/2015 02:31 PM, Peter Eisentraut wrote:
> On 1/6/15 7:33 PM, Josh Berkus wrote:
>> D. Wierd name: for those doing only replication, not PITR,
>> "recovery.conf" is completely baffling.
>
> I don't disagree, but "standby.enabled" or whatever isn't any better,
> for the inverse reason.

Yeah. Like I said, I posted a list of bugs and features so that we can
test your solution and the pg.conf merger to see how much they actually
improve things.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2015-01-08 00:13:45 empty select list allowed when using function as table
Previous Message Peter Geoghegan 2015-01-07 23:34:08 Re: INSERT ... ON CONFLICT UPDATE and RLS