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

Re: Parsing config files in a directory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Smith <gsmith(at)gregsmith(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, 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 17:43:14
Message-ID: 804.1256751794@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Greg Smith <gsmith(at)gregsmith(dot)com> writes:
> If as you say the only right way to do this is to use the flex logic, that 
> just reinforced how high the bar is for someone who wants to write a tool 
> that modifies the file.

Yup, exactly.  Personally I think that trying to auto-modify
postgresql.conf is insane.  The whole and entire reason behind this
discussion is that we want the tools modifying OTHER files, for which
we will establish different and much simpler rules for what is allowed.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Greg StarkDate: 2009-10-28 17:56:06
Subject: Re: Parsing config files in a directory
Previous:From: Kevin GrittnerDate: 2009-10-28 17:32:28
Subject: Re: Parsing config files in a directory

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