Re: Permanent settings - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Permanent settings
Date
Msg-id 47BC6C6C.8060708@agliodbs.com
Whole thread Raw
In response to Re: Permanent settings  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Permanent settings
List pgsql-hackers
Magnus, all:

Other thoughts:

1) fix category display for pg_settings.  'nuff said.

2) allow *commenting* of pg_settings / SET PERMANENT.  Thus:

SET PERMANENT work_mem = '12mb' COMMENT '16mb too high; OOM';

SET

SELECT name, comment FROM pg_settings WHERE name = 'work_mem';

work_mem    |   16mb too high; OOM

3) We should also discuss potentially having "changed_on", "changedby" data:

SELECT name, changedon, changedat, changedby FROM pg_settings;

work_mem       |  2008-01-22 14:35:11  | postgres
shared_buffers | 2008-01-20 13:11:11   | postgresql.conf file

(for "postgresql.conf file" the changedon would always be the date of 
the last reboot)

4) We'll need a log setting for "log SET", since I can see people 
wanting to log this kind of activity without necessarily logging all 
statements.

--Josh Berkus


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Permanent settings
Next
From: Tom Lane
Date:
Subject: Re: Permanent settings