2000-01-09 04:48:39 +01:00
|
|
|
--
|
|
|
|
-- TRANSACTIONS
|
|
|
|
--
|
|
|
|
BEGIN;
|
2010-11-23 21:27:50 +01:00
|
|
|
SELECT *
|
1997-04-29 16:23:51 +02:00
|
|
|
INTO TABLE xacttest
|
|
|
|
FROM aggtest;
|
2000-01-09 04:48:39 +01:00
|
|
|
INSERT INTO xacttest (a, b) VALUES (777, 777.777);
|
|
|
|
END;
|
|
|
|
-- should retrieve one value--
|
|
|
|
SELECT a FROM xacttest WHERE a > 100;
|
|
|
|
a
|
|
|
|
-----
|
|
|
|
777
|
1997-04-29 16:23:51 +02:00
|
|
|
(1 row)
|
|
|
|
|
2000-01-09 04:48:39 +01:00
|
|
|
BEGIN;
|
|
|
|
CREATE TABLE disappear (a int4);
|
|
|
|
DELETE FROM aggtest;
|
|
|
|
-- should be empty
|
|
|
|
SELECT * FROM aggtest;
|
|
|
|
a | b
|
|
|
|
---+---
|
1997-04-29 16:23:51 +02:00
|
|
|
(0 rows)
|
|
|
|
|
2000-01-09 04:48:39 +01:00
|
|
|
ABORT;
|
2010-11-23 21:27:50 +01:00
|
|
|
-- should not exist
|
2000-01-09 04:48:39 +01:00
|
|
|
SELECT oid FROM pg_class WHERE relname = 'disappear';
|
|
|
|
oid
|
|
|
|
-----
|
1997-04-29 16:23:51 +02:00
|
|
|
(0 rows)
|
|
|
|
|
2010-11-23 21:27:50 +01:00
|
|
|
-- should have members again
|
2000-01-09 04:48:39 +01:00
|
|
|
SELECT * FROM aggtest;
|
|
|
|
a | b
|
|
|
|
-----+---------
|
|
|
|
56 | 7.8
|
|
|
|
100 | 99.097
|
|
|
|
0 | 0.09561
|
|
|
|
42 | 324.78
|
1997-04-29 16:23:51 +02:00
|
|
|
(4 rows)
|
|
|
|
|
2003-01-10 23:03:30 +01:00
|
|
|
-- Read-only tests
|
|
|
|
CREATE TABLE writetest (a int);
|
|
|
|
CREATE TEMPORARY TABLE temptest (a int);
|
2011-01-23 02:51:32 +01:00
|
|
|
BEGIN;
|
Implement genuine serializable isolation level.
Until now, our Serializable mode has in fact been what's called Snapshot
Isolation, which allows some anomalies that could not occur in any
serialized ordering of the transactions. This patch fixes that using a
method called Serializable Snapshot Isolation, based on research papers by
Michael J. Cahill (see README-SSI for full references). In Serializable
Snapshot Isolation, transactions run like they do in Snapshot Isolation,
but a predicate lock manager observes the reads and writes performed and
aborts transactions if it detects that an anomaly might occur. This method
produces some false positives, ie. it sometimes aborts transactions even
though there is no anomaly.
To track reads we implement predicate locking, see storage/lmgr/predicate.c.
Whenever a tuple is read, a predicate lock is acquired on the tuple. Shared
memory is finite, so when a transaction takes many tuple-level locks on a
page, the locks are promoted to a single page-level lock, and further to a
single relation level lock if necessary. To lock key values with no matching
tuple, a sequential scan always takes a relation-level lock, and an index
scan acquires a page-level lock that covers the search key, whether or not
there are any matching keys at the moment.
A predicate lock doesn't conflict with any regular locks or with another
predicate locks in the normal sense. They're only used by the predicate lock
manager to detect the danger of anomalies. Only serializable transactions
participate in predicate locking, so there should be no extra overhead for
for other transactions.
Predicate locks can't be released at commit, but must be remembered until
all the transactions that overlapped with it have completed. That means that
we need to remember an unbounded amount of predicate locks, so we apply a
lossy but conservative method of tracking locks for committed transactions.
If we run short of shared memory, we overflow to a new "pg_serial" SLRU
pool.
We don't currently allow Serializable transactions in Hot Standby mode.
That would be hard, because even read-only transactions can cause anomalies
that wouldn't otherwise occur.
Serializable isolation mode now means the new fully serializable level.
Repeatable Read gives you the old Snapshot Isolation level that we have
always had.
Kevin Grittner and Dan Ports, reviewed by Jeff Davis, Heikki Linnakangas and
Anssi Kääriäinen
2011-02-07 22:46:51 +01:00
|
|
|
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE, READ ONLY, DEFERRABLE; -- ok
|
2011-01-23 02:51:32 +01:00
|
|
|
SELECT * FROM writetest; -- ok
|
|
|
|
a
|
|
|
|
---
|
|
|
|
(0 rows)
|
|
|
|
|
|
|
|
SET TRANSACTION READ WRITE; --fail
|
|
|
|
ERROR: transaction read-write mode must be set before any query
|
|
|
|
COMMIT;
|
|
|
|
BEGIN;
|
|
|
|
SET TRANSACTION READ ONLY; -- ok
|
|
|
|
SET TRANSACTION READ WRITE; -- ok
|
|
|
|
SET TRANSACTION READ ONLY; -- ok
|
|
|
|
SELECT * FROM writetest; -- ok
|
|
|
|
a
|
|
|
|
---
|
|
|
|
(0 rows)
|
|
|
|
|
|
|
|
SAVEPOINT x;
|
|
|
|
SET TRANSACTION READ ONLY; -- ok
|
|
|
|
SELECT * FROM writetest; -- ok
|
|
|
|
a
|
|
|
|
---
|
|
|
|
(0 rows)
|
|
|
|
|
|
|
|
SET TRANSACTION READ ONLY; -- ok
|
|
|
|
SET TRANSACTION READ WRITE; --fail
|
|
|
|
ERROR: cannot set transaction read-write mode inside a read-only transaction
|
|
|
|
COMMIT;
|
|
|
|
BEGIN;
|
|
|
|
SET TRANSACTION READ WRITE; -- ok
|
|
|
|
SAVEPOINT x;
|
|
|
|
SET TRANSACTION READ WRITE; -- ok
|
|
|
|
SET TRANSACTION READ ONLY; -- ok
|
|
|
|
SELECT * FROM writetest; -- ok
|
|
|
|
a
|
|
|
|
---
|
|
|
|
(0 rows)
|
|
|
|
|
|
|
|
SET TRANSACTION READ ONLY; -- ok
|
|
|
|
SET TRANSACTION READ WRITE; --fail
|
|
|
|
ERROR: cannot set transaction read-write mode inside a read-only transaction
|
|
|
|
COMMIT;
|
|
|
|
BEGIN;
|
|
|
|
SET TRANSACTION READ WRITE; -- ok
|
|
|
|
SAVEPOINT x;
|
|
|
|
SET TRANSACTION READ ONLY; -- ok
|
|
|
|
SELECT * FROM writetest; -- ok
|
|
|
|
a
|
|
|
|
---
|
|
|
|
(0 rows)
|
|
|
|
|
|
|
|
ROLLBACK TO SAVEPOINT x;
|
|
|
|
SHOW transaction_read_only; -- off
|
|
|
|
transaction_read_only
|
|
|
|
-----------------------
|
|
|
|
off
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
SAVEPOINT y;
|
|
|
|
SET TRANSACTION READ ONLY; -- ok
|
|
|
|
SELECT * FROM writetest; -- ok
|
|
|
|
a
|
|
|
|
---
|
|
|
|
(0 rows)
|
|
|
|
|
|
|
|
RELEASE SAVEPOINT y;
|
|
|
|
SHOW transaction_read_only; -- off
|
|
|
|
transaction_read_only
|
|
|
|
-----------------------
|
|
|
|
off
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
COMMIT;
|
2003-01-10 23:03:30 +01:00
|
|
|
SET SESSION CHARACTERISTICS AS TRANSACTION READ ONLY;
|
|
|
|
DROP TABLE writetest; -- fail
|
2010-02-20 22:24:02 +01:00
|
|
|
ERROR: cannot execute DROP TABLE in a read-only transaction
|
2003-01-10 23:03:30 +01:00
|
|
|
INSERT INTO writetest VALUES (1); -- fail
|
2010-02-20 22:24:02 +01:00
|
|
|
ERROR: cannot execute INSERT in a read-only transaction
|
2003-01-10 23:03:30 +01:00
|
|
|
SELECT * FROM writetest; -- ok
|
|
|
|
a
|
|
|
|
---
|
|
|
|
(0 rows)
|
|
|
|
|
|
|
|
DELETE FROM temptest; -- ok
|
2005-04-07 03:51:41 +02:00
|
|
|
UPDATE temptest SET a = 0 FROM writetest WHERE temptest.a = 1 AND writetest.a = temptest.a; -- ok
|
2003-01-10 23:03:30 +01:00
|
|
|
PREPARE test AS UPDATE writetest SET a = 0; -- ok
|
|
|
|
EXECUTE test; -- fail
|
2010-02-20 22:24:02 +01:00
|
|
|
ERROR: cannot execute UPDATE in a read-only transaction
|
2003-01-10 23:03:30 +01:00
|
|
|
SELECT * FROM writetest, temptest; -- ok
|
|
|
|
a | a
|
|
|
|
---+---
|
|
|
|
(0 rows)
|
|
|
|
|
|
|
|
CREATE TABLE test AS SELECT * FROM writetest; -- fail
|
2010-02-20 22:24:02 +01:00
|
|
|
ERROR: cannot execute SELECT INTO in a read-only transaction
|
2003-01-10 23:03:30 +01:00
|
|
|
START TRANSACTION READ WRITE;
|
|
|
|
DROP TABLE writetest; -- ok
|
|
|
|
COMMIT;
|
2004-07-01 02:52:04 +02:00
|
|
|
-- Subtransactions, basic tests
|
|
|
|
-- create & drop tables
|
|
|
|
SET SESSION CHARACTERISTICS AS TRANSACTION READ WRITE;
|
|
|
|
CREATE TABLE foobar (a int);
|
|
|
|
BEGIN;
|
|
|
|
CREATE TABLE foo (a int);
|
2004-07-27 07:11:48 +02:00
|
|
|
SAVEPOINT one;
|
2004-07-01 02:52:04 +02:00
|
|
|
DROP TABLE foo;
|
|
|
|
CREATE TABLE bar (a int);
|
2004-08-12 21:12:21 +02:00
|
|
|
ROLLBACK TO SAVEPOINT one;
|
|
|
|
RELEASE SAVEPOINT one;
|
2004-07-27 07:11:48 +02:00
|
|
|
SAVEPOINT two;
|
2004-07-01 02:52:04 +02:00
|
|
|
CREATE TABLE baz (a int);
|
2004-08-12 21:12:21 +02:00
|
|
|
RELEASE SAVEPOINT two;
|
2004-07-01 02:52:04 +02:00
|
|
|
drop TABLE foobar;
|
|
|
|
CREATE TABLE barbaz (a int);
|
|
|
|
COMMIT;
|
|
|
|
-- should exist: barbaz, baz, foo
|
|
|
|
SELECT * FROM foo; -- should be empty
|
|
|
|
a
|
|
|
|
---
|
|
|
|
(0 rows)
|
|
|
|
|
|
|
|
SELECT * FROM bar; -- shouldn't exist
|
|
|
|
ERROR: relation "bar" does not exist
|
2008-09-01 22:42:46 +02:00
|
|
|
LINE 1: SELECT * FROM bar;
|
|
|
|
^
|
2004-07-01 02:52:04 +02:00
|
|
|
SELECT * FROM barbaz; -- should be empty
|
|
|
|
a
|
|
|
|
---
|
|
|
|
(0 rows)
|
|
|
|
|
|
|
|
SELECT * FROM baz; -- should be empty
|
|
|
|
a
|
|
|
|
---
|
|
|
|
(0 rows)
|
|
|
|
|
|
|
|
-- inserts
|
|
|
|
BEGIN;
|
|
|
|
INSERT INTO foo VALUES (1);
|
2004-07-27 07:11:48 +02:00
|
|
|
SAVEPOINT one;
|
2004-07-01 02:52:04 +02:00
|
|
|
INSERT into bar VALUES (1);
|
|
|
|
ERROR: relation "bar" does not exist
|
2008-09-01 22:42:46 +02:00
|
|
|
LINE 1: INSERT into bar VALUES (1);
|
|
|
|
^
|
2004-07-27 07:11:48 +02:00
|
|
|
ROLLBACK TO one;
|
2004-08-12 21:12:21 +02:00
|
|
|
RELEASE SAVEPOINT one;
|
2004-07-27 07:11:48 +02:00
|
|
|
SAVEPOINT two;
|
2004-07-01 02:52:04 +02:00
|
|
|
INSERT into barbaz VALUES (1);
|
2004-07-27 07:11:48 +02:00
|
|
|
RELEASE two;
|
|
|
|
SAVEPOINT three;
|
|
|
|
SAVEPOINT four;
|
2004-07-01 02:52:04 +02:00
|
|
|
INSERT INTO foo VALUES (2);
|
2004-08-12 21:12:21 +02:00
|
|
|
RELEASE SAVEPOINT four;
|
|
|
|
ROLLBACK TO SAVEPOINT three;
|
|
|
|
RELEASE SAVEPOINT three;
|
2004-07-01 02:52:04 +02:00
|
|
|
INSERT INTO foo VALUES (3);
|
|
|
|
COMMIT;
|
|
|
|
SELECT * FROM foo; -- should have 1 and 3
|
|
|
|
a
|
|
|
|
---
|
|
|
|
1
|
|
|
|
3
|
|
|
|
(2 rows)
|
|
|
|
|
|
|
|
SELECT * FROM barbaz; -- should have 1
|
|
|
|
a
|
|
|
|
---
|
|
|
|
1
|
|
|
|
(1 row)
|
|
|
|
|
2004-07-27 07:11:48 +02:00
|
|
|
-- test whole-tree commit
|
2004-07-01 22:11:03 +02:00
|
|
|
BEGIN;
|
2004-07-27 07:11:48 +02:00
|
|
|
SAVEPOINT one;
|
|
|
|
SELECT foo;
|
|
|
|
ERROR: column "foo" does not exist
|
2006-03-14 23:48:25 +01:00
|
|
|
LINE 1: SELECT foo;
|
|
|
|
^
|
2004-08-12 21:12:21 +02:00
|
|
|
ROLLBACK TO SAVEPOINT one;
|
|
|
|
RELEASE SAVEPOINT one;
|
2004-07-27 07:11:48 +02:00
|
|
|
SAVEPOINT two;
|
|
|
|
CREATE TABLE savepoints (a int);
|
|
|
|
SAVEPOINT three;
|
|
|
|
INSERT INTO savepoints VALUES (1);
|
|
|
|
SAVEPOINT four;
|
|
|
|
INSERT INTO savepoints VALUES (2);
|
|
|
|
SAVEPOINT five;
|
|
|
|
INSERT INTO savepoints VALUES (3);
|
2004-08-12 21:12:21 +02:00
|
|
|
ROLLBACK TO SAVEPOINT five;
|
2004-07-01 22:11:03 +02:00
|
|
|
COMMIT;
|
2004-07-27 07:11:48 +02:00
|
|
|
COMMIT; -- should not be in a transaction block
|
|
|
|
WARNING: there is no transaction in progress
|
|
|
|
SELECT * FROM savepoints;
|
|
|
|
a
|
|
|
|
---
|
|
|
|
1
|
|
|
|
2
|
|
|
|
(2 rows)
|
|
|
|
|
|
|
|
-- test whole-tree rollback
|
|
|
|
BEGIN;
|
|
|
|
SAVEPOINT one;
|
|
|
|
DELETE FROM savepoints WHERE a=1;
|
2004-08-12 21:12:21 +02:00
|
|
|
RELEASE SAVEPOINT one;
|
2004-07-27 07:11:48 +02:00
|
|
|
SAVEPOINT two;
|
|
|
|
DELETE FROM savepoints WHERE a=1;
|
|
|
|
SAVEPOINT three;
|
|
|
|
DELETE FROM savepoints WHERE a=2;
|
|
|
|
ROLLBACK;
|
|
|
|
COMMIT; -- should not be in a transaction block
|
|
|
|
WARNING: there is no transaction in progress
|
|
|
|
SELECT * FROM savepoints;
|
|
|
|
a
|
|
|
|
---
|
|
|
|
1
|
|
|
|
2
|
|
|
|
(2 rows)
|
|
|
|
|
|
|
|
-- test whole-tree commit on an aborted subtransaction
|
|
|
|
BEGIN;
|
|
|
|
INSERT INTO savepoints VALUES (4);
|
|
|
|
SAVEPOINT one;
|
|
|
|
INSERT INTO savepoints VALUES (5);
|
|
|
|
SELECT foo;
|
|
|
|
ERROR: column "foo" does not exist
|
2006-03-14 23:48:25 +01:00
|
|
|
LINE 1: SELECT foo;
|
|
|
|
^
|
2004-07-27 07:11:48 +02:00
|
|
|
COMMIT;
|
|
|
|
SELECT * FROM savepoints;
|
|
|
|
a
|
|
|
|
---
|
|
|
|
1
|
|
|
|
2
|
|
|
|
(2 rows)
|
|
|
|
|
|
|
|
BEGIN;
|
|
|
|
INSERT INTO savepoints VALUES (6);
|
|
|
|
SAVEPOINT one;
|
|
|
|
INSERT INTO savepoints VALUES (7);
|
2004-08-12 21:12:21 +02:00
|
|
|
RELEASE SAVEPOINT one;
|
2004-07-27 07:11:48 +02:00
|
|
|
INSERT INTO savepoints VALUES (8);
|
|
|
|
COMMIT;
|
|
|
|
-- rows 6 and 8 should have been created by the same xact
|
|
|
|
SELECT a.xmin = b.xmin FROM savepoints a, savepoints b WHERE a.a=6 AND b.a=8;
|
2004-07-01 22:11:03 +02:00
|
|
|
?column?
|
|
|
|
----------
|
2004-07-27 07:11:48 +02:00
|
|
|
t
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
-- rows 6 and 7 should have been created by different xacts
|
|
|
|
SELECT a.xmin = b.xmin FROM savepoints a, savepoints b WHERE a.a=6 AND b.a=7;
|
|
|
|
?column?
|
|
|
|
----------
|
|
|
|
f
|
2004-07-01 22:11:03 +02:00
|
|
|
(1 row)
|
|
|
|
|
|
|
|
BEGIN;
|
2004-07-27 07:11:48 +02:00
|
|
|
INSERT INTO savepoints VALUES (9);
|
|
|
|
SAVEPOINT one;
|
|
|
|
INSERT INTO savepoints VALUES (10);
|
2004-08-12 21:12:21 +02:00
|
|
|
ROLLBACK TO SAVEPOINT one;
|
2004-07-27 07:11:48 +02:00
|
|
|
INSERT INTO savepoints VALUES (11);
|
|
|
|
COMMIT;
|
|
|
|
SELECT a FROM savepoints WHERE a in (9, 10, 11);
|
|
|
|
a
|
|
|
|
----
|
|
|
|
9
|
|
|
|
11
|
|
|
|
(2 rows)
|
|
|
|
|
|
|
|
-- rows 9 and 11 should have been created by different xacts
|
|
|
|
SELECT a.xmin = b.xmin FROM savepoints a, savepoints b WHERE a.a=9 AND b.a=11;
|
2004-07-01 22:11:03 +02:00
|
|
|
?column?
|
|
|
|
----------
|
2004-07-27 07:11:48 +02:00
|
|
|
f
|
2004-07-01 22:11:03 +02:00
|
|
|
(1 row)
|
|
|
|
|
2004-07-27 07:11:48 +02:00
|
|
|
BEGIN;
|
|
|
|
INSERT INTO savepoints VALUES (12);
|
|
|
|
SAVEPOINT one;
|
|
|
|
INSERT INTO savepoints VALUES (13);
|
|
|
|
SAVEPOINT two;
|
|
|
|
INSERT INTO savepoints VALUES (14);
|
2004-08-12 21:12:21 +02:00
|
|
|
ROLLBACK TO SAVEPOINT one;
|
2004-07-27 07:11:48 +02:00
|
|
|
INSERT INTO savepoints VALUES (15);
|
|
|
|
SAVEPOINT two;
|
|
|
|
INSERT INTO savepoints VALUES (16);
|
|
|
|
SAVEPOINT three;
|
|
|
|
INSERT INTO savepoints VALUES (17);
|
|
|
|
COMMIT;
|
|
|
|
SELECT a FROM savepoints WHERE a BETWEEN 12 AND 17;
|
|
|
|
a
|
|
|
|
----
|
|
|
|
12
|
|
|
|
15
|
|
|
|
16
|
|
|
|
17
|
|
|
|
(4 rows)
|
|
|
|
|
|
|
|
BEGIN;
|
|
|
|
INSERT INTO savepoints VALUES (18);
|
|
|
|
SAVEPOINT one;
|
|
|
|
INSERT INTO savepoints VALUES (19);
|
|
|
|
SAVEPOINT two;
|
|
|
|
INSERT INTO savepoints VALUES (20);
|
2004-08-12 21:12:21 +02:00
|
|
|
ROLLBACK TO SAVEPOINT one;
|
2004-07-27 07:11:48 +02:00
|
|
|
INSERT INTO savepoints VALUES (21);
|
2004-08-12 21:12:21 +02:00
|
|
|
ROLLBACK TO SAVEPOINT one;
|
2004-07-27 07:11:48 +02:00
|
|
|
INSERT INTO savepoints VALUES (22);
|
|
|
|
COMMIT;
|
|
|
|
SELECT a FROM savepoints WHERE a BETWEEN 18 AND 22;
|
|
|
|
a
|
|
|
|
----
|
|
|
|
18
|
|
|
|
22
|
|
|
|
(2 rows)
|
|
|
|
|
|
|
|
DROP TABLE savepoints;
|
|
|
|
-- only in a transaction block:
|
|
|
|
SAVEPOINT one;
|
Wording cleanup for error messages. Also change can't -> cannot.
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
2007-02-01 20:10:30 +01:00
|
|
|
ERROR: SAVEPOINT can only be used in transaction blocks
|
2004-08-12 21:12:21 +02:00
|
|
|
ROLLBACK TO SAVEPOINT one;
|
Wording cleanup for error messages. Also change can't -> cannot.
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
2007-02-01 20:10:30 +01:00
|
|
|
ERROR: ROLLBACK TO SAVEPOINT can only be used in transaction blocks
|
2004-08-12 21:12:21 +02:00
|
|
|
RELEASE SAVEPOINT one;
|
Wording cleanup for error messages. Also change can't -> cannot.
Standard English uses "may", "can", and "might" in different ways:
may - permission, "You may borrow my rake."
can - ability, "I can lift that log."
might - possibility, "It might rain today."
Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice. Similarly, "It may crash" is better stated, "It might crash".
2007-02-01 20:10:30 +01:00
|
|
|
ERROR: RELEASE SAVEPOINT can only be used in transaction blocks
|
2004-07-27 07:11:48 +02:00
|
|
|
-- Only "rollback to" allowed in aborted state
|
|
|
|
BEGIN;
|
|
|
|
SAVEPOINT one;
|
|
|
|
SELECT 0/0;
|
2004-07-01 22:11:03 +02:00
|
|
|
ERROR: division by zero
|
2004-07-27 07:11:48 +02:00
|
|
|
SAVEPOINT two; -- ignored till the end of ...
|
2004-07-01 22:11:03 +02:00
|
|
|
ERROR: current transaction is aborted, commands ignored until end of transaction block
|
2004-08-12 21:12:21 +02:00
|
|
|
RELEASE SAVEPOINT one; -- ignored till the end of ...
|
2004-07-01 22:11:03 +02:00
|
|
|
ERROR: current transaction is aborted, commands ignored until end of transaction block
|
2004-08-12 21:12:21 +02:00
|
|
|
ROLLBACK TO SAVEPOINT one;
|
2004-07-27 07:11:48 +02:00
|
|
|
SELECT 1;
|
2004-07-01 22:11:03 +02:00
|
|
|
?column?
|
|
|
|
----------
|
|
|
|
1
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
COMMIT;
|
|
|
|
SELECT 1; -- this should work
|
|
|
|
?column?
|
|
|
|
----------
|
|
|
|
1
|
|
|
|
(1 row)
|
|
|
|
|
2004-07-17 05:32:14 +02:00
|
|
|
-- check non-transactional behavior of cursors
|
|
|
|
BEGIN;
|
2007-06-09 19:24:46 +02:00
|
|
|
DECLARE c CURSOR FOR SELECT unique2 FROM tenk1 ORDER BY unique2;
|
2004-07-27 07:11:48 +02:00
|
|
|
SAVEPOINT one;
|
2004-07-17 05:32:14 +02:00
|
|
|
FETCH 10 FROM c;
|
|
|
|
unique2
|
|
|
|
---------
|
|
|
|
0
|
|
|
|
1
|
|
|
|
2
|
|
|
|
3
|
|
|
|
4
|
|
|
|
5
|
|
|
|
6
|
|
|
|
7
|
|
|
|
8
|
|
|
|
9
|
|
|
|
(10 rows)
|
|
|
|
|
2004-08-12 21:12:21 +02:00
|
|
|
ROLLBACK TO SAVEPOINT one;
|
2004-07-17 05:32:14 +02:00
|
|
|
FETCH 10 FROM c;
|
|
|
|
unique2
|
|
|
|
---------
|
|
|
|
10
|
|
|
|
11
|
|
|
|
12
|
|
|
|
13
|
|
|
|
14
|
|
|
|
15
|
|
|
|
16
|
|
|
|
17
|
|
|
|
18
|
|
|
|
19
|
|
|
|
(10 rows)
|
|
|
|
|
2004-08-12 21:12:21 +02:00
|
|
|
RELEASE SAVEPOINT one;
|
2004-07-17 05:32:14 +02:00
|
|
|
FETCH 10 FROM c;
|
|
|
|
unique2
|
|
|
|
---------
|
|
|
|
20
|
|
|
|
21
|
|
|
|
22
|
|
|
|
23
|
|
|
|
24
|
|
|
|
25
|
|
|
|
26
|
|
|
|
27
|
|
|
|
28
|
|
|
|
29
|
|
|
|
(10 rows)
|
|
|
|
|
|
|
|
CLOSE c;
|
2007-06-09 19:24:46 +02:00
|
|
|
DECLARE c CURSOR FOR SELECT unique2/0 FROM tenk1 ORDER BY unique2;
|
2004-07-27 07:11:48 +02:00
|
|
|
SAVEPOINT two;
|
2004-07-17 05:32:14 +02:00
|
|
|
FETCH 10 FROM c;
|
|
|
|
ERROR: division by zero
|
2004-08-12 21:12:21 +02:00
|
|
|
ROLLBACK TO SAVEPOINT two;
|
2004-07-17 05:32:14 +02:00
|
|
|
-- c is now dead to the world ...
|
|
|
|
FETCH 10 FROM c;
|
|
|
|
ERROR: portal "c" cannot be run
|
2004-08-12 21:12:21 +02:00
|
|
|
ROLLBACK TO SAVEPOINT two;
|
|
|
|
RELEASE SAVEPOINT two;
|
2004-07-17 05:32:14 +02:00
|
|
|
FETCH 10 FROM c;
|
|
|
|
ERROR: portal "c" cannot be run
|
|
|
|
COMMIT;
|
2004-09-13 22:10:13 +02:00
|
|
|
--
|
|
|
|
-- Check that "stable" functions are really stable. They should not be
|
|
|
|
-- able to see the partial results of the calling query. (Ideally we would
|
|
|
|
-- also check that they don't see commits of concurrent transactions, but
|
|
|
|
-- that's a mite hard to do within the limitations of pg_regress.)
|
|
|
|
--
|
|
|
|
select * from xacttest;
|
|
|
|
a | b
|
|
|
|
-----+---------
|
|
|
|
56 | 7.8
|
|
|
|
100 | 99.097
|
|
|
|
0 | 0.09561
|
|
|
|
42 | 324.78
|
|
|
|
777 | 777.777
|
|
|
|
(5 rows)
|
|
|
|
|
|
|
|
create or replace function max_xacttest() returns smallint language sql as
|
|
|
|
'select max(a) from xacttest' stable;
|
|
|
|
begin;
|
|
|
|
update xacttest set a = max_xacttest() + 10 where a > 0;
|
|
|
|
select * from xacttest;
|
|
|
|
a | b
|
|
|
|
-----+---------
|
|
|
|
0 | 0.09561
|
|
|
|
787 | 7.8
|
|
|
|
787 | 99.097
|
|
|
|
787 | 324.78
|
|
|
|
787 | 777.777
|
|
|
|
(5 rows)
|
|
|
|
|
|
|
|
rollback;
|
|
|
|
-- But a volatile function can see the partial results of the calling query
|
|
|
|
create or replace function max_xacttest() returns smallint language sql as
|
|
|
|
'select max(a) from xacttest' volatile;
|
|
|
|
begin;
|
|
|
|
update xacttest set a = max_xacttest() + 10 where a > 0;
|
|
|
|
select * from xacttest;
|
|
|
|
a | b
|
|
|
|
-----+---------
|
|
|
|
0 | 0.09561
|
|
|
|
787 | 7.8
|
|
|
|
797 | 99.097
|
|
|
|
807 | 324.78
|
|
|
|
817 | 777.777
|
|
|
|
(5 rows)
|
|
|
|
|
|
|
|
rollback;
|
|
|
|
-- Now the same test with plpgsql (since it depends on SPI which is different)
|
|
|
|
create or replace function max_xacttest() returns smallint language plpgsql as
|
|
|
|
'begin return max(a) from xacttest; end' stable;
|
|
|
|
begin;
|
|
|
|
update xacttest set a = max_xacttest() + 10 where a > 0;
|
|
|
|
select * from xacttest;
|
|
|
|
a | b
|
|
|
|
-----+---------
|
|
|
|
0 | 0.09561
|
|
|
|
787 | 7.8
|
|
|
|
787 | 99.097
|
|
|
|
787 | 324.78
|
|
|
|
787 | 777.777
|
|
|
|
(5 rows)
|
|
|
|
|
|
|
|
rollback;
|
|
|
|
create or replace function max_xacttest() returns smallint language plpgsql as
|
|
|
|
'begin return max(a) from xacttest; end' volatile;
|
|
|
|
begin;
|
|
|
|
update xacttest set a = max_xacttest() + 10 where a > 0;
|
|
|
|
select * from xacttest;
|
|
|
|
a | b
|
|
|
|
-----+---------
|
|
|
|
0 | 0.09561
|
|
|
|
787 | 7.8
|
|
|
|
797 | 99.097
|
|
|
|
807 | 324.78
|
|
|
|
817 | 777.777
|
|
|
|
(5 rows)
|
|
|
|
|
|
|
|
rollback;
|
2004-09-06 19:56:33 +02:00
|
|
|
-- test case for problems with dropping an open relation during abort
|
|
|
|
BEGIN;
|
|
|
|
savepoint x;
|
|
|
|
CREATE TABLE koju (a INT UNIQUE);
|
|
|
|
NOTICE: CREATE TABLE / UNIQUE will create implicit index "koju_a_key" for table "koju"
|
|
|
|
INSERT INTO koju VALUES (1);
|
|
|
|
INSERT INTO koju VALUES (1);
|
2007-06-04 00:16:03 +02:00
|
|
|
ERROR: duplicate key value violates unique constraint "koju_a_key"
|
2009-08-01 21:59:41 +02:00
|
|
|
DETAIL: Key (a)=(1) already exists.
|
2004-09-06 19:56:33 +02:00
|
|
|
rollback to x;
|
|
|
|
CREATE TABLE koju (a INT UNIQUE);
|
|
|
|
NOTICE: CREATE TABLE / UNIQUE will create implicit index "koju_a_key" for table "koju"
|
|
|
|
INSERT INTO koju VALUES (1);
|
|
|
|
INSERT INTO koju VALUES (1);
|
2007-06-04 00:16:03 +02:00
|
|
|
ERROR: duplicate key value violates unique constraint "koju_a_key"
|
2009-08-01 21:59:41 +02:00
|
|
|
DETAIL: Key (a)=(1) already exists.
|
2004-09-06 19:56:33 +02:00
|
|
|
ROLLBACK;
|
2004-07-01 02:52:04 +02:00
|
|
|
DROP TABLE foo;
|
|
|
|
DROP TABLE baz;
|
|
|
|
DROP TABLE barbaz;
|
2005-01-27 02:32:00 +01:00
|
|
|
-- verify that cursors created during an aborted subtransaction are
|
|
|
|
-- closed, but that we do not rollback the effect of any FETCHs
|
|
|
|
-- performed in the aborted subtransaction
|
|
|
|
begin;
|
|
|
|
savepoint x;
|
|
|
|
create table abc (a int);
|
|
|
|
insert into abc values (5);
|
|
|
|
insert into abc values (10);
|
|
|
|
declare foo cursor for select * from abc;
|
|
|
|
fetch from foo;
|
|
|
|
a
|
|
|
|
---
|
|
|
|
5
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
rollback to x;
|
|
|
|
-- should fail
|
|
|
|
fetch from foo;
|
|
|
|
ERROR: cursor "foo" does not exist
|
|
|
|
commit;
|
|
|
|
begin;
|
|
|
|
create table abc (a int);
|
|
|
|
insert into abc values (5);
|
|
|
|
insert into abc values (10);
|
|
|
|
insert into abc values (15);
|
|
|
|
declare foo cursor for select * from abc;
|
|
|
|
fetch from foo;
|
|
|
|
a
|
|
|
|
---
|
|
|
|
5
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
savepoint x;
|
|
|
|
fetch from foo;
|
|
|
|
a
|
|
|
|
----
|
|
|
|
10
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
rollback to x;
|
|
|
|
fetch from foo;
|
|
|
|
a
|
|
|
|
----
|
|
|
|
15
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
abort;
|
2012-02-15 22:18:34 +01:00
|
|
|
-- Test for successful cleanup of an aborted transaction at session exit.
|
|
|
|
-- THIS MUST BE THE LAST TEST IN THIS FILE.
|
|
|
|
begin;
|
|
|
|
select 1/0;
|
|
|
|
ERROR: division by zero
|
|
|
|
rollback to X;
|
|
|
|
ERROR: no such savepoint
|
|
|
|
-- DO NOT ADD ANYTHING HERE.
|