| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 10:01:12 |
| Message-ID: | m262x5rt3r.fsf@2ndQuadrant.fr |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> writes:
> Ok, now, some people want to still be able to edit the files by hand
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);
Of course comments are ignored. Settings in the directory would be
changed according to what's in your file, so that it'd be roughtly
equivalent as current steps:
a. edit the file
b. use pg_load_conf() rather than pg_reload_conf()
Comments?
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Massa, Harald Armin | 2010-10-14 10:02:13 | Re: querying the version of libpq |
| Previous Message | Boszormenyi Zoltan | 2010-10-14 09:56:24 | Re: ECPG FETCH readahead |