| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Improving postgresql.conf |
| Date: | 2004-06-16 03:27:28 |
| Message-ID: | 16286.1087356448@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> The proposal is to remove the comments from postgresql.conf (like
> Apache) so all entries will be active. The downside is that it will not
> be possible to determine which values were modified from their defaults.
I think the latter is a nontrivial cost. Perhaps we could address this
by extending the pg_settings view to include the compile-time-default
values for each variable, and then instead of "show us what you did to
postgresql.conf", the standard help request would be
select * from pg_settings where setting != default_setting;
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2004-06-16 04:05:23 | Re: Improving postgresql.conf |
| Previous Message | Tom Lane | 2004-06-16 03:09:04 | Re: OWNER TO on all objects |