Re: unite recovery.conf and postgresql.conf

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Tatsuo Ishii <ishii@postgresql.org>, "josh@agliodbs.com" <josh@agliodbs.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2011-09-24T17:49:05Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Restructure error handling in reading of postgresql.conf.
- d56b3afc0376 9.2.0 cited

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 really editing 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