Skip to content

Commit 388b959

Browse files
committed
Raise a timeout to 180s, in contrib/test_decoding.
Per buildfarm member hornet. The test is new in v14, so no back-patch.
1 parent 977b2c0 commit 388b959

File tree

2 files changed

+4
-6
lines changed

2 files changed

+4
-6
lines changed

contrib/test_decoding/expected/twophase.out

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -143,9 +143,8 @@ WHERE locktype = 'relation'
143143
test_prepared1 | relation | AccessExclusiveLock
144144
(3 rows)
145145

146-
-- The above CLUSTER command shouldn't cause a timeout on 2pc decoding. The
147-
-- call should return within a second.
148-
SET statement_timeout = '1s';
146+
-- The above CLUSTER command shouldn't cause a timeout on 2pc decoding.
147+
SET statement_timeout = '180s';
149148
SELECT data FROM pg_logical_slot_get_changes('regression_slot', NULL, NULL, 'two-phase-commit', '1', 'include-xids', '0', 'skip-empty-xacts', '1');
150149
data
151150
---------------------------------------------------------------------------

contrib/test_decoding/sql/twophase.sql

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -68,9 +68,8 @@ SELECT 'test_prepared1' AS relation, locktype, mode
6868
FROM pg_locks
6969
WHERE locktype = 'relation'
7070
AND relation = 'test_prepared1'::regclass;
71-
-- The above CLUSTER command shouldn't cause a timeout on 2pc decoding. The
72-
-- call should return within a second.
73-
SET statement_timeout = '1s';
71+
-- The above CLUSTER command shouldn't cause a timeout on 2pc decoding.
72+
SET statement_timeout = '180s';
7473
SELECT data FROM pg_logical_slot_get_changes('regression_slot', NULL, NULL, 'two-phase-commit', '1', 'include-xids', '0', 'skip-empty-xacts', '1');
7574
RESET statement_timeout;
7675
COMMIT PREPARED 'test_prepared_lock';

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy