Re: unite recovery.conf and postgresql.conf

Peter Eisentraut <peter_e@gmx.net>

From: Peter Eisentraut <peter_e@gmx.net>

To: Fujii Masao <masao.fujii@gmail.com>

Cc: Simon Riggs <simon@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, Magnus Hagander <magnus@hagander.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2011-09-13T13:51:07Z

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 tis, 2011-09-13 at 14:46 +0900, Fujii Masao wrote:
> Are you still thinking the backward-compatibility (i.e., the
> capability to specify recovery parameters in recovery.conf) is
> required? 

I think parameters related to a particular recovery, e.g.,
recovery_target_time, fit better into a recovery.conf that is renamed
after the recovery is complete.  That was the original idea, after all.

Everything that is a permanent setting across multiple recovery
attempts, and anything related to replication, better fits elsewhere.