Re: Turning recovery.conf into GUCs - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Turning recovery.conf into GUCs
Date
Msg-id 54AF17BF.9020903@agliodbs.com
Whole thread Raw
In response to Re: Turning recovery.conf into GUCs  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On 01/08/2015 12:57 PM, Peter Eisentraut wrote:
>> > c) Infrastructure for changing settings effective during recovery. Right
>> >    now we'd have to rebuild a lot of guc infrasturcture to allow
>> >    that. It'd not be that hard to allow changing parameters like
>> >    restore_command, primary_conninfo, recovery_target_* et al. That's
>> >    for sure not the same commit, but once the infrastructure is in those
>> >    won't be too hard.
> Right, if that worked, then it would be a real win.  But this discussion
> is about right now, and the perspective of the user.

That's rather a catch-22, isn't it?

Last I checked, it was our policy to try to get smaller, more discrete
patches rather than patches which try to change everything at once.

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



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: PATCH: decreasing memory needlessly consumed by array_agg
Next
From: Stephen Frost
Date:
Subject: Re: INSERT ... ON CONFLICT UPDATE and RLS