Re: Parsing config files in a directory

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Greg Smith <gsmith(at)gregsmith(dot)com>, 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:40:27
Message-ID: 4AE857DB.7080603@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera wrote:
> 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.
>
>

In any case, initdb has to be in C for portability reasons (I'm more
aware of this than most ;-) ), but other tools don't unless the server
has to rely on them.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2009-10-28 14:56:00 Re: Parsing config files in a directory
Previous Message Alvaro Herrera 2009-10-28 14:34:19 Re: Parsing config files in a directory