FYI, After applying only the 0001 patch I received a TAP test error.
t/032_subscribe_use_index.pl ....... 1/? # Tests were run but no plan was declared and done_testing() was not seen. t/032_subscribe_use_index.pl ....... Dubious, test returned 29 (wstat 7424, 0x1d00) All 1 subtests passed t/100_bugs.pl ...................... ok More details: 2023-03-03 12:45:45.382 AEDT [9931] 032_subscribe_use_index.pl LOG: statement: CREATE INDEX test_replica_id_full_idx ON test_replica_id_full(x) 2023-03-03 12:45:45.423 AEDT [9937] 032_subscribe_use_index.pl LOG: statement: CREATE SUBSCRIPTION tap_sub_rep_full CONNECTION 'port=56538 host=/tmp/zWyRQnOa1a dbname=postgres application_name=tap_sub' PUBLICATION tap_pub_rep_full WITH (enable_index_scan = false) 2023-03-03 12:45:45.423 AEDT [9937] 032_subscribe_use_index.pl ERROR: unrecognized subscription parameter: "enable_index_scan" 2023-03-03 12:45:45.423 AEDT [9937] 032_subscribe_use_index.pl STATEMENT: CREATE SUBSCRIPTION tap_sub_rep_full CONNECTION 'port=56538 host=/tmp/zWyRQnOa1a dbname=postgres application_name=tap_sub' PUBLICATION tap_pub_rep_full WITH (enable_index_scan = false) 2023-03-03 12:45:45.532 AEDT [9834] LOG: received immediate shutdown request 2023-03-03 12:45:45.533 AEDT [9834] LOG: database system is shut down ~~ The patches 0001 and 0002 seem to have accidentally blended together because AFAICT the error is because patch 0001 is testing something that is not available until 0002. ------ Kind Regards, Peter Smith. Fujitsu Australia