Re: Parsing config files in a directory

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

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.

--Josh Berkus

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christophe Pettus 2009-10-26 05:54:29 Proposal: String key space for advisory locks
Previous Message Greg Smith 2009-10-26 04:34:46 Re: Parsing config files in a directory