| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Marko Kreen <marko(at)l-t(dot)ee>, <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: take 2: show all / reset all |
| Date: | 2001-06-08 23:17:17 |
| Message-ID: | Pine.LNX.4.30.0106090112540.757-100000@peter.localdomain |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Tom Lane writes:
> This looks fairly bogus, given the comment on ResetAllOptions:
>
> /*
> * Reset all options to their specified default values. Should only be
> * called at program startup.
> */
>
> Or is that OK now with the "makeDefault" addition to SetConfigOption?
Evidently not quite:
peter=# show port;
NOTICE: port is 6543
SHOW VARIABLE
peter=# reset all;
RESET VARIABLE
peter=# show port;
NOTICE: port is 5432
SHOW VARIABLE
This is because I started the postmaster with -p 6543, but that assigns to
the variable directly and does not save it as default.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2001-06-09 01:28:20 | Re: Re: [PATCHES] Fw: Isn't pg_statistic a security hole - Solution Proposal |
| Previous Message | Bruce Momjian | 2001-06-08 23:13:07 | Re: take 2: show all / reset all |