Skip site navigation (1) Skip section navigation (2)

Re: unite recovery.conf and postgresql.conf

From: Greg Stark <stark(at)mit(dot)edu>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: unite recovery.conf and postgresql.conf
Date: 2011-09-09 23:07:28
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Fri, Sep 9, 2011 at 6:40 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> I'm in favor of this.  People are sufficiently confused by the existing
> behavior that we're not going to confuse them further by changing it.

Fwiw as someone who *was* confused previously, it now makes perfect
sense to me. "We have postgres.conf which always applies and then
recovery.conf which can have all the same options but they only apply
during recover". That's much clearer than "we have two configuration
files with two disjoint sets of options and good luck remembering
which options belong in which file". And it still serves a useful
purpose if you have options like recovery_target that you only want to
apply during recovery and then plan to remove.


In response to


pgsql-hackers by date

Next:From: Greg StarkDate: 2011-09-09 23:35:20
Subject: Re: fsyncing data to disk
Previous:From: Bruce MomjianDate: 2011-09-09 23:06:49
Subject: Re: Patch to improve reliability of postgresql on linux nfs

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group