From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Changing recovery.conf parameters into GUCs |
Date: | 2013-07-05 18:49:31 |
Message-ID: | 51D7153B.8050804@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert, Simon, All,
On 04/01/2013 04:51 AM, Robert Haas wrote:> On Thu, Mar 28, 2013 at
11:48 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> a) recovery parameters are made into GUCs (for which we have a patch
>> from Fujii)
>> b) all processes automatically read recovery.conf as the last step in
>> reading configuration files, if it exists, even if data_directory
>> parameter is in use (attached patch)
>> c) we trigger archive recovery by the presence of either
>> recovery.conf or recovery.trigger in the data directory. At the end,
>> we rename to recovery.done just as we do now. This means that any
>> parameters put into recovery.conf will not be re-read when we SIGHUP
>> after end of recovery. Note that recovery.trigger will NOT be read for
>> parameters and is assumed to be zero-length.
>> (minor patch required)
>
> I still prefer Greg Smith's proposal.
>
> http://www.postgresql.org/message-id/4EE91248.8010505@2ndQuadrant.com
So, this seems to still be stalled. Is there a way forward on this
which won't cause us to wait *another* version before we have working
replication GUCs?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2013-07-05 19:04:19 | Re: [PATCH] Add transforms feature |
Previous Message | Tom Lane | 2013-07-05 18:47:06 | Preventing tuple-table leakage in plpgsql |