| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Smith <gsmith(at)gregsmith(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Add default_val to pg_settings |
| Date: | 2008-09-25 13:23:22 |
| Message-ID: | 1222349002.4445.786.camel@ebony.2ndQuadrant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2008-09-25 at 14:52 +0200, Magnus Hagander wrote:
> Simon Riggs wrote:
> > On Thu, 2008-09-25 at 14:42 +0200, Magnus Hagander wrote:
> >> Having
> >> one column named reset_val and one named boot_val should work, no?
> >
> > Yes, those names seem very appropriate to me.
> >
> > Finding the reset_val isn't that tough, IIRC the way the guc assignment
> > works with its "doit" flag.
> I haven't looked at the code.. but there is actually a field in the
> struct called reset_val. It may not be usable, or you may have just
> missed it?
Yah, missed it. Cool, even easier ;-)
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-09-25 13:44:17 | Re: Add default_val to pg_settings |
| Previous Message | Marko Kreen | 2008-09-25 13:20:30 | Re: PostgreSQL future ideas |