Re: show all;

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Marko Kreen <marko(at)l-t(dot)ee>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: show all;
Date: 2001-06-01 22:35:16
Message-ID: 200106012235.f51MZGR08051@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

> On Fri, Jun 01, 2001 at 04:18:54PM -0400, Bruce Momjian wrote:
> >
> > Care to add RESET ALL?
>
> What exactly should it do? We have:
>
> 1) Compiled in default
> 2) postgres.conf / command line provided
> 3) through SET modified
>
> I guess it should reset to 2). But is it possible to differ
> 2) and 3) values?
>
> Or should it reset only some subset of vars (eg currenlty
> variable.c special-cased?) What variables should belog to
> that subset?

Good question and this brings up issues with SHOW. Let's look at:

SET ALL
SHOW ALL
RESET ALL

The first makes no sense. The third is needed for persistent
connections. Should RESET ALL also rollback any open transaction? If
not, we have to keep our 'BEGIN;COMMIT;' hack in PHP to reset the
transaction state. Do we eat an XID when we do that?

If we have SHOW ALL show things that are not SET-able, is it clear what
RESET ALL does? Can I recommend SHOW ALL output two groups, one
SET-able, and the rest non-SET-able. When I say SET-able, I mean
set-able by SET, not postgresql.conf.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2001-06-01 22:37:23 Re: show all;
Previous Message Joe Conway 2001-06-01 22:33:30 Re: Fw: Isn't pg_statistic a security hole - Solution Proposal