mirror of
https://github.com/postgres/postgres.git
synced 2025-05-18 17:41:14 +03:00
Fix breakages of hot standby regression test.
This commit changes HS regression test so that it uses REPEATABLE READ transaction instead of SERIALIZABLE one because SERIALIZABLE transaction isolation level is not available in HS. Also this commit fixes VACUUM/ANALYZE label mixup. This was fixed in HEAD (commit 2985e16), but it should have been back-patched to 9.1 which had introduced SSI and forbidden SERIALIZABLE transaction in HS. Amit Langote
This commit is contained in:
parent
780852ef00
commit
e2f02ed64e
@ -49,7 +49,7 @@ select count(*) as should_be_1 from hs1;
|
|||||||
(1 row)
|
(1 row)
|
||||||
|
|
||||||
end;
|
end;
|
||||||
begin transaction isolation level serializable;
|
begin transaction isolation level repeatable read;
|
||||||
select count(*) as should_be_1 from hs1;
|
select count(*) as should_be_1 from hs1;
|
||||||
should_be_1
|
should_be_1
|
||||||
-------------
|
-------------
|
||||||
|
@ -124,7 +124,7 @@ unlisten *;
|
|||||||
ERROR: cannot execute UNLISTEN during recovery
|
ERROR: cannot execute UNLISTEN during recovery
|
||||||
-- disallowed commands
|
-- disallowed commands
|
||||||
ANALYZE hs1;
|
ANALYZE hs1;
|
||||||
ERROR: cannot execute VACUUM during recovery
|
ERROR: cannot execute ANALYZE during recovery
|
||||||
VACUUM hs2;
|
VACUUM hs2;
|
||||||
ERROR: cannot execute VACUUM during recovery
|
ERROR: cannot execute VACUUM during recovery
|
||||||
CLUSTER hs2 using hs1_pkey;
|
CLUSTER hs2 using hs1_pkey;
|
||||||
|
@ -28,7 +28,7 @@ begin transaction read only;
|
|||||||
select count(*) as should_be_1 from hs1;
|
select count(*) as should_be_1 from hs1;
|
||||||
end;
|
end;
|
||||||
|
|
||||||
begin transaction isolation level serializable;
|
begin transaction isolation level repeatable read;
|
||||||
select count(*) as should_be_1 from hs1;
|
select count(*) as should_be_1 from hs1;
|
||||||
select count(*) as should_be_1 from hs1;
|
select count(*) as should_be_1 from hs1;
|
||||||
select count(*) as should_be_1 from hs1;
|
select count(*) as should_be_1 from hs1;
|
||||||
|
Loading…
x
Reference in New Issue
Block a user