Re: unite recovery.conf and postgresql.conf - Mailing list pgsql-hackers

From Robert Haas
Subject Re: unite recovery.conf and postgresql.conf
Date
Msg-id F8473C8B-6534-458F-8866-770A13C1CE9A@gmail.com
Whole thread Raw
In response to Re: unite recovery.conf and postgresql.conf  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: unite recovery.conf and postgresql.conf
List pgsql-hackers
On Sep 24, 2011, at 1:04 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I don't exactly buy this argument.  If postgresql.conf is hard to
> machine-edit, why is recovery.conf any easier?

Because you generally just write a brand-new file, without worrying about preserving existing settings. You aren't
reallyediting at all, just writing. 

>
>> What if we modified pg_ctl to allow passing configuration parameters
>> through to postmaster,
>
> You mean like pg_ctl -o?

Oh, cool. Yes, like that.

...Robert

pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs)
Next
From: Jeff Janes
Date:
Subject: Re: [PATCH] Log crashed backend's query (activity string)