New SET/autocommit problem

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: New SET/autocommit problem
Date: 2002-10-20 02:56:49
Message-ID: 200210200256.g9K2uoj23262@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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;
SET
test=> COMMIT;
WARNING: COMMIT: no transaction in progress
COMMIT

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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-10-20 03:01:18 Re: [GENERAL] [PATCH] PL/Perl (Mis-)Behavior with Runtime Error Reporting
Previous Message Bruce Momjian 2002-10-20 02:51:12 Re: autocommit vs TRUNCATE et al