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
