Re: unite recovery.conf and postgresql.conf

Andrew Dunstan <andrew@dunslane.net>

From: Andrew Dunstan <andrew@dunslane.net>

To: Joshua Berkus <josh@agliodbs.com>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Tatsuo Ishii <ishii@postgresql.org>, pgsql-hackers@postgresql.org, Robert Haas <robertmhaas@gmail.com>

Date: 2011-09-25T19:37:21Z

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 09/25/2011 02:39 PM, Joshua Berkus wrote:
>> There might be a use case for a separate directive include_if_exists,
>> or some such name.  But I think the user should have to tell us very
>> clearly that it's okay for the file to not be found.
> Better to go back to include_directory, then.
>
>

I rather like Tom's suggestion of include_if_exists.

There might be a case for include_directory, but I think that needs to 
be made separately.

cheers

andrew