Re: unite recovery.conf and postgresql.conf

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Joshua Berkus <josh(at)agliodbs(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: unite recovery.conf and postgresql.conf
Date: 2011-09-25 19:37:21
Message-ID: 4E7F82F1.8070903@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-09-25 20:00:09 Re: BUG #6218: TRAP: FailedAssertion( "!(owner->nsnapshots == 0)", File: "resowner.c", Line: 365)
Previous Message Kohei KaiGai 2011-09-25 19:33:22 Re: [v9.2] "database" object class of contrib/sepgsql