Re: unite recovery.conf and postgresql.conf

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

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

To: Magnus Hagander <magnus@hagander.net>

Cc: Fujii Masao <masao.fujii@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2011-09-09T14:05:08Z

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

Magnus Hagander <magnus@hagander.net> writes:
> I have to wonder though, if it wouldn't be less confusing to just get
> rid of recovery.conf and use a *different* file for this. Just to make
> it clear it's not a config file, but just a boolean exists/notexists
> state.

+1.  If it's not a configuration file anymore, it shouldn't be called
one.

			regards, tom lane