| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, 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:49:19 |
| Message-ID: | m2pqvcrfrk.fsf@2ndQuadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> 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?
Yeah, it only has value if those two conditions are met:
1. there's a single source file possible for the configuration
2. it's not in the format you'd like it to be for easy hand editing
As the premise aren't reached, I agree such a function would have no value.
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alastair Turner | 2010-10-14 14:53:53 | Re: First patch proposal |
| Previous Message | Dimitri Fontaine | 2010-10-14 14:47:41 | Re: SQL command to edit postgresql.conf, with comments |