| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [patch] GUC source file and line number |
| Date: | 2008-08-29 21:09:11 |
| Message-ID: | 20080829210911.GL3983@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Treat wrote:
> On Thursday 28 August 2008 13:08:58 Alvaro Herrera wrote:
> > This should make life easier for tools trying to find the config file
> > each setting is from (and possibly edit it).
>
> If I have read this patch right, anything commented out (aka all of our
> default values) will emit null in these fields... right?
Of course.
> Trying to decide just how helpful this will actually be for tool
> writers.
Oh, it's easy -- just rip all the commented stuff out of the default
file. It's useless anyway.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-08-29 22:37:54 | Re: Is it really such a good thing for newNode() to be a macro? |
| Previous Message | Robert Treat | 2008-08-29 21:01:17 | Re: [patch] GUC source file and line number |