From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Marko Kreen <marko(at)l-t(dot)ee> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: show all; |
Date: | 2001-06-02 00:08:06 |
Message-ID: | 10486.991440486@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Marko Kreen <marko(at)l-t(dot)ee> writes:
> As I understand Tom, all vars should go through GUC and some of
> the current .conf vars will be SET-able. So RESET ALL would
> be quite weird.
RESET ALL should re-establish the same state of the conf vars that you'd
get with a freshly started backend. This doesn't seem weird or even in
need of discussion ...
> 1) rolls TX back, so you are not in any TX
This I do not agree with; it ties together two concepts that are better
kept separate. (If SET were under transaction control, my opinion might
be different ... but it isn't.) There is nothing wrong with sending a
ROLLBACK if you want to be sure you are not in a transaction block.
Further, there could be situations where you want to RESET the conf vars
without forcing a rollback.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-06-02 01:17:24 | Re: show all; |
Previous Message | Marko Kreen | 2001-06-01 23:17:55 | Re: show all; |