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

Re: Parsing config files in a directory

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Greg Smith <gsmith(at)gregsmith(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,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 14:33:05
Message-ID: 20091028143305.GG5018@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Greg Smith escribió:

> >I was thinking that the algorithm would be something like: "Read
> >the old postgresql.conf and write it back out to a new file line
> >by line....
> 
> This sounds familiar...oh, that's right, this is almost the same
> algorithm pgtune uses.  And it sucks, and it's a pain to covert the
> tool into C because of it, and the fact that you have to write this
> sort of boring code before you can do a single line of productive
> work is one reason why we don't have more tools available; way too
> much painful grunt work to write.

Huh, isn't this code in initdb.c already?  Since it's BSD-licensed (or
is it MIT?) you could just have lifted it.  Surely this isn't the reason
the tool isn't written in C.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2009-10-28 14:34:19
Subject: Re: Parsing config files in a directory
Previous:From: Kevin GrittnerDate: 2009-10-28 14:14:49
Subject: Re: Parsing config files in a directory

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