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

Re: Parsing config files in a directory

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Smith <gsmith(at)gregsmith(dot)com>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parsing config files in a directory
Date: 2009-10-28 01:05:00
Message-ID: 4AE798BC.5080502@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Robert,

> The Apache model is definitely the first of these, AFAICS.  The
> proposals on this thread mostly seem to be an amalgam of both, which
> doesn't strike me as a terribly good idea, but evidently I'm in the
> minority.

Well, an individual DBA would not want to do it both ways.  But we
should *allow* both ways rather than trying to mandate how the files get
created or what their names are.

--Josh Berkus


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2009-10-28 01:13:29
Subject: Re: per-tablespace random_page_cost/seq_page_cost
Previous:From: Robert HaasDate: 2009-10-28 00:50:30
Subject: Re: per-tablespace random_page_cost/seq_page_cost

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