forked from timescale/timescaledb
-
Notifications
You must be signed in to change notification settings - Fork 1
/
remote_txn.out
1296 lines (1087 loc) · 47.1 KB
/
remote_txn.out
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
-- This file and its contents are licensed under the Timescale License.
-- Please see the included NOTICE for copyright information and
-- LICENSE-TIMESCALE for a copy of the license.
-- ===================================================================
-- create FDW objects
-- ===================================================================
\c :TEST_DBNAME :ROLE_SUPERUSER
\ir include/remote_exec.sql
-- This file and its contents are licensed under the Timescale License.
-- Please see the included NOTICE for copyright information and
-- LICENSE-TIMESCALE for a copy of the license.
CREATE SCHEMA IF NOT EXISTS test;
psql:include/remote_exec.sql:5: NOTICE: schema "test" already exists, skipping
GRANT USAGE ON SCHEMA test TO PUBLIC;
CREATE OR REPLACE FUNCTION test.remote_exec(srv_name name[], command text)
RETURNS VOID
AS :TSL_MODULE_PATHNAME, 'ts_remote_exec'
LANGUAGE C;
CREATE OR REPLACE FUNCTION test.remote_exec_get_result_strings(srv_name name[], command text)
RETURNS TABLE("table_record" CSTRING[])
AS :TSL_MODULE_PATHNAME, 'ts_remote_exec_get_result_strings'
LANGUAGE C;
CREATE OR REPLACE FUNCTION remote_node_killer_set_event(text, text)
RETURNS VOID
AS :TSL_MODULE_PATHNAME, 'ts_remote_node_killer_set_event'
LANGUAGE C;
CREATE OR REPLACE FUNCTION test_remote_txn_persistent_record(srv_name name)
RETURNS VOID
AS :TSL_MODULE_PATHNAME, 'ts_test_remote_txn_persistent_record'
LANGUAGE C;
-- To ensure predictability, we want to kill the remote backend when it's in
-- the midst of processing the transaction. To ensure that the access node
-- sets the event handler and then takes an exclusive session lock on the
-- "remote_conn_xact_end" advisory lock via "debug_waitpoint_enable" function
--
-- The "RegisterXactCallback" callback on the remote backend tries to take
-- this same advisory lock in shared mode and waits. This allows the event
-- handler enough time to kill this remote backend at the right time
--
-- Don't forget to release lock via debug_waitpoint_release on the access node
-- since it's a session level advisory lock
--
CREATE OR REPLACE FUNCTION debug_waitpoint_enable(TEXT)
RETURNS VOID
AS :MODULE_PATHNAME, 'ts_debug_point_enable'
LANGUAGE C VOLATILE STRICT;
CREATE OR REPLACE FUNCTION debug_waitpoint_release(TEXT)
RETURNS VOID
AS :MODULE_PATHNAME, 'ts_debug_point_release'
LANGUAGE C VOLATILE STRICT;
CREATE OR REPLACE FUNCTION add_loopback_server(
server_name NAME,
host TEXT = 'localhost',
database NAME = current_database(),
port INTEGER = inet_server_port(),
if_not_exists BOOLEAN = FALSE,
bootstrap BOOLEAN = TRUE,
password TEXT = NULL
) RETURNS TABLE(server_name NAME, host TEXT, port INTEGER, database NAME,
server_created BOOL, database_created BOOL, extension_created BOOL)
AS :TSL_MODULE_PATHNAME, 'ts_unchecked_add_data_node'
LANGUAGE C;
SELECT server_name, database, server_created, database_created, extension_created FROM add_loopback_server('loopback', database => :'TEST_DBNAME', bootstrap => false);
server_name | database | server_created | database_created | extension_created
-------------+---------------+----------------+------------------+-------------------
loopback | db_remote_txn | t | f | f
(1 row)
SELECT server_name, database, server_created, database_created, extension_created FROM add_loopback_server('loopback2', database => :'TEST_DBNAME', bootstrap => false);
server_name | database | server_created | database_created | extension_created
-------------+---------------+----------------+------------------+-------------------
loopback2 | db_remote_txn | t | f | f
(1 row)
-- ===================================================================
-- create objects used through FDW loopback server
-- ===================================================================
CREATE SCHEMA "S 1";
CREATE TABLE "S 1"."T 1" (
"C 1" int NOT NULL,
c2 int NOT NULL,
c3 text,
c4 timestamptz,
c5 timestamp,
c6 varchar(10),
c7 char(10),
CONSTRAINT t1_pkey PRIMARY KEY ("C 1")
);
ANALYZE "S 1"."T 1";
INSERT INTO "S 1"."T 1"
SELECT id,
id % 10,
to_char(id, 'FM00000'),
'1970-01-01'::timestamptz + ((id % 100) || ' days')::interval,
'1970-01-01'::timestamp + ((id % 100) || ' days')::interval,
id % 10,
id % 10
FROM generate_series(1, 1000) id;
\set ON_ERROR_STOP 0
SELECT test_remote_txn_persistent_record('loopback');
test_remote_txn_persistent_record
-----------------------------------
(1 row)
-- ===================================================================
-- 1 pc tests
-- ===================================================================
--successfull transaction
SET timescaledb.enable_2pc = false;
--initially, there are no connections in the cache
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
(0 rows)
BEGIN;
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (20001,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
NOTICE: [loopback]: INSERT INTO "S 1"."T 1" VALUES (20001,1,'bleh', '2001-01-01', '2001-01-01', 'bleh')
remote_exec
-------------
(1 row)
--expect to see one connection in transaction state
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | INTRANS | 1 | f
(1 row)
COMMIT;
--connection should remain, idle
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | IDLE | 0 | f
(1 row)
SELECT count(*) FROM "S 1"."T 1" WHERE "C 1" = 20001;
count
-------
1
(1 row)
--aborted transaction
BEGIN;
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (20002,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
NOTICE: [loopback]: INSERT INTO "S 1"."T 1" VALUES (20002,1,'bleh', '2001-01-01', '2001-01-01', 'bleh')
remote_exec
-------------
(1 row)
--existing connection, in transaction
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | INTRANS | 1 | f
(1 row)
ROLLBACK;
--connection should remain, in idle state after rollback
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | IDLE | 0 | f
(1 row)
SELECT count(*) FROM "S 1"."T 1" WHERE "C 1" = 20002;
count
-------
0
(1 row)
--constraint violation
BEGIN;
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (20001,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
NOTICE: [loopback]: INSERT INTO "S 1"."T 1" VALUES (20001,1,'bleh', '2001-01-01', '2001-01-01', 'bleh')
ERROR: [loopback]: duplicate key value violates unique constraint "t1_pkey"
COMMIT;
-- Connection should remain after conflict, in idle state
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | IDLE | 0 | f
(1 row)
--the next few statements inject faults before the commit. They should all fail
--and be rolled back with no unresolved state
-- We set min message level to "error" since order of warnings generated
-- is different due to timing issues but check that the transaction was
-- rolled back after the commit.
SET client_min_messages TO error;
BEGIN;
SELECT remote_node_killer_set_event('pre-commit', 'loopback');
remote_node_killer_set_event
------------------------------
(1 row)
SELECT debug_waitpoint_enable('remote_conn_xact_end');
debug_waitpoint_enable
------------------------
(1 row)
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (20003,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
remote_exec
-------------
(1 row)
COMMIT;
ERROR: [loopback]: terminating connection due to administrator command
RESET client_min_messages;
SELECT debug_waitpoint_release('remote_conn_xact_end');
debug_waitpoint_release
-------------------------
(1 row)
-- Failed connection should be cleared
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
(0 rows)
SELECT count(*) FROM "S 1"."T 1" WHERE "C 1" = 20003;
count
-------
0
(1 row)
SELECT count(*) FROM pg_prepared_xacts;
count
-------
0
(1 row)
-- We set min message level to "error" since order of warnings generated
-- is different due to timing issues but check that the transaction was
-- rolled back after the commit.
SET client_min_messages TO error;
BEGIN;
SELECT remote_node_killer_set_event('waiting-commit', 'loopback');
remote_node_killer_set_event
------------------------------
(1 row)
SELECT debug_waitpoint_enable('remote_conn_xact_end');
debug_waitpoint_enable
------------------------
(1 row)
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (20004,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
remote_exec
-------------
(1 row)
--connection in transaction
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | INTRANS | 1 | f
(1 row)
COMMIT;
ERROR: [loopback]: terminating connection due to administrator command
RESET client_min_messages;
SELECT debug_waitpoint_release('remote_conn_xact_end');
debug_waitpoint_release
-------------------------
(1 row)
--connection failed during commit, so should be cleared from the cache
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
(0 rows)
--during waiting-commit the data node process could die before or after
--executing the commit on the remote node. So the behaviour here is non-deterministic
--this is the bad part of 1-pc transactions.
--there are no prepared txns in either case
SELECT count(*) FROM pg_prepared_xacts;
count
-------
0
(1 row)
--fail the connection before the abort
BEGIN;
SELECT remote_node_killer_set_event('pre-abort', 'loopback');
remote_node_killer_set_event
------------------------------
(1 row)
SELECT debug_waitpoint_enable('remote_conn_xact_end');
debug_waitpoint_enable
------------------------
(1 row)
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (20005,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
NOTICE: [loopback]: INSERT INTO "S 1"."T 1" VALUES (20005,1,'bleh', '2001-01-01', '2001-01-01', 'bleh')
remote_exec
-------------
(1 row)
--connection in transaction
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | INTRANS | 1 | f
(1 row)
-- since the error messages/warnings from this ROLLBACK varies between
-- platforms/environments we remove it from test output and show
-- SQLSTATE instead. SQLSTATE should be 00000 since we are not
-- throwing errors during rollback/abort and it should succeed in any
-- case.
\echo 'ROLLBACK SQLSTATE' :SQLSTATE
ROLLBACK SQLSTATE 00000
SELECT debug_waitpoint_release('remote_conn_xact_end');
debug_waitpoint_release
-------------------------
(1 row)
SELECT count(*) FROM "S 1"."T 1" WHERE "C 1" = 20005;
count
-------
0
(1 row)
SELECT count(*) FROM pg_prepared_xacts;
count
-------
0
(1 row)
--the failed connection should be cleared
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
(0 rows)
--block preparing transactions on the access node
BEGIN;
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (20006,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
NOTICE: [loopback]: INSERT INTO "S 1"."T 1" VALUES (20006,1,'bleh', '2001-01-01', '2001-01-01', 'bleh')
remote_exec
-------------
(1 row)
PREPARE TRANSACTION 'test-2';
ERROR: cannot prepare a transaction that modified remote tables
-- ===================================================================
-- 2 pc tests
-- ===================================================================
--undo changes from 1-pc tests
DELETE FROM "S 1"."T 1" where "C 1" >= 20000;
SET timescaledb.enable_2pc = true;
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | IDLE | 0 | f
(1 row)
--simple commit
BEGIN;
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (10001,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
NOTICE: [loopback]: INSERT INTO "S 1"."T 1" VALUES (10001,1,'bleh', '2001-01-01', '2001-01-01', 'bleh')
remote_exec
-------------
(1 row)
--connection in transaction
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | INTRANS | 1 | f
(1 row)
COMMIT;
--connection should remain in idle state
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | IDLE | 0 | f
(1 row)
SELECT count(*) FROM "S 1"."T 1" WHERE "C 1" = 10001;
count
-------
1
(1 row)
SELECT count(*) FROM pg_prepared_xacts;
count
-------
0
(1 row)
--simple
BEGIN;
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (11001,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
NOTICE: [loopback]: INSERT INTO "S 1"."T 1" VALUES (11001,1,'bleh', '2001-01-01', '2001-01-01', 'bleh')
remote_exec
-------------
(1 row)
--connection in transaction
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | INTRANS | 1 | f
(1 row)
ROLLBACK;
--rolled back transaction, but connection should remain in idle
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | IDLE | 0 | f
(1 row)
SELECT count(*) FROM "S 1"."T 1" WHERE "C 1" = 11001;
count
-------
0
(1 row)
SELECT count(*) FROM pg_prepared_xacts;
count
-------
0
(1 row)
--constraint violation should fail the txn
BEGIN;
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (10001,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
NOTICE: [loopback]: INSERT INTO "S 1"."T 1" VALUES (10001,1,'bleh', '2001-01-01', '2001-01-01', 'bleh')
ERROR: [loopback]: duplicate key value violates unique constraint "t1_pkey"
COMMIT;
--connection should remain in idle after constraint violation
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | IDLE | 0 | f
(1 row)
--the next few statements inject faults before the commit. They should all fail
--and be rolled back with no unresolved state
BEGIN;
SELECT remote_node_killer_set_event('pre-prepare-transaction', 'loopback');
remote_node_killer_set_event
------------------------------
(1 row)
SELECT debug_waitpoint_enable('remote_conn_xact_end');
debug_waitpoint_enable
------------------------
(1 row)
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (10002,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
NOTICE: [loopback]: INSERT INTO "S 1"."T 1" VALUES (10002,1,'bleh', '2001-01-01', '2001-01-01', 'bleh')
remote_exec
-------------
(1 row)
-- since the error messages/warnings from this COMMIT varies between
-- platforms/environments we remove it from test output and show SQLSTATE instead.
-- SQLSTATE should be 08006 connection_failure
\echo 'COMMIT SQLSTATE' :SQLSTATE
COMMIT SQLSTATE 08006
SELECT debug_waitpoint_release('remote_conn_xact_end');
debug_waitpoint_release
-------------------------
(1 row)
--the connection was killed, so should be cleared
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
(0 rows)
SELECT count(*) FROM "S 1"."T 1" WHERE "C 1" = 10002;
count
-------
0
(1 row)
SELECT count(*) FROM pg_prepared_xacts;
count
-------
0
(1 row)
BEGIN;
SELECT remote_node_killer_set_event('waiting-prepare-transaction', 'loopback');
remote_node_killer_set_event
------------------------------
(1 row)
SELECT debug_waitpoint_enable('remote_conn_xact_end');
debug_waitpoint_enable
------------------------
(1 row)
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (10003,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
NOTICE: [loopback]: INSERT INTO "S 1"."T 1" VALUES (10003,1,'bleh', '2001-01-01', '2001-01-01', 'bleh')
remote_exec
-------------
(1 row)
-- since the error messages/warnings from this COMMIT varies between
-- platforms/environments we remove it from test output and show SQLSTATE instead.
-- SQLSTATE should be 08006 connection_failure
\echo 'COMMIT SQLSTATE' :SQLSTATE
COMMIT SQLSTATE 08006
SELECT debug_waitpoint_release('remote_conn_xact_end');
debug_waitpoint_release
-------------------------
(1 row)
--the connection should be cleared from the cache
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
(0 rows)
SELECT count(*) FROM "S 1"."T 1" WHERE "C 1" = 10003;
count
-------
0
(1 row)
--during waiting-prepare-transaction the data node process could die before or after
--executing the prepare transaction. To be safe to either case rollback using heal_server.
SELECT * FROM _timescaledb_internal.remote_txn_heal_data_node((SELECT OID FROM pg_foreign_server WHERE srvname = 'loopback'));
remote_txn_heal_data_node
---------------------------
0
(1 row)
SELECT count(*) FROM pg_prepared_xacts;
count
-------
0
(1 row)
SELECT count(*) from _timescaledb_catalog.remote_txn;
count
-------
0
(1 row)
--the following only breaks stuff in post-commit so commit should succeed
--but leave transaction in an unresolved state.
BEGIN;
SELECT remote_node_killer_set_event('post-prepare-transaction', 'loopback');
remote_node_killer_set_event
------------------------------
(1 row)
SELECT debug_waitpoint_enable('remote_conn_xact_end');
debug_waitpoint_enable
------------------------
(1 row)
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (10004,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
NOTICE: [loopback]: INSERT INTO "S 1"."T 1" VALUES (10004,1,'bleh', '2001-01-01', '2001-01-01', 'bleh')
remote_exec
-------------
(1 row)
-- since the error messages/warnings from this COMMIT varies between
-- platforms/environments we remove it from test output and show SQLSTATE instead.
-- SQLSTATE should be 00000 successful_completion
\echo 'COMMIT SQLSTATE' :SQLSTATE
COMMIT SQLSTATE 00000
SELECT debug_waitpoint_release('remote_conn_xact_end');
debug_waitpoint_release
-------------------------
(1 row)
--connection should be cleared
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
(0 rows)
--unresolved state shown here
SELECT count(*) FROM "S 1"."T 1" WHERE "C 1" = 10004;
count
-------
0
(1 row)
SELECT count(*) FROM pg_prepared_xacts;
count
-------
1
(1 row)
--this fails because heal cannot run inside txn block
BEGIN;
SELECT _timescaledb_internal.remote_txn_heal_data_node((SELECT OID FROM pg_foreign_server WHERE srvname = 'loopback'));
ERROR: remote_txn_heal_data_node cannot run inside a transaction block
COMMIT;
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
(0 rows)
select count(*) from _timescaledb_catalog.remote_txn;
count
-------
1
(1 row)
--this resolves the previous txn
SELECT _timescaledb_internal.remote_txn_heal_data_node((SELECT OID FROM pg_foreign_server WHERE srvname = 'loopback'));
remote_txn_heal_data_node
---------------------------
1
(1 row)
SELECT count(*) FROM "S 1"."T 1" WHERE "C 1" = 10004;
count
-------
1
(1 row)
SELECT count(*) FROM pg_prepared_xacts;
count
-------
0
(1 row)
--cleanup also happened
select count(*) from _timescaledb_catalog.remote_txn;
count
-------
0
(1 row)
BEGIN;
SELECT remote_node_killer_set_event('pre-commit-prepared', 'loopback');
remote_node_killer_set_event
------------------------------
(1 row)
SELECT debug_waitpoint_enable('remote_conn_xact_end');
debug_waitpoint_enable
------------------------
(1 row)
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (10006,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
NOTICE: [loopback]: INSERT INTO "S 1"."T 1" VALUES (10006,1,'bleh', '2001-01-01', '2001-01-01', 'bleh')
remote_exec
-------------
(1 row)
-- since the error messages/warnings from this COMMIT varies between
-- platforms/environments we remove it from test output and show SQLSTATE instead.
-- SQLSTATE should be 00000 successful_completion
\echo 'COMMIT SQLSTATE' :SQLSTATE
COMMIT SQLSTATE 00000
SELECT debug_waitpoint_release('remote_conn_xact_end');
debug_waitpoint_release
-------------------------
(1 row)
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
(0 rows)
--unresolved state shown here
SELECT count(*) FROM "S 1"."T 1" WHERE "C 1" = 10006;
count
-------
0
(1 row)
SELECT count(*) FROM pg_prepared_xacts;
count
-------
1
(1 row)
--this resolves the previous txn
SELECT _timescaledb_internal.remote_txn_heal_data_node((SELECT OID FROM pg_foreign_server WHERE srvname = 'loopback'));
remote_txn_heal_data_node
---------------------------
1
(1 row)
SELECT count(*) FROM "S 1"."T 1" WHERE "C 1" = 10006;
count
-------
1
(1 row)
SELECT count(*) FROM pg_prepared_xacts;
count
-------
0
(1 row)
select count(*) from _timescaledb_catalog.remote_txn;
count
-------
0
(1 row)
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
(0 rows)
BEGIN;
SELECT remote_node_killer_set_event('waiting-commit-prepared','loopback');
remote_node_killer_set_event
------------------------------
(1 row)
SELECT debug_waitpoint_enable('remote_conn_xact_end');
debug_waitpoint_enable
------------------------
(1 row)
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (10005,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
NOTICE: [loopback]: INSERT INTO "S 1"."T 1" VALUES (10005,1,'bleh', '2001-01-01', '2001-01-01', 'bleh')
remote_exec
-------------
(1 row)
-- since the error messages/warnings from this COMMIT varies between
-- platforms/environments we remove it from test output and show SQLSTATE instead.
-- SQLSTATE should be 00000 successful_completion
\echo 'COMMIT SQLSTATE' :SQLSTATE
COMMIT SQLSTATE 00000
SELECT debug_waitpoint_release('remote_conn_xact_end');
debug_waitpoint_release
-------------------------
(1 row)
--at this point the commit prepared might or might not have been executed before
--the data node process was killed.
--but in any case, healing the server will bring it into a known state
SELECT * FROM _timescaledb_internal.remote_txn_heal_data_node((SELECT OID FROM pg_foreign_server WHERE srvname = 'loopback'));
remote_txn_heal_data_node
---------------------------
1
(1 row)
--heal does not use the connection cache, so unaffected
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
(0 rows)
SELECT count(*) FROM "S 1"."T 1" WHERE "C 1" = 10005;
count
-------
1
(1 row)
SELECT count(*) FROM pg_prepared_xacts;
count
-------
0
(1 row)
select count(*) from _timescaledb_catalog.remote_txn;
count
-------
0
(1 row)
--test prepare transactions. Note that leaked prepared stmts should be
--detected by `remote_txn_check_for_leaked_prepared_statements` so we
--should be fine if we don't see any WARNINGS.
BEGIN;
SELECT test.remote_exec('{loopback}', $$ PREPARE prep_1 AS SELECT 1 $$);
NOTICE: [loopback]: PREPARE prep_1 AS SELECT 1
remote_exec
-------------
(1 row)
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (10001,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
NOTICE: [loopback]: INSERT INTO "S 1"."T 1" VALUES (10001,1,'bleh', '2001-01-01', '2001-01-01', 'bleh')
ERROR: [loopback]: duplicate key value violates unique constraint "t1_pkey"
COMMIT;
--unique constraint violation, connection should remain
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | IDLE | 0 | f
(1 row)
BEGIN;
SAVEPOINT save_1;
SELECT test.remote_exec('{loopback}', $$ PREPARE prep_1 AS SELECT 1 $$);
NOTICE: [loopback]: PREPARE prep_1 AS SELECT 1
remote_exec
-------------
(1 row)
--connection in transaction state
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | INTRANS | 2 | f
(1 row)
--generate a unique violation
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (10001,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
NOTICE: [loopback]: INSERT INTO "S 1"."T 1" VALUES (10001,1,'bleh', '2001-01-01', '2001-01-01', 'bleh')
ERROR: [loopback]: duplicate key value violates unique constraint "t1_pkey"
ROLLBACK TO SAVEPOINT save_1;
--for correctness, the connection must remain after rollback since
--the transaction is still ongoing
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | INTRANS | 1 | f
(1 row)
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (81,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
NOTICE: [loopback]: INSERT INTO "S 1"."T 1" VALUES (81,1,'bleh', '2001-01-01', '2001-01-01', 'bleh')
ERROR: [loopback]: duplicate key value violates unique constraint "t1_pkey"
COMMIT;
--connection should remain and be idle
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | IDLE | 0 | f
(1 row)
SELECT count(*) FROM "S 1"."T 1" WHERE "C 1" = 81;
count
-------
1
(1 row)
--Make the primary key DEFERRABLE and INITIALLY DEFERRED
--this is a way to force errors to happen during PREPARE TRANSACTION
--since pkey constraint violations would not occur on the INSERT command
--but rather are deferred till PREPARE TRANSACTION happens.
ALTER TABLE "S 1"."T 1" DROP CONSTRAINT t1_pkey,
ADD CONSTRAINT t1_pkey PRIMARY KEY ("C 1") DEFERRABLE INITIALLY DEFERRED;
--test ROLLBACK TRANSACTION on failure in PREPARE TRANSACTION.
-- We set min message level to "error" since order of warnings generated
-- is different due to timing issues but check that the transaction was
-- rolled back after the commit.
SET client_min_messages TO error;
BEGIN;
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (10001,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
remote_exec
-------------
(1 row)
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | INTRANS | 1 | f
(1 row)
COMMIT;
ERROR: [loopback]: duplicate key value violates unique constraint "t1_pkey"
RESET client_min_messages;
--connection should be removed since PREPARE TRANSACTION failed
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
(0 rows)
SELECT count(*) FROM pg_prepared_xacts;
count
-------
0
(1 row)
--test ROLLBACK TRANSACTION
--this has an error on the second connection. So should force conn1 to prepare transaction
--ok and then have the txn fail on conn2. Thus conn1 would do a ROLLBACK PREPARED.
--conn2 would do a ROLLBACK TRANSACTION.
-- We set min message level to "error" since order of warnings generated
-- is different due to timing issues but check that the transaction was
-- rolled back after the commit.
SET client_min_messages TO error;
BEGIN;
SELECT test.remote_exec('{loopback}', $$ INSERT INTO "S 1"."T 1" VALUES (10010,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
remote_exec
-------------
(1 row)
SELECT test.remote_exec('{loopback2}', $$ INSERT INTO "S 1"."T 1" VALUES (10001,1,'bleh', '2001-01-01', '2001-01-01', 'bleh') $$);
remote_exec
-------------
(1 row)
--Both connections in transaction state
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | INTRANS | 1 | f
loopback2 | OK | INTRANS | 1 | f
(2 rows)
COMMIT;
ERROR: [loopback2]: duplicate key value violates unique constraint "t1_pkey"
RESET client_min_messages;
--one connection should remain and be idle
SELECT node_name, connection_status, transaction_status, transaction_depth, processing
FROM _timescaledb_internal.show_connection_cache() ORDER BY 1,4;
node_name | connection_status | transaction_status | transaction_depth | processing
-----------+-------------------+--------------------+-------------------+------------
loopback | OK | IDLE | 0 | f
(1 row)
SELECT count(*) FROM "S 1"."T 1" WHERE "C 1" = 10010;
count
-------
0
(1 row)
SELECT count(*) FROM pg_prepared_xacts;
count
-------