Re: SQL command to edit postgresql.conf, with comments - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: SQL command to edit postgresql.conf, with comments
Date
Msg-id m2tykorfua.fsf@2ndQuadrant.fr
Whole thread Raw
In response to Re: SQL command to edit postgresql.conf, with comments  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: SQL command to edit postgresql.conf, with comments
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> writes:
> Um, other than "show work_mem" or "select from pg_settings"?
>
> The fact is that you cannot know the active value anyway without
> checking, because what you did with SET PERMANENT might be overridden
> in various session-local ways.  The proposal for hand-edited versus
> machine-edited files just adds one more layer of possible overrides
> to the existing half-dozen layers, all of which are widely considered
> features not bugs.  So I see no merit in your argument.

I understand that. I just think there are already too many sources for
GUCs and would welcome that there's a single possible source file with a
complete remote editing feature.

-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: First patch proposal
Next
From: Dimitri Fontaine
Date:
Subject: Re: SQL command to edit postgresql.conf, with comments