Re: Parsing config files in a directory

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parsing config files in a directory
Date: 2009-10-26 13:51:14
Message-ID: 1256565074.6481.0.camel@fsopti579.F-Secure.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2009-10-26 at 09:04 -0400, Robert Haas wrote:
> On Mon, Oct 26, 2009 at 12:46 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> > On 10/25/09 5:33 PM, Robert Haas wrote:
> >> Greg believes that it
> >> isn't politically feasible to change the default postgresql.conf, now
> >> or perhaps ever. I notice that he didn't say that he thinks it's a
> >> bad idea. So he has come up with an alternate plan which he believes
> >> is the best one possible considering that limitation.
> >
> > I agree with Greg. I would love to dump the current stupid long
> > postgresql.conf, but I've lost that argument every time I've had it.
> >
> > We have to work around it.
>
> Do you have a pointer to the archives?

http://archives.postgresql.org/pgsql-hackers/2008-08/msg00812.php

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2009-10-26 13:51:27 Re: License clarification: BSD vs MIT
Previous Message Merlin Moncure 2009-10-26 13:48:03 Re: Proposal: String key space for advisory locks