| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Darren Duncan <darren(at)darrenduncan(dot)net>, postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SQL command to edit postgresql.conf, with comments |
| Date: | 2010-10-14 14:09:26 |
| Message-ID: | 17477.1287065366@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> writes:
> I wonder if providing a system function to load some configuration
> option from a file, using the current parser, would do it:
> SELECT pg_load_conf('path/to/filename.conf', permament => true);
That seems like a pretty bizarre idea. The settings wouldn't be
persistent would they? Or are you proposing this as a substitute
way of providing input for SET PERMANENT? If so what's the value?
It seems to me that it just introduces unnecessary failure modes
(ie, server can't read file because of permissions) without any
really useful new functionality.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2010-10-14 14:18:59 | Re: rollback to savepoint leads to transaction already in progress |
| Previous Message | Tom Lane | 2010-10-14 14:05:09 | Re: First patch proposal |