Re: take 2: show all / reset all

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: 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 22:38:00
Message-ID: 12345.992039880@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> ! else if (strcasecmp(name, "all") == 0)
> ! {
> ! reset_DefaultXactIsoLevel();
> ! reset_XactIsoLevel();
> ! reset_random_seed();
> ! /* reset_server_encoding(); */
> ! reset_client_encoding();
> ! reset_datestyle();
> ! reset_timezone();
> !
> ! ResetAllOptions();
> ! } else

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?
Peter, your thoughts please? (If it is OK, the patch needs to change
this comment. Some additional commentary about what exactly the
makeDefault switch does would be appropriate too, since it's not real
clear exactly how "default" the value is becoming.)

I also wonder whether it's a good idea to reset the client encoding
here... it might be correct in a pure sense, but isn't it likely to
break the client?

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2001-06-08 23:13:07 Re: take 2: show all / reset all
Previous Message Peter Eisentraut 2001-06-08 16:09:50 Re: Re: [PATCHES] Fw: Isn't pg_statistic a security hole - Solution Proposal