Re: RFC: programmable file format for postgresql.conf - Mailing list pgsql-hackers

From Greg Stark
Subject Re: RFC: programmable file format for postgresql.conf
Date
Msg-id CAM-w4HP-EbzmTvk8PyqNwv4dbkuZ8Nhs6UGO68Cp-O_mMtEM5w@mail.gmail.com
Whole thread Raw
In response to Re: RFC: programmable file format for postgresql.conf  (Álvaro Hernández Tortosa <aht@nosys.es>)
Responses Re: RFC: programmable file format for postgresql.conf
List pgsql-hackers
<p dir="ltr"><br /> On 12 Dec 2013 04:20, "Álvaro Hernández Tortosa" <<a
href="mailto:aht@nosys.es">aht@nosys.es</a>>wrote:<p dir="ltr">>         Thanks, Greg. I've been going through
thosethreads, they are quite interesting. I didn't find an answer, though, about my question: why parsing the
postgresql.conf(and for instance preserving the comments while writing it back) is no longer a problem<p
dir="ltr">Parsingit isn't hard. It's precisely because the file isn't programmable and is such a simple format that's
easyto parse.<p dir="ltr">It's making changes and then writing it out again while preserving the intended format that's
hard.<pdir="ltr">So we convinced people to stop trying to do that.<p dir="ltr">The whole idea of include rules is to
separatethe portion of the file that's human edited and the portion that's machine maintained. That's the only viable
strategy.

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] configure: allow adding a custom string to PG_VERSION
Next
From: Dan Langille
Date:
Subject: PGCon 2014 call for papers