Re: RFC: programmable file format for postgresql.conf

From: Greg Stark <stark(at)mit(dot)edu>
To: Álvaro Hernández Tortosa <aht(at)nosys(dot)es>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: RFC: programmable file format for postgresql.conf
Date: 2013-12-13 03:11:54
Message-ID: CAM-w4HP-EbzmTvk8PyqNwv4dbkuZ8Nhs6UGO68Cp-O_mMtEM5w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12 Dec 2013 04:20, "Álvaro Hernández Tortosa" <aht(at)nosys(dot)es> wrote:

> Thanks, Greg. I've been going through those threads, 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

Parsing it isn't hard. It's precisely because the file isn't programmable
and is such a simple format that's easy to parse.

It's making changes and then writing it out again while preserving the
intended format that's hard.

So we convinced people to stop trying to do that.

The whole idea of include rules is to separate the portion of the file
that's human edited and the portion that's machine maintained. That's the
only viable strategy.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dan Langille 2013-12-13 03:20:26 PGCon 2014 call for papers
Previous Message Peter Eisentraut 2013-12-13 03:03:58 Re: [PATCH] configure: allow adding a custom string to PG_VERSION