On 12/1/13, 2:24 PM, Álvaro Hernández Tortosa wrote:
> IMHO, defining a new syntax for the postgreql.conf file format,
> that is suitable for writing and parsing, or using an already existing,
> well-known, programmatic syntax, could offer a solution for all the
> problems/limitations above.
That's the problem, there isn't one, is there? The closest you'd get is
the INI syntax, but that's like CSV, with many variations. And most
client libraries for this will likely drop all comments when they read
and write a file, so this doesn't address that issue.
