Re: Parsing config files in a directory

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: 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:04:11
Message-ID: 603c8f070910260604k422b5755sb75e12b6136750b8@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2009-10-26 13:08:00 Re: License clarification: BSD vs MIT
Previous Message Alvaro Herrera 2009-10-26 12:53:52 Re: Endgame for all those SELECT FOR UPDATE changes: fix plan node order