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

Re: unite recovery.conf and postgresql.conf

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joshua Berkus <josh(at)agliodbs(dot)com>
Cc: 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 18:05:29
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Joshua Berkus <josh(at)agliodbs(dot)com> writes:
> What happens currently if we have an \include in postgresql.conf for a file which doesn't exist?  Is it ignored, or do we error out?

It's an error, and I think changing that would be a really bad idea.

> If it could just be ignored, maybe with a note in the logs, then we could be a lot more flexible.

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.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Jeff DavisDate: 2011-09-25 18:30:54
Subject: Re: Range Types - symmetric
Previous:From: Joshua BerkusDate: 2011-09-25 17:52:06
Subject: Re: unite recovery.conf and postgresql.conf

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