Re: show all;

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Marko Kreen <marko(at)l-t(dot)ee>, pgsql-patches(at)postgresql(dot)org
Subject: Re: show all;
Date: 2001-06-02 01:17:24
Message-ID: 200106020117.f521HOo14054@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

> > 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.

I agree it links two unrelated items.

The problem with ROLLBACK is that it throws an error into the log if
there is not transaction. This is for persistent connections reset.
How about ROLLBACK QUIET?

--
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 Tom Lane 2001-06-02 06:00:20 Re: show all;
Previous Message Tom Lane 2001-06-02 00:08:06 Re: show all;