New SET/autocommit problem - Mailing list pgsql-hackers

From Bruce Momjian
Subject New SET/autocommit problem
Date
Msg-id 200210200256.g9K2uoj23262@candle.pha.pa.us
Whole thread Raw
Responses Re: New SET/autocommit problem  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Remember how we make SET/SHOW/RESET _not_ be part of a multi-statement
transaction when it is at the start of a transaction and autocommit is
off?

Well, look at this:test=> SET random_page_cost = 2;SETtest=> COMMIT;WARNING:  COMMIT: no transaction in progressCOMMIT

The WARNING happens with SHOW and RESET too.  I wonder if we should
suppress the WARNING of a COMMIT with no statements when autocommit is
off.  This will probably be better for portability, though again, it is
confusing.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: autocommit vs TRUNCATE et al
Next
From: Bruce Momjian
Date:
Subject: Re: [GENERAL] [PATCH] PL/Perl (Mis-)Behavior with Runtime Error Reporting