On Tue, Nov 13, 2012 at 1:16 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Josh Berkus <j...@agliodbs.com> writes: >> I was imagining writing single, specific settings, which inevitably >> leads to one-setting-per-file, e.g.: > >> SET PERSISTENT work_mem = 256MB; > >> What Amit seems to be talking about is more EXPORT SETTINGS, where you >> dump all current settings in the session to a file. This seems likely >> to produce accidental changes when the user writes out settings they've >> forgotten they changed. > > Yeah. It also seems to be unnecessarily different from the existing > model of SET. I'd go with one-setting-per-command.
+1. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
