Known Buildfarm Test Failures - Archive

Fixed Test Failures - 2024

partition_split.sql contains queries producing unstable results

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=jackdaw&dt=2024-05-24%2015%3A58%3A17 - HEAD

--- /home/debian/17-jackdaw/buildroot/HEAD/pgsql.build/src/test/regress/expected/partition_split.out	2024-05-24 15:58:23.929113215 +0000
+++ /home/debian/17-jackdaw/buildroot/HEAD/pgsql.build/src/test/regress/results/partition_split.out	2024-05-24 16:05:58.286542479 +0000
@@ -637,15 +637,15 @@
 SELECT pg_get_constraintdef(oid), conname, conkey FROM pg_constraint WHERE conrelid = 'sales_feb2022'::regclass::oid;
                         pg_get_constraintdef                         |             conname             | conkey 
 ---------------------------------------------------------------------+---------------------------------+--------
- CHECK ((sales_amount > 1))                                          | sales_range_sales_amount_check  | {2}
  FOREIGN KEY (salesperson_id) REFERENCES salespeople(salesperson_id) | sales_range_salesperson_id_fkey | {1}
+ CHECK ((sales_amount > 1))                                          | sales_range_sales_amount_check  | {2}
 (2 rows)
 
 SELECT pg_get_constraintdef(oid), conname, conkey FROM pg_constraint WHERE conrelid = 'sales_mar2022'::regclass::oid;
                         pg_get_constraintdef                         |             conname             | conkey 
 ---------------------------------------------------------------------+---------------------------------+--------
- CHECK ((sales_amount > 1))                                          | sales_range_sales_amount_check  | {2}
  FOREIGN KEY (salesperson_id) REFERENCES salespeople(salesperson_id) | sales_range_salesperson_id_fkey | {1}
+ CHECK ((sales_amount > 1))                                          | sales_range_sales_amount_check  | {2}
 (2 rows)
 
 SELECT pg_get_constraintdef(oid), conname, conkey FROM pg_constraint WHERE conrelid = 'sales_apr2022'::regclass::oid;

Add SPLIT PARTITION/MERGE PARTITIONS commands \ the test unstable results

Provide deterministic order for catalog queries in partition_split.sql

026_overwrite_contrecord.pl and 033_replay_tsp_drops.pl trigger Assert("ItemIdIsNormal(lpp)")

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=adder&dt=2024-06-04%2003%3A27%3A47 - HEAD

  29/295 postgresql:recovery / recovery/026_overwrite_contrecord ERROR            39.55s   exit status 32

---
026_overwrite_contrecord_standby.log
TRAP: failed Assert("ItemIdIsNormal(lpp)"), File: "../pgsql/src/backend/access/heap/heapam.c", Line: 1002, PID: 3740958
postgres: standby: bf postgres [local] startup(ExceptionalCondition+0x81)[0x56c60bf9]
postgres: standby: bf postgres [local] startup(+0xf776e)[0x5667276e]
postgres: standby: bf postgres [local] startup(heap_getnextslot+0x40)[0x56672ee1]
postgres: standby: bf postgres [local] startup(+0x11c218)[0x56697218]
postgres: standby: bf postgres [local] startup(systable_getnext+0xfa)[0x56697c1a]
postgres: standby: bf postgres [local] startup(+0x6d29c7)[0x56c4d9c7]
postgres: standby: bf postgres [local] startup(+0x6d372c)[0x56c4e72c]
postgres: standby: bf postgres [local] startup(+0x6d8288)[0x56c53288]
postgres: standby: bf postgres [local] startup(RelationCacheInitializePhase3+0x149)[0x56c52d71]

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=calliphoridae&dt=2024-04-03%2003%3A32%3A18 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=tamandua&dt=2024-04-04%2015%3A38%3A16 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=margay&dt=2024-05-07%2004%3A00%3A08 - HEAD

Assert in heapgettup_pagemode() fails due to underlying buffer change

Hot standby queries see transient all-zeros pages

Fix RBM_ZERO_AND_LOCK.

040_pg_createsubscriber.pl fails due to error: could not obtain replication slot information

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2024-06-06%2000%3A32%3A20 - HEAD

stderr:
#   Failed test 'run pg_createsubscriber --dry-run on node S'
#   at /home/bf/bf-build/culicidae/HEAD/pgsql/src/bin/pg_basebackup/t/040_pg_createsubscriber.pl line 264.
# Looks like you failed 1 test of 31.

---
regress_log_040_pg_createsubscriber
[00:38:25.368](1.063s) ok 23 - standby contains unmet conditions on node S
...
# Running: pg_createsubscriber --verbose --dry-run ...
...
pg_createsubscriber: checking settings on publisher
2024-06-06 00:38:26.895 UTC [4001283][client backend][:0] LOG:  disconnection: session time: 0:00:00.028 user=bf database=pg1 host=[local]
pg_createsubscriber: error: could not obtain replication slot information: got 0 rows, expected 1 row
...
pg_createsubscriber: server was stopped
[00:38:27.352](1.984s) not ok 24 - run pg_createsubscriber --dry-run on node S
[00:38:27.355](0.004s) #   Failed test 'run pg_createsubscriber --dry-run on node S'
#   at /home/bf/bf-build/culicidae/HEAD/pgsql/src/bin/pg_basebackup/t/040_pg_createsubscriber.pl line 264.

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2024-06-12%2000%3A58%3A32 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2024-06-17%2008%3A00%3A02 - HEAD

speed up a logical replica setup \ analysis for two failures

pg_createsubscriber: Remove replication slot check on primary

plperl.sql failing in v15- on caiman with a newer Perl version

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=caiman&dt=2024-06-23%2003%3A52%3A53 - REL_15_STABLE

(caiman is running on Fedora Rawhide with Perl 5.40)

--- /repos/build-farm-17/REL_13_STABLE/pgsql.build/src/pl/plperl/expected/plperl.out	2024-06-23 21:35:07.618704257 -0300
+++ /repos/build-farm-17/REL_13_STABLE/pgsql.build/src/pl/plperl/results/plperl.out	2024-06-23 21:59:11.425256754 -0300
@@ -706,7 +706,8 @@
 CONTEXT:  PL/Perl anonymous code block
 -- check that eval is allowed and eval'd restricted ops are caught
 DO $$ eval q{chdir '.';}; warn "Caught: $@"; $$ LANGUAGE plperl;
-WARNING:  Caught: 'chdir' trapped by operation mask at line 1.
+ERROR:  'eval hints' trapped by operation mask at line 1.
+CONTEXT:  PL/Perl anonymous code block

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=caiman&dt=2024-06-24%2001%3A34%3A23 - REL_15_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=caiman&dt=2024-06-25%2001%3A21%3A03 - REL_15_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=caiman&dt=2024-06-23%2003%3A51%3A53 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=caiman&dt=2024-06-24%2000%3A59%3A30 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=caiman&dt=2024-06-25%2000%3A48%3A40 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=caiman&dt=2024-06-23%2003%3A50%3A53 - REL_13_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=caiman&dt=2024-06-24%2000%3A35%3A06 - REL_13_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=caiman&dt=2024-06-23%2003%3A49%3A53 - REL_12_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=caiman&dt=2024-06-24%2000%3A15%3A16 - REL_12_STABLE

Buildfarm animal caiman showing a plperl test issue with newer Perl versions

Remove redundant perl version checks

inplace-inval.spec fails on prion and trilobite on checking relhasindex

(prion run tests with -DCATCACHE_FORCE_RELEASE, trilobite with -DCLOBBER_CACHE_ALWAYS)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2024-06-28%2002%3A38%3A03 - HEAD

not ok 40    - inplace-inval                             141 ms

regression.diffs
---
--- /home/ec2-user/bf/root/HEAD/pgsql/src/test/isolation/expected/inplace-inval.out	2024-06-28 02:38:07.965133814 +0000
+++ /home/ec2-user/bf/root/HEAD/pgsql.build/src/test/isolation/output_iso/results/inplace-inval.out	2024-06-28 04:50:14.086521986 +0000
@@ -14,7 +14,7 @@
 
 relhasindex
 -----------
-f          
+t          
 (1 row)

race condition in pg_class \ -DCATCACHE_FORCE_RELEASE affects testing an extant failure to inval a cache entry

Remove configuration-dependent output from new inplace-inval test.

040_pg_createsubscriber.pl fails on Windows due to unterminated quoted string

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-06-30%2018%3A03%3A06 - HEAD

 93/242 postgresql:pg_basebackup / pg_basebackup/040_pg_createsubscriber                ERROR             7.95s   exit status 2
...
stderr:
# Tests were run but no plan was declared and done_testing() was not seen.

# Looks like your test exited with 2 just after 19.

---
regress_log_040_pg_createsubscriber
[18:15:28.475](4.206s) ok 18 - created database with ASCII characters from 1 to 45
# Running: createdb regression./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ
[18:15:28.801](0.327s) ok 19 - created database with ASCII characters from 46 to 90
connection error: 'psql: error: unterminated quoted string in connection info string'
while running 'psql -XAtq -d port=52984 host=C:/tools/nmsys64/tmp/hHg_pngw4z dbname='regression\\\\"\\\\�������	�������������������� !"#$%&\\'()*+,-\\\\\\\\"\\\\\\\\\\\\' -f - -v ON_ERROR_STOP=1' at C:/tools/nmsys64/home/pgrunner/bf/root/HEAD/pgsql/src/test/perl/PostgreSQL/Test/Cluster.pm line 2124.
# Postmaster PID for node "node_p" is 916
### Stopping node "node_p" using mode immediate
# Running: pg_ctl -D C:\\tools\\nmsys64\\home\\pgrunner\\bf\\root\\HEAD\\pgsql.build/testrun/pg_basebackup/040_pg_createsubscriber/data/t_040_pg_createsubscriber_node_p_data/pgdata -m immediate stop
waiting for server to shut down.... done
server stopped
# No postmaster PID for node "node_p"
# No postmaster PID for node "node_f"
[18:15:29.072](0.271s) # Tests were run but no plan was declared and done_testing() was not seen.
[18:15:29.073](0.001s) # Looks like your test exited with 2 just after 19.

speed up a logical replica setup \ b3f5ccebd blew up on fairywren

Temporarily(?) weaken new pg_createsubscriber test on Windows.
Further weaken new pg_createsubscriber test on Windows.

prepare.sql fails with ERROR: out of memory

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dhole&dt=2024-07-02%2008%3A01%3A13 - HEAD

not ok 193   + prepare                                   989 ms

--- /home/centos/build-farm-17-dhole/buildroot/HEAD/pgsql.build/src/test/regress/expected/prepare.out	2024-07-02 08:01:35.653580689 +0000
+++ /home/centos/build-farm-17-dhole/buildroot/HEAD/pgsql.build/src/test/regress/results/prepare.out	2024-07-02 08:12:46.599290163 +0000
@@ -186,9 +186,8 @@
 
---
regression.diffs:
 -- max parameter number and one above
 PREPARE q9 AS SELECT $268435455, $268435456;
-ERROR:  there is no parameter $268435456
-LINE 1: PREPARE q9 AS SELECT $268435455, $268435456;
-                                         ^
+ERROR:  out of memory
+DETAIL:  Failed on request of size 1073741820 in memory context "PortalContext".
 -- test DEALLOCATE ALL;

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=morepork&dt=2024-07-02%2008%3A30%3A38 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=schnauzer&dt=2024-07-02%2008%3A31%3A34 - HEAD

Underscore in positional parameters? \ some build farm machines running out of memory with the new test case

Remove too demanding test

040_pg_createsubscriber.pl fails when flushed position lagging behind on pg_sync_replication_slots()

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=piculet&dt=2024-06-28%2004%3A42%3A48 - HEAD

163/295 postgresql:pg_basebackup / pg_basebackup/040_pg_createsubscriber                ERROR            26.03s   exit status 29
...
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 29 just after 23.

---
regress_log_040_pg_createsubscriber
[04:46:20.321](0.703s) ok 23 - standby contains unmet conditions on node S
### Restarting node "node_p"
# Running: pg_ctl -w -D /home/bf/bf-build/piculet/HEAD/pgsql.build/testrun/pg_basebackup/040_pg_createsubscriber/data/t_040_pg_createsubscriber_node_p_data/pgdata -l /home/bf/bf-build/piculet/HEAD/pgsql.build/testrun/pg_basebackup/040_pg_createsubscriber/log/040_pg_createsubscriber_node_p.log restart
waiting for server to shut down.... done
server stopped
waiting for server to start.... done
server started
# Postmaster PID for node "node_p" is 415642
### Starting node "node_s"
# Running: pg_ctl -w -D /home/bf/bf-build/piculet/HEAD/pgsql.build/testrun/pg_basebackup/040_pg_createsubscriber/data/t_040_pg_createsubscriber_node_s_data/pgdata -l /home/bf/bf-build/piculet/HEAD/pgsql.build/testrun/pg_basebackup/040_pg_createsubscriber/log/040_pg_createsubscriber_node_s.log -o --cluster-name=node_s start
waiting for server to start.... done
server started
# Postmaster PID for node "node_s" is 416482
error running SQL: 'psql:<stdin>:1: ERROR:  skipping slot synchronization as the received slot sync LSN 0/30047F0 for slot "failover_slot" is ahead of the standby position 0/3004708'
while running 'psql -XAtq -d port=51506 host=/tmp/pqWohdD5Qj dbname='postgres' -f - -v ON_ERROR_STOP=1' with sql 'SELECT pg_sync_replication_slots()' at /home/bf/bf-build/piculet/HEAD/pgsql/src/test/perl/PostgreSQL/Test/Cluster.pm line 2126.

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2024-07-01%2006%3A55%3A38 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2024-07-02%2008%3A46%3A00 - HEAD

Also 040_pg_createsubscriber.pl fails due to autovacuum

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=adder&dt=2024-07-02%2008%3A45%3A39 - HEAD

162/295 postgresql:pg_basebackup / pg_basebackup/040_pg_createsubscriber                ERROR            81.93s   exit status 1

#   Failed test 'failover slot is synced'
#   at /home/bf/bf-build/adder/HEAD/pgsql/src/bin/pg_basebackup/t/040_pg_createsubscriber.pl line 300.
#          got: ''
#     expected: 'failover_slot'
# Looks like you failed 1 test of 36.

---
regress_log_040_pg_createsubscriber
[08:53:55.718](3.371s) not ok 26 - failover slot is synced
[08:53:55.718](0.001s) #   Failed test 'failover slot is synced'
#   at /home/bf/bf-build/adder/HEAD/pgsql/src/bin/pg_basebackup/t/040_pg_createsubscriber.pl line 300.
[08:53:55.719](0.000s) #          got: ''
#     expected: 'failover_slot'

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2024-07-02%2018%3A06%3A00 - HEAD

New instability of the 040_pg_createsubscriber test

Fix the testcase introduced in commit 81d20fbf7a.

misc_functions.sql fails due to JIT-related plan info added with low jit thresholds

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bushmaster&dt=2024-07-09%2000%3A00%3A13 - HEAD

not ok 138   + misc_functions                            188 ms
...
# 1 of 223 tests failed.

---
regression.diffs
--- /home/bf/bf-build/bushmaster/HEAD/pgsql/src/test/regress/expected/misc_functions.out	2024-07-09 00:00:11.692649130 +0000
+++ /home/bf/bf-build/bushmaster/HEAD/pgsql.build/src/test/regress/results/misc_functions.out	2024-07-09 00:02:05.252863892 +0000
@@ -641,7 +641,10 @@
                                     explain_mask_costs                                    
 ------------------------------------------------------------------------------------------
  Function Scan on generate_series g  (cost=N..N rows=30 width=N) (actual rows=30 loops=1)
-(1 row)
+ JIT:
+   Functions: 3
+   Options: Inlining false, Optimization false, Expressions true, Deforming true
+(4 rows)
...

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=taipan&dt=2024-07-09%2000%3A07%3A59 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bushmaster&dt=2024-07-09%2000%3A17%3A47 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=taipan&dt=2024-07-09%2000%3A23%3A00 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=taipan&dt=2024-07-09%2000%3A39%3A55 - HEAD

pgsql: Teach planner how to estimate rows for timestamp generate_series \ Fixing bushmaster failures

ssl tests (001_ssltests.pl, 002_scram.pl, 003_sslinfo.pl) fail due to TCP port conflict

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=kestrel&dt=2024-06-04%2011%3A20%3A07 - HEAD

287/295 postgresql:ssl / ssl/001_ssltests                                               ERROR             6.18s   (exit status 255 or signal 127 SIGinvalid)

---
001_ssltests_primary.log
2024-06-04 11:30:40.227 UTC [3373644][postmaster][:0] LOG:  starting PostgreSQL 17beta1 on x86_64-linux, compiled by clang-13.0.1-11, 64-bit
2024-06-04 11:30:40.231 UTC [3373644][postmaster][:0] LOG:  listening on Unix socket "/tmp/tUmT8ItNQ2/.s.PGSQL.60362"
...
2024-06-04 11:30:45.273 UTC [3376046][postmaster][:0] LOG:  starting PostgreSQL 17beta1 on x86_64-linux, compiled by clang-13.0.1-11, 64-bit
2024-06-04 11:30:45.273 UTC [3376046][postmaster][:0] LOG:  could not bind IPv4 address "127.0.0.1": Address already in use
2024-06-04 11:30:45.273 UTC [3376046][postmaster][:0] HINT:  Is another postmaster already running on port 60362? If not, wait a few seconds and retry.
2024-06-04 11:30:45.273 UTC [3376046][postmaster][:0] WARNING:  could not create listen socket for "127.0.0.1"
2024-06-04 11:30:45.273 UTC [3376046][postmaster][:0] FATAL:  could not create any TCP/IP sockets

ssl tests fail due to TCP port conflict

Also kerberos/001_auth due to UDP/TCP port conflict

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rorqual&dt=2024-07-02%2009%3A27%3A15 - HEAD

\342\226\266  28/295 command "/usr/sbin/krb5kdc -P /home/bf/bf-build/rorqual/HEAD/pgsql.build/testrun/kerberos/001_auth/data/krb5kdc.pid" exited with value 1 ERROR         
 28/295 postgresql:kerberos / kerberos/001_auth                                         ERROR             4.43s   (exit status 255 or signal 127 SIGinvalid)

---
krb5kdc.log
Jul 02 09:29:41 andres-postgres-buildfarm-v5 krb5kdc[471964](info): setting up network...
Jul 02 09:29:41 andres-postgres-buildfarm-v5 krb5kdc[471964](Error): Address already in use - Cannot bind server socket on 127.0.0.1.55853
Jul 02 09:29:41 andres-postgres-buildfarm-v5 krb5kdc[471964](Error): Failed setting up a UDP socket (for 127.0.0.1.55853)
Jul 02 09:29:41 andres-postgres-buildfarm-v5 krb5kdc[471964](Error): Address already in use - Error setting up network

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mylodon&dt=2024-05-15%2001%3A25%3A07 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=grassquit&dt=2024-07-04%2008%3A28%3A19 - HEAD

ssl tests fail due to TCP port conflict \ kerberos/001_auth suffers from the port conflict

Force nodes for SSL tests to start in TCP mode

Choose ports for test servers less likely to result in conflicts

001_ssltests.pl failed in REL_12_STABLE due to host name translation error

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=massasauga&dt=2024-07-08%2022%3A01%3A03 - REL_12_STABLE

Bailout called.  Further testing stopped:  pg_ctl start failed
FAILED--Further testing stopped: pg_ctl start failed
make: *** [check] Error 255

================== pgsql.build/src/test/ssl/tmp_check/log/001_ssltests_master.log ===================
2024-07-08 22:19:47.955 UTC [25951:1] LOG:  starting PostgreSQL 12.19 on aarch64-unknown-linux-gnu, compiled by gcc (GCC) 7.3.1 20180712 (Red Hat 7.3.1-17), 64-bit
2024-07-08 22:19:47.957 UTC [25951:2] LOG:  could not translate host name "/tmp/xwbhy3r7ai", service "32471" to address: Name or service not known
2024-07-08 22:19:47.957 UTC [25951:3] WARNING:  could not create listen socket for "/tmp/xwbhy3r7ai"
2024-07-08 22:19:47.957 UTC [25951:4] FATAL:  could not create any TCP/IP sockets
2024-07-08 22:19:47.957 UTC [25951:5] LOG:  database system is shut down

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hachi&dt=2024-07-08%2021%3A05%3A04 - REL_12_STABLE

Revert "Force nodes for SSL tests to start in TCP mode"

xml.sql fails because of test results change due to libxml2.13 incompatibilies

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2024-07-09%2018%3A17%3A23 - HEAD

--- /Users/buildfarm/bf-data/HEAD/pgsql.build/src/test/regress/expected/xml.out	2024-07-09 14:17:24
+++ /Users/buildfarm/bf-data/HEAD/pgsql.build/src/test/regress/results/xml.out	2024-07-09 14:18:36
@@ -254,17 +254,11 @@
 DETAIL:  line 1: xmlParseEntityRef: no name
 <invalidentity>&</invalidentity>
                 ^
-line 1: chunk is not well balanced
-<invalidentity>&</invalidentity>
-                                ^
 SELECT xmlparse(content '<undefinedentity>&idontexist;</undefinedentity>');
 ERROR:  invalid XML content
 DETAIL:  line 1: Entity 'idontexist' not defined
 <undefinedentity>&idontexist;</undefinedentity>
                              ^
-line 1: chunk is not well balanced
-<undefinedentity>&idontexist;</undefinedentity>
-                                               ^
 SELECT xmlparse(content '<invalidns xmlns=''<''/>');
          xmlparse          
 ---------------------------
@@ -283,9 +277,6 @@
 <twoerrors>&idontexist;</unbalanced>
                        ^
 line 1: Opening and ending tag mismatch: twoerrors line 1 and unbalanced
-<twoerrors>&idontexist;</unbalanced>
-                                    ^
-line 1: chunk is not well balanced
 <twoerrors>&idontexist;</unbalanced>
                                     ^
 SELECT xmlparse(content '<nosuchprefix:tag/>');

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2024-07-10%2014%3A16%3A06 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2024-07-09%2021%3A58%3A12 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2024-07-09%2020%3A01%3A37 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2024-07-10%2023%3A45%3A57 - REL_16_STABLE

XML test error on Arch Linux \ ignoring XML_ERR_NOT_WELL_BALANCED

Suppress "chunk is not well balanced" errors from libxml2.
Make our back branches compatible with libxml2 2.13.x.

xml.sql fails due to libxml2-version-dependent error reports

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=snakefly&dt=2024-07-09%2019%3A02%3A05 - HEAD

--- /opt/postgres/bf/v11/buildroot/HEAD/pgsql.build/src/test/regress/expected/xml_2.out	2024-07-09 19:02:04.906168111 +0000
+++ /opt/postgres/bf/v11/buildroot/HEAD/pgsql.build/src/test/regress/results/xml.out	2024-07-09 19:08:11.038226015 +0000
@@ -282,16 +282,12 @@
 SELECT xmlparse(content '<unclosed>');
 ERROR:  invalid XML content
 DETAIL:  line 1: Premature end of data in tag unclosed line 1
-<unclosed>
-          ^
 SELECT xmlparse(content '<parent><child></parent></child>');
 ERROR:  invalid XML content
 DETAIL:  line 1: Opening and ending tag mismatch: child line 1 and parent
 <parent><child></parent></child>
                         ^
 line 1: Opening and ending tag mismatch: parent line 1 and child
-<parent><child></parent></child>
-                                ^
 SELECT xmlparse(document '   ');
 ERROR:  invalid XML document
 DETAIL:  line 1: Start tag expected, '<' not found
@@ -345,16 +341,12 @@
 SELECT xmlparse(document '<unclosed>');
 ERROR:  invalid XML document
 DETAIL:  line 1: Premature end of data in tag unclosed line 1
-<unclosed>
-          ^
 SELECT xmlparse(document '<parent><child></parent></child>');
 ERROR:  invalid XML document
 DETAIL:  line 1: Opening and ending tag mismatch: child line 1 and parent
 <parent><child></parent></child>
                         ^
 line 1: Opening and ending tag mismatch: parent line 1 and child
-<parent><child></parent></child>
-                                ^
 SELECT xmlpi(name foo);
   xmlpi  
 ---------

XML test error on Arch Linux \ Several animals are reporting different error text

Remove new XML test cases added by e7192486d.

040_pg_createsubscriber.pl fails due to subscriber's local catalog xmin is ahead of remote xmin

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2024-07-08%2013%3A16%3A35 - HEAD

163/295 postgresql:pg_basebackup / pg_basebackup/040_pg_createsubscriber                ERROR             84.29s   exit status 1

---
regress_log_040_pg_createsubscriber
[13:28:05.647](2.460s) not ok 26 - failover slot is synced
[13:28:05.648](0.001s) #   Failed test 'failover slot is synced'
#   at /home/bf/bf-build/skink-master/HEAD/pgsql/src/bin/pg_basebackup/t/040_pg_createsubscriber.pl line 307.
[13:28:05.648](0.000s) #          got: ''
#     expected: 'failover_slot'
#### Begin standard error
psql:<stdin>:1: WARNING:  subscription was created, but is not connected
HINT:  To initiate replication, you must manually create the replication slot, enable the subscription, and refresh the subscription.
#### End standard error

---
040_pg_createsubscriber_node_s.log
2024-07-08 13:28:05.369 UTC [3985464][client backend][0/2:0] LOG:  statement: SELECT pg_sync_replication_slots()
2024-07-08 13:28:05.557 UTC [3985464][client backend][0/2:0] LOG:  could not sync slot "failover_slot" as remote slot precedes local slot
2024-07-08 13:28:05.557 UTC [3985464][client backend][0/2:0] DETAIL:  Remote slot has LSN 0/30047B8 and catalog xmin 743, but local slot has LSN 0/30047B8 and catalog xmin 744.
2024-07-08 13:28:05.557 UTC [3985464][client backend][0/2:0] STATEMENT:  SELECT pg_sync_replication_slots()

---
040_pg_createsubscriber_node_p.log
2024-07-08 13:28:00.702 UTC [3981996][postmaster][:0] LOG:  listening on Unix socket "/tmp/WnqJHhLtur/.s.PGSQL.60666"
2024-07-08 13:28:00.872 UTC [3982331][walsender][:0] FATAL:  the database system is starting up
2024-07-08 13:28:00.875 UTC [3982328][startup][:0] LOG:  database system was shut down at 2024-07-08 13:28:00 UTC
2024-07-08 13:28:01.105 UTC [3981996][postmaster][:0] LOG:  database system is ready to accept connections

speed up a logical replica setup \ pg_createsubscriber can affect primary's catalog xmin

Fix unstable test in 040_pg_createsubscriber.

collate.windows.win1252.sql fails on Windows due to trailing whitespace differences

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-07-10%2015%3A12%3A56 - REL_17_STABLE


|  41/287 - regression tests pass                                                       FAIL          
 41/287 postgresql:recovery / recovery/027_stream_regress                               ERROR           756.41s   exit status 1
------------------------------------- 8< -------------------------------------
stderr:
#   Failed test 'regression tests pass'
#   at C:/prog/bf/root/REL_17_STABLE/pgsql/src/test/recovery/t/027_stream_regress.pl line 95.
#          got: '256'
#     expected: '0'
# Looks like you failed 1 test of 9.

---
regress_log_027_stream_regress
...
not ok 154   + collate.windows.win1252                  7120 ms

# 1 of 223 tests failed.

--- C:/prog/bf/root/REL_17_STABLE/pgsql/src/test/regress/expected/collate.windows.win1252.out	2024-07-02 01:00:52.572435500 +0000
+++ C:/prog/bf/root/REL_17_STABLE/pgsql.build/testrun/recovery/027_stream_regress/data/results/collate.windows.win1252.out	2024-07-10 16:19:06.807922000 +0000
@@ -21,10 +21,10 @@
 );
 \\d collate_test1
         Table "collate_tests.collate_test1"
- Column |  Type   | Collation | Nullable | Default
+ Column |  Type   | Collation | Nullable | Default 
 --------+---------+-----------+----------+---------
- a      | integer |           |          |
- b      | text    | en_US     | not null |
+ a      | integer |           |          | 
+ b      | text    | en_US     | not null | 
 
 CREATE TABLE collate_test_fail (
     a int,
@@ -52,10 +52,10 @@
 );
 \\d collate_test_like
       Table "collate_tests.collate_test_like"
- Column |  Type   | Collation | Nullable | Default
+ Column |  Type   | Collation | Nullable | Default 
 --------+---------+-----------+----------+---------
- a      | integer |           |          |
- b      | text    | en_US     | not null |
+ a      | integer |           |          | 
+ b      | text    | en_US     | not null | 
 
 CREATE TABLE collate_test2 (
...

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-07-11%2009%3A45%3A50 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-07-10%2017%3A19%3A23 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-07-12%2010%3A26%3A09 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-07-13%2013%3A44%3A15 - REL_17_STABLE

CFbot failed on Windows platform

Change pg_regress.c back to using diff -w on Windows

constraints.sql fails due to unstable order of new query results

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2024-07-12%2011%3A06%3A04 - REL_15_STABLE

--- /home/ec2-user/bf/root/REL_15_STABLE/pgsql/src/test/regress/expected/constraints.out	2024-07-12 11:06:13.651296795 +0000
+++ /home/ec2-user/bf/root/REL_15_STABLE/pgsql.build/src/test/regress/results/constraints.out	2024-07-12 11:12:36.482910801 +0000
@@ -642,8 +642,8 @@
   FROM pg_constraint WHERE conname IN ('tp_pkey', 'tp_b_a_key');
   conname   | conparentid | conislocal | coninhcount 
 ------------+-------------+------------+-------------
- tp_pkey    |           0 | t          |           0
  tp_b_a_key |           0 | t          |           0
+ tp_pkey    |           0 | t          |           0
 (2 rows)

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=alligator&dt=2024-07-12%2011%3A13%3A45 - REL_13_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2024-07-12%2011%3A03%3A05 - REL_12_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=pogona&dt=2024-07-12%2010%3A57%3A31 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2024-07-12%2011%3A04%3A03 - REL_13_STABLE

Add ORDER BY to new test query

Isolation tests fail on hamerkop with "too many clients" errors

(hamerkop is a Windows animal with gssapi enabled on v16- (as of 2024-06-08))

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2024-06-07%2014%3A17%3A19 - REL_13_STABLE

test skip-locked                  ... ok          530 ms
test skip-locked-2                ... ok          401 ms
test skip-locked-3                ... FAILED (test process exited with exit code 1)      364 ms
test skip-locked-4                ... FAILED (test process exited with exit code 1)      197 ms

---
diff -w -U3 c:/build-farm-local/buildroot/REL_13_STABLE/pgsql.build/src/test/isolation/expected/skip-locked-3.out c:/build-farm-local/buildroot/REL_13_STABLE/pgsql.build/src/test/isolation/results/skip-locked-3.out
--- c:/build-farm-local/buildroot/REL_13_STABLE/pgsql.build/src/test/isolation/expected/skip-locked-3.out	2024-06-07 23:17:47 +0900
+++ c:/build-farm-local/buildroot/REL_13_STABLE/pgsql.build/src/test/isolation/results/skip-locked-3.out	2024-06-08 00:01:27 +0900
@@ -1,25 +1,3 @@
 Parsed test spec with 3 sessions
-
-starting permutation: s1a s2a s3a s1b s2b s3b
...
+Connection 3 failed: could not initiate GSSAPI security context: Unspecified GSS failure.  Minor code may provide more information: Credential cache is empty
+FATAL:  sorry, too many clients already

Why is citext/regress failing on hamerkop? \ "sorry, too many clients already" failures

Fix lost Windows socket EOF events.

partition_split.sql and partition_merge.sql fail due to new queries missing schema names

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=conchuela&dt=2024-07-15%2004%3A23%3A58 - HEAD

--- /home/pgbf/buildroot/HEAD/pgsql.build/src/test/regress/expected/partition_split.out	2024-07-15 06:23:21.117538000 +0200
+++ /home/pgbf/buildroot/HEAD/pgsql.build/src/test/regress/results/partition_split.out	2024-07-15 06:26:53.086612000 +0200
@@ -1506,18 +1506,24 @@
  tablename |    tablespace    
 -----------+------------------
  t         | regress_tblspace
+ t         | 
  tp_0_1    | regress_tblspace
  tp_1_2    | regress_tblspace
-(3 rows)
+ tp_1_2    | 
+(5 rows)
...

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=conchuela&dt=2024-07-15%2004%3A21%3A02 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2024-07-15%2004%3A22%3A01 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=loach&dt=2024-07-15%2004%3A25%3A17 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=morepork&dt=2024-07-15%2004%3A30%3A34 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sidewinder&dt=2024-07-15%2004%3A36%3A39 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=plover&dt=2024-07-15%2004%3A50%3A22 - REL_17_STABLE

MERGE/SPLIT partition commands should create new partitions in the parent's tablespace? \ some buildfarm members reported errors after c08689662

Fix unstable tests in partition_merge.sql and partition_split.sql.

select_parallel.sql fails due to a newly added query plan change

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=tamandua&dt=2024-07-17%2017%3A12%3A53 - HEAD

193/296 postgresql:recovery / recovery/027_stream_regress                               ERROR           192.60s   exit status 1

#   Failed test 'regression tests pass'
#   at /home/bf/bf-build/tamandua/HEAD/pgsql/src/test/recovery/t/027_stream_regress.pl line 95.
#          got: '256'
#     expected: '0'
# Looks like you failed 1 test of 9.

---
regress_log_027_stream_regress

not ok 155   - select_parallel                          3183 ms

--- /home/bf/bf-build/tamandua/HEAD/pgsql/src/test/regress/expected/select_parallel.out	2024-07-12 02:22:21.079018314 +0000
+++ /home/bf/bf-build/tamandua/HEAD/pgsql.build/testrun/recovery/027_stream_regress/data/results/select_parallel.out	2024-07-17 17:17:36.018136963 +0000
@@ -671,15 +671,15 @@
 -- the joinrel is not parallel-safe due to the OFFSET clause in the subquery
 explain (costs off)
 	select * from tenk1 t1, (select * from tenk2 t2 offset 0) t2 where t1.two > t2.two;
-                QUERY PLAN                 
--------------------------------------------
+                   QUERY PLAN                    
+-------------------------------------------------
  Nested Loop
    Join Filter: (t1.two > t2.two)
-   ->  Gather
-         Workers Planned: 4
-         ->  Parallel Seq Scan on tenk1 t1
+   ->  Seq Scan on tenk2 t2
    ->  Materialize
-         ->  Seq Scan on tenk2 t2
+         ->  Gather
+               Workers Planned: 4
+               ->  Parallel Seq Scan on tenk1 t1
 (7 rows)
 
 alter table tenk2 reset (parallel_workers);

Should consider materializing the cheapest inner path in consider_parallel_nestloop()\ an instability of the test addition

Fix unstable test in select_parallel.sql

postgres_fdw.sql hangs on lorikeet due to a Cygwin anomaly

(lorikeet is a Cygwin animal)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=lorikeet&dt=2024-07-12%2010%3A05%3A27 - REL_17_STABLE

===================================================
timed out after 10800 secs

---
lastcommand
# +++ regress install-check in contrib/postgres_fdw +++
# using postmaster on /home/andrew/bf/root/tmp/buildfarm-e2ahpQ, port 5878

Add non-blocking version of PQcancel \ query-cancelling backend is stuck inside poll()

postgres_fdw: Split out the query_cancel test to its own file

043_vacuum_horizon_floor.pl fails on timeout while waiting for index vacuuming

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2024-07-19%2018%3A33%3A47 - REL_17_STABLE

Test Summary Report
-------------------
t/043_vacuum_horizon_floor.pl       (Wstat: 7424 Tests: 3 Failed: 0)
  Non-zero exit status: 29
  Parse errors: No plan found in TAP output

---
regress_log_043_vacuum_horizon_floor
[21:27:38.061](0.011s) ok 3 - Cursor query returned 7 from second fetch. Expected value 7.
[21:33:30.415](352.354s) # poll_query_until timed out executing this query:
# 
# 	SELECT index_vacuum_count > 0
# 	FROM pg_stat_progress_vacuum
# 	WHERE datname='test_db' AND relid::regclass = 'vac_horizon_floor_table'::regclass;
# 	
# expecting this output:
# t
# last actual query output:
# f
# with stderr:
IPC::Run: timeout on timer #2 at /usr/share/perl5/IPC/Run.pm line 2951.

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2024-07-19%2019%3A34%3A56 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2024-07-20%2023%3A47%3A06 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2024-07-21%2000%3A45%3A49 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2024-07-22%2015%3A00%3A11 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2024-07-22%2014%3A01%3A51 - REL_17_STABLE

Vacuum ERRORs out considering freezing dead tuples from before OldestXmin \ the test failed on master on CI

Revert "Test that vacuum removes tuples older than OldestXmin"

043_vacuum_horizon_floor.pl fails on slow machines (especially 32-bit) due to IPC::Run: timeout

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gull&dt=2024-07-20%2007%3A35%3A15 - REL_17_STABLE

t/043_vacuum_horizon_floor.pl       (Wstat: 1024 Tests: 0 Failed: 0)
  Non-zero exit status: 4
  Parse errors: No plan found in TAP output
Files=42, Tests=590, 3121 wallclock secs ( 1.75 usr  0.40 sys + 301.09 cusr 296.01 csys = 599.25 CPU)
Result: FAIL

---
regress_log_043_vacuum_horizon_floor
[04:14:23.558](258.036s) # issuing query via background psql: 
# 		INSERT INTO vac_horizon_floor_table VALUES (99);
# 		UPDATE vac_horizon_floor_table SET col1 = 100 WHERE col1 = 99;
# 		SELECT 'after_update';
#         
IPC::Run: timeout on timer #1 at /usr/share/perl5/IPC/Run.pm line 2951.

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mereswine&dt=2024-07-21%2006%3A26%3A51 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mamba&dt=2024-07-20%2006%3A09%3A08 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gull&dt=2024-07-20%2011%3A16%3A05 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mamba&dt=2024-07-21%2006%3A01%3A48 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mereswine&dt=2024-07-21%2009%3A07%3A36 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mamba&dt=2024-07-22%2001%3A00%3A26 - HEAD

Vacuum ERRORs out considering freezing dead tuples from before OldestXmin \ the test takes too long

Revert "Test that vacuum removes tuples older than OldestXmin"

select_parallel.sql fails on Cygwin due to asserts triggered (< v16 only)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=lorikeet&dt=2024-07-09%2008%3A54%3A07 - REL_12_STABLE

parallel group (5 tests, in groups of 3):  psql_crosstab psql rules amutils stats_ext
     rules                        ... ok         1289 ms
     psql                         ... ok          689 ms
     psql_crosstab                ... ok          238 ms
     amutils                      ... ok          185 ms
     stats_ext                    ... ok         1388 ms
test select_parallel              ... FAILED (test process exited with exit code 2)    16012 ms

---
postmaster.log
2024-07-09 05:01:44.019 EDT [668cfc72.ab3:146] pg_regress/select_parallel LOG:  statement: explain (costs off)
	select * from
	  (select string4, count(unique2)
	   from tenk1 group by string4 order by string4) ss
	  right join (values (1),(2),(3)) v(x) on true;
TRAP: FailedAssertion("!(slot->in_use)", File: "/home/andrew/bf/root/REL_12_STABLE/pgsql.build/../pgsql/src/backend/postmaster/bgworker.c", Line: 436)
*** starting debugger for pid 2026, tid 6324
2024-07-09 05:01:44.020 EDT [668cfc72.ab3:147] pg_regress/select_parallel LOG:  statement: select * from
	  (select string4, count(unique2)
	   from tenk1 group by string4 order by string4) ss
	  right join (values (1),(2),(3)) v(x) on true;
2024-07-09 05:01:50.267 EDT [668cfc72.ab3:148] pg_regress/select_parallel FATAL:  postmaster exited during a parallel transaction
TRAP: FailedAssertion("!(entry->trans == ((void *)0))", File: "/home/andrew/bf/root/REL_12_STABLE/pgsql.build/../pgsql/src/backend/postmaster/pgstat.c", Line: 872)

intermittent failures in Cygwin from select_parallel tests \ signal blocking broke on Cygwin

Also select_parallel.sql hangs on Cygwin (<v16 only)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=lorikeet&dt=2024-07-24%2008%3A54%3A07 - REL_12_STABLE

===================================================
timed out after 10800 secs

test stats_ext                    ... ok         1370 ms
test select_parallel              ...

Sporadic connection-setup-related test failures on Cygwin in v15- \ select_parallel failed due to the signal processing issue

Also dblink.sql, postgres_fdw.sql fail on Cygwin due to connection failures (<v16 only)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=lorikeet&dt=2024-07-16%2009%3A18%3A31 - REL_13_STABLE

test dblink                       ... FAILED     1067 ms

---
pgsql.build/contrib/dblink/regression.diffs
--- /home/andrew/bf/root/REL_13_STABLE/pgsql.build/../pgsql/contrib/dblink/expected/dblink.out	2021-04-10 20:04:00.415079000 -0400
+++ /home/andrew/bf/root/REL_13_STABLE/pgsql.build/contrib/dblink/results/dblink.out	2024-07-16 05:38:21.825846900 -0400
@@ -836,36 +836,19 @@
 (11 rows)
 
 SELECT dblink_connect('dtest1', connection_parameters());
- dblink_connect 
-----------------
- OK
-(1 row)
-
+ERROR:  could not establish connection
+DETAIL:  could not connect to server: Connection refused

---
inst/logfile:
2024-07-16 05:38:21.492 EDT [66963f67.7823:4] LOG:  could not accept new connection: Software caused connection abort
2024-07-16 05:38:21.492 EDT [66963f8c.79e5:170] pg_regress/dblink ERROR:  could not establish connection
2024-07-16 05:38:21.492 EDT [66963f8c.79e5:171] pg_regress/dblink DETAIL:  could not connect to server: Connection refused
         Is the server running locally and accepting
         connections on Unix domain socket "/home/andrew/bf/root/tmp/buildfarm-DK1yh4/.s.PGSQL.5838"?

Sporadic connection-setup-related test failures on Cygwin in v15-

This problem went away in v16 with commit 7389aad63666a2cac18cd6d7496378d7f50ef37b; now we don't really need signal blocking to work 100% reliably properly in the postmaster.

Sporadic connection-setup-related test failures on Cygwin in v15-\ Stop testing releases <16 on lorikeet

postgres_fdw.sql failed on hake due to pgfdw_conn_check returned 0 against expectations

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hake&dt=2024-07-26%2017%3A16%3A31 - HEAD

--- /export/home/elmer/c15x/buildroot/HEAD/pgsql.build/contrib/postgres_fdw/expected/postgres_fdw.out	Fri Jul 26 19:16:29 2024
+++ /export/home/elmer/c15x/buildroot/HEAD/pgsql.build/contrib/postgres_fdw/results/postgres_fdw.out	Fri Jul 26 19:31:12 2024
@@ -12326,7 +12326,7 @@
   FROM postgres_fdw_get_connections(true);
  case 
 ------
-    1
+    0
 (1 row)

Proposal Add foreign-server health checks infrastructure \ hake reported a failure in the postgres_fdw test

postgres_fdw: Fix bug in connection status check.

The --disable-spinlocks animals failing after 9d9b9d46f due to a spinlock released twice

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rorqual&dt=2024-07-29%2013%3A27%3A42 - HEAD

regress_log_027_stream_regress
not ok 109   + brin                                     3653 ms
# (test process exited with exit code 2)
not ok 110   + gin                                      3669 ms
# (test process exited with exit code 2)

---
027_stream_regress_primary.log
2024-07-29 13:31:55.529 UTC [3768125] LOG:  background worker "parallel worker" (PID 3810206) was terminated by signal 6: Aborted

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rorqual&dt=2024-07-29%2013%3A19%3A25 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=francolin&dt=2024-07-29%2013%3A19%3A00 - HEAD

Move cancel key generation to after forking the backend \ The --disable-spinlocks animals are failing

Fix double-release of spinlock

001_emergency_vacuum.pl fails to wait for datfrozenxid advancing

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dodo&dt=2024-05-19%2006%3A33%3A34 - HEAD

(dodo is a slow armv7l machine)

# +++ tap install-check in src/test/modules/xid_wraparound +++
# poll_query_until timed out executing this query:
# 
# SELECT NOT EXISTS (
# 	SELECT *
# 	FROM pg_database
# 	WHERE age(datfrozenxid) > current_setting('autovacuum_freeze_max_age')::int)
# 
# expecting this output:
# t
# last actual query output:
# f
# with stderr:
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 29 just after 1.
t/001_emergency_vacuum.pl .. 
Dubious, test returned 29 (wstat 7424, 0x1d00)
All 1 subtests passed

Testing autovacuum wraparound (including failsafe) \ autovacuum worker can't be started due to a race condition
xid_wraparound tests intermittent failure.

Stabilize xid_wraparound tests

040_pg_createsubscriber.pl fails due to recovery timed out during pg_createsubscriber run

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=olingo&dt=2024-07-11%2007%3A25%3A12 - HEAD


239/295 postgresql:pg_basebackup / pg_basebackup/040_pg_createsubscriber                ERROR           274.49s   exit status 29

---
regress_log_040_pg_createsubscriber

recovery_target_lsn = '0/30098D0'
pg_createsubscriber: starting the subscriber
...
2024-07-11 07:37:10.001 UTC [2948830][client backend][0/3:0] LOG:  statement: SELECT pg_catalog.pg_is_in_recovery()
...
pg_createsubscriber: server was started
pg_createsubscriber: waiting for the target server to reach the consistent state
...
2024-07-11 07:40:10.816 UTC [2948830][client backend][0/183:0] LOG:  statement: SELECT pg_catalog.pg_is_in_recovery()
...
2024-07-11 07:40:10.837 UTC [2948531][postmaster][:0] LOG:  received fast shutdown request 
# (there is no "recovery stopping after WAL location (LSN) XXXX" record)
...
pg_createsubscriber: server was stopped
pg_createsubscriber: error: recovery timed out

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2024-07-12%2000%3A38%3A06 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-07-13%2001%3A53%3A19 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=tamandua&dt=2024-07-22%2002%3A31%3A32 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=canebrake&dt=2024-07-25%2002%3A39%3A02 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=adder&dt=2024-07-26%2009%3A20%3A15 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2024-07-26%2022%3A24%3A58 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=olingo&dt=2024-07-26%2016%3A02%3A40 - HEAD

speed up a logical replica setup \ recovery timed out

pg_createsubscriber: Fix an unpredictable recovery wait time.

002_pg_upgrade.pl fails with debug_parallel_query = regress after f5f30c22e

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=perentie&dt=2024-08-01%2000%3A00%3A03 - HEAD

#   Failed test 'regression tests pass'
#   at t/002_pg_upgrade.pl line 260.
#          got: '256'
#     expected: '0'

#   Failed test 'dump before running pg_upgrade'
#   at t/002_pg_upgrade.pl line 322.

---
002_pg_upgrade_old_node.log
2024-08-01 09:12:17.546 JST [458166:4] FATAL:  cannot change "client_encoding" during a parallel operation
...
2024-08-01 09:12:18.391 JST [450200:253] LOG:  background worker "parallel worker" (PID 458166) was terminated by signal 6: Aborted
2024-08-01 09:12:18.391 JST [450200:254] DETAIL:  Failed process was running: SELECT a, b FROM collate_test1 UNION ALL SELECT a, b FROM collate_test3 ORDER BY 2;
...

Also collate.icu.utf8.sql triggers assertion failure when non-default encoding is used

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=conchuela&dt=2024-08-01%2000%3A54%3A50 - HEAD

not ok 145   + collate.icu.utf8                         3316 ms
# (test process exited with exit code 2)

---
inst/logfile
2024-08-01 03:00:53.562 CEST [821316:4] FATAL:  cannot change "client_encoding" during a parallel operation
TRAP: failed Assert("!IsTransactionOrTransactionBlock()"), File: "pgstat.c", Line: 632, PID: 821316
0x9deaed <ExceptionalCondition+0x6d> at /home/pgbf/buildroot/HEAD/inst/bin/postgres
0x8a0e86 <pgstat_report_stat+0x2d6> at /home/pgbf/buildroot/HEAD/inst/bin/postgres
0x8a0f58 <pgstat_shutdown_hook+0x38> at /home/pgbf/buildroot/HEAD/inst/bin/postgres
0x8592c5 <shmem_exit+0x65> at /home/pgbf/buildroot/HEAD/inst/bin/postgres
0x8591dc <proc_exit_prepare+0x5c> at /home/pgbf/buildroot/HEAD/inst/bin/postgres
0x859136 <proc_exit+0x56> at /home/pgbf/buildroot/HEAD/inst/bin/postgres
0x9df998 <errfinish+0x258> at /home/pgbf/buildroot/HEAD/inst/bin/postgres
0x686626 <assign_client_encoding+0x56> at /home/pgbf/buildroot/HEAD/inst/bin/postgres
0x9f8ce3 <AtEOXact_GUC+0x2f3> at /home/pgbf/buildroot/HEAD/inst/bin/postgres
0x546935 <AbortTransaction+0x285> at /home/pgbf/buildroot/HEAD/inst/bin/postgres
0x54662b <AbortOutOfAnyTransaction+0x5b> at /home/pgbf/buildroot/HEAD/inst/bin/postgres
0x9f23d9 <ShutdownPostgres+0x9> at /home/pgbf/buildroot/HEAD/inst/bin/postgres

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=jay&dt=2024-07-31%2023%3A58%3A16 - HEAD

BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION \ the buildfarm didn't like that much

Revert "Allow parallel workers to cope with a newly-created session user ID."

001_concurrent_transaction.pl fails due to standby not synchronized (after e2ed7e322)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=calliphoridae&dt=2024-08-15%2021%3A20%3A20 - HEAD

223/299 postgresql:pg_visibility / pg_visibility/001_concurrent_transaction             ERROR             5.55s   exit status 29

stderr:
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 29 just after 1.

(test program exited with status code 29)

---
regress_log_001_concurrent_transaction
[21:27:36.319](0.096s) ok 1 - pg_check_visible() detects no errors
error running SQL: 'psql:<stdin>:1: ERROR:  function pg_check_visible(unknown) does not exist
LINE 1: SELECT * FROM pg_check_visible('vacuum_test');
                      ^
HINT:  No function matches the given name and argument types. You might need to add explicit type casts.'
while running 'psql -XAtq -d port=28153 host=/tmp/H_TnqDvPcT dbname='postgres' -f - -v ON_ERROR_STOP=1' with sql 'SELECT * FROM pg_check_visible('vacuum_test');' at /home/bf/bf-build/calliphoridae/HEAD/pgsql/src/test/perl/PostgreSQL/Test/Cluster.pm line 2140.

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=tamandua&dt=2024-08-15%2021%3A20%3A13 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2024-08-15%2021%3A20%3A00 - HEAD

pgsql: Fix GetStrictOldestNonRemovableTransactionId() on standby \ buildfarm failures

Add missing wait_for_catchup() to pg_visibility tap test

006_db_file_copy.pl failed on dikkop due to replication timeout

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dikkop&dt=2024-07-27%2023%3A22%3A57 - HEAD

[02:09:22.511](24.583s) ok 1 - full backup
...
[02:10:35.758](73.247s) not ok 2 - incremental backup

---
006_db_file_copy_primary.log
2024-07-28 02:09:29.441 UTC [67785:12] 006_db_file_copy.pl LOG: received replication command: START_REPLICATION SLOT "pg_basebackup_67785" 0/4000000 TIMELINE 1
2024-07-28 02:09:29.441 UTC [67785:13] 006_db_file_copy.pl STATEMENT:  START_REPLICATION SLOT "pg_basebackup_67785" 0/4000000 TIMELINE 1
2024-07-28 02:09:29.441 UTC [67785:14] 006_db_file_copy.pl LOG: acquired physical replication slot "pg_basebackup_67785"
2024-07-28 02:09:29.441 UTC [67785:15] 006_db_file_copy.pl STATEMENT:  START_REPLICATION SLOT "pg_basebackup_67785" 0/4000000 TIMELINE 1
2024-07-28 02:10:29.487 UTC [67785:16] 006_db_file_copy.pl LOG: terminating walsender process due to replication timeout
2024-07-28 02:10:29.487 UTC [67785:17] 006_db_file_copy.pl STATEMENT:  START_REPLICATION SLOT "pg_basebackup_67785" 0/4000000 TIMELINE 1

Also 001_stream_rep.pl failed on dikkop due to replication timeout

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dikkop&dt=2024-08-02%2005%3A00%3A26 - REL_14_STABLE

regress_log_001_stream_rep
# Taking pg_basebackup my_backup from node "standby_1"
# Running: pg_basebackup -D /mnt/data/buildfarm/buildroot/REL_14_STABLE/pgsql.build/src/test/recovery/tmp_check/t_001_stream_rep_standby_1_data/backup/my_backup -h /mnt/data/buildfarm/buildroot/tmp/dU3MkMjYZe -p 20416 --checkpoint fast --no-sync
pg_basebackup: error: could not send feedback packet: server closed the connection unexpectedly

---
001_stream_rep_standby_1.log
2024-08-02 08:24:11.371 UTC [33738:5] standby_1 LOG:  received replication command: START_REPLICATION 0/3000000 TIMELINE 1
2024-08-02 08:24:11.371 UTC [33738:6] standby_1 STATEMENT:  START_REPLICATION 0/3000000 TIMELINE 1
2024-08-02 08:25:11.485 UTC [33738:7] standby_1 LOG:  terminating walsender process due to replication timeout
2024-08-02 08:25:11.485 UTC [33738:8] standby_1 STATEMENT:  START_REPLICATION 0/3000000 TIMELINE 1

Also 003_timeline.pl failed on dikkop due to replication timeout

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dikkop&dt=2024-08-04%2010%3A04%3A51 - HEAD

regress_log_003_timeline
# Running: pg_basebackup -D /mnt/data/buildfarm/buildroot/HEAD/pgsql.build/src/bin/pg_combinebackup/tmp_check/t_003_timeline_node1_data/backup/backup2 --no-sync -cfast --incremental /mnt/data/buildfarm/buildroot/HEAD/pgsql.build/src/bin/pg_combinebackup/tmp_check/t_003_timeline_node1_data/backup/backup1/backup_manifest
pg_basebackup: error: could not receive data from WAL stream: server closed the connection unexpectedly
	This probably means the server terminated abnormally
	before or while processing the request.
...
[12:47:42.477](87.278s) not ok 2 - incremental backup from node1

---
003_timeline_node1.log
2024-08-04 12:46:34.985 UTC [4951:12] 003_timeline.pl LOG:  received replication command: START_REPLICATION SLOT "pg_basebackup_4951" 0/4000000 TIMELINE 1
2024-08-04 12:46:34.985 UTC [4951:13] 003_timeline.pl STATEMENT:  START_REPLICATION SLOT "pg_basebackup_4951" 0/4000000 TIMELINE 1
2024-08-04 12:46:34.986 UTC [4951:14] 003_timeline.pl LOG:  acquired physical replication slot "pg_basebackup_4951"
2024-08-04 12:46:34.986 UTC [4951:15] 003_timeline.pl STATEMENT:  START_REPLICATION SLOT "pg_basebackup_4951" 0/4000000 TIMELINE 1
2024-08-04 12:47:34.987 UTC [4951:16] 003_timeline.pl LOG:  terminating walsender process due to replication timeout

dikkop failed the pg_combinebackupCheck/006_db_file_copy.pl test

Instability with incremental backup tests (pg_combinebackup, 003_timeline.pl) \ Moving to a better storage

`make temp-install/check` triggers assert on CLOBBER_CACHE_ALWAYS animal after c14d4acb8

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=trilobite&dt=2024-08-25%2005%3A22%3A07 - HEAD

performing post-bootstrap initialization ... TRAP: failed Assert("found"), File: "typcache.c", Line: 3077, PID: 22100

type cache cleanup improvements \ trilobite failed to perform `make check`

Revert: Avoid looping over all type cache entries in TypeCacheRelCallback()

The postgres_fdw test fails due to an unexpected warning on canceling a statement

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=olingo&dt=2024-06-20%2009%3A52%3A04 - HEAD

70/70 postgresql:postgres_fdw-running / postgres_fdw-running/regress               ERROR           278.67s   exit status 1

---
postgres_fdw-running/regress/regression.diffs
--- /home/bf/bf-build/olingo/HEAD/pgsql/contrib/postgres_fdw/expected/postgres_fdw.out	2024-06-07 10:43:46.591500366 +0000
+++ /home/bf/bf-build/olingo/HEAD/pgsql.build/testrun/postgres_fdw-running/regress/results/postgres_fdw.out	2024-06-20 10:13:52.926459374 +0000
@@ -2775,6 +2775,7 @@
 SET LOCAL statement_timeout = '10ms';
 select count(*) from ft1 CROSS JOIN ft2 CROSS JOIN ft4 CROSS JOIN ft5; -- this takes very long
 ERROR:  canceling statement due to statement timeout
+WARNING:  could not get result of cancel request due to timeout
 COMMIT;
 -- ====================================================================
 -- Check that userid to use when querying the remote table is correctly

postgres_fdw-running/regress fails due to an unxepected warning

Make postgres_fdw's query_cancel test less flaky.

kerberos/001_auth.pl fails on chipmunk due to kerberos utils missing

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=chipmunk&dt=2024-08-03%2014%3A12%3A56 - HEAD

# +++ tap check in src/test/kerberos +++
Bailout called.  Further testing stopped:  command "/usr/sbin/kdb5_util create -s -P secret0" exited with value 2
FAILED--Further testing stopped: command "/usr/sbin/kdb5_util create -s -P secret0" exited with value 2
Makefile:22: recipe for target 'check' failed

---
regress_log_001_auth
Can't exec "/usr/sbin/kdb5_util": No such file or directory at /home/pgbfarm/buildroot/HEAD/pgsql.build/src/test/kerberos/../../../src/test/perl/PostgreSQL/Test/Utils.pm line 349.

configure failures on chipmunk \ chipmunk fails on the kerberosCheck stage

configure failures on chipmunk \ chipmunk turned green

pg_visibilty failed due to stack-use-after-scope under ASAN after ed1b1ee59

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=olingo&dt=2024-09-03%2017%3A47%3A20 - master

 84/300 postgresql:pg_visibility / pg_visibility/regress                                ERROR             2.84s   exit status 1

---
pgsql.build/testrun/pg_visibility/regress/log/postmaster.log
==2755594==ERROR: AddressSanitizer: stack-use-after-scope on address 0x7ffe7e0a1770 at pc 0x56137e4ad33f bp 0x7ffe7e0a1530 sp 0x7ffe7e0a1528
READ of size 4 at 0x7ffe7e0a1770 thread T0
    #0 0x56137e4ad33e in block_range_read_stream_cb /home/bf/bf-build/olingo/HEAD/pgsql.build/../pgsql/src/backend/storage/aio/read_stream.c:177:9
    #1 0x56137e4af3e0 in read_stream_get_block /home/bf/bf-build/olingo/HEAD/pgsql.build/../pgsql/src/backend/storage/aio/read_stream.c:196:14
...
2024-09-03 17:54:12.370 UTC postmaster[2755270] LOG:  server process (PID 2755594) was terminated by signal 6: Aborted
2024-09-03 17:54:12.370 UTC postmaster[2755270] DETAIL:  Failed process was running: select count(*) > 0 from pg_visibility('regular_table');

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=grassquit&dt=2024-09-03%2017%3A47%3A20 - master

Use read streams in pg_visibility \ invalid scope of variable

Fix stack variable scope from previous commit.

sqljson_queryfuncs.sql and sqljson_jsontable.sql break due to a llvm compilation issue (after 3a9746097)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bushmaster&dt=2024-09-06%2003%3A10%3A37 - master

not ok 184   + sqljson_queryfuncs                         92 ms
# (test process exited with exit code 2)
not ok 185   + sqljson_jsontable                          85 ms
# (test process exited with exit code 2)


--- /home/bf/bf-build/bushmaster/HEAD/pgsql/src/test/regress/expected/sqljson_queryfuncs.out	2024-08-29 12:56:56.067199857 +0000
+++ /home/bf/bf-build/bushmaster/HEAD/pgsql.build/src/test/regress/results/sqljson_queryfuncs.out	2024-09-06 03:19:10.330722910 +0000
@@ -48,1408 +48,8 @@
 (1 row)
 
 SELECT JSON_EXISTS(jsonb '1', 'strict $.a' ERROR ON ERROR);
-ERROR:  jsonpath member accessor can only be applied to an object
...
+FATAL:  fatal llvm error: Broken module found, compilation aborted!
+server closed the connection unexpectedly
...
--- /home/bf/bf-build/bushmaster/HEAD/pgsql/src/test/regress/expected/sqljson_jsontable.out	2024-09-06 03:10:37.530863386 +0000
+++ /home/bf/bf-build/bushmaster/HEAD/pgsql.build/src/test/regress/results/sqljson_jsontable.out	2024-09-06 03:19:10.322722911 +0000
@@ -16,1162 +16,8 @@
                                                              ^
 DETAIL:  Only EMPTY [ ARRAY ] or ERROR is allowed in the top-level ON ERROR clause.
 SELECT * FROM JSON_TABLE('[]', 'strict $.a' COLUMNS (js2 int PATH '$') EMPTY ON ERROR);
- js2 
------
-(0 rows)
...
+FATAL:  fatal llvm error: Broken module found, compilation aborted!
+server closed the connection unexpectedly

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=canebrake&dt=2024-09-06%2003%3A09%3A15 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=urutu&dt=2024-09-06%2003%3A10%3A35 - master

Re: pgsql: Add more SQL/JSON constructor functions \ 0004 doesn't play nicely with LLVM

Revert recent SQL/JSON related commits

sqljson_jsontable.sql fails due to extra JIT-related output in EXPLAIN (after 68222851d and 565caaa79)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=taipan&dt=2024-09-06%2003%3A08%3A17 - master

not ok 185   + sqljson_jsontable                        1869 ms
...

---
pgsql.build/src/test/regress/regression.diffs
--- /home/bf/bf-build/taipan/HEAD/pgsql/src/test/regress/expected/sqljson_jsontable.out	2024-09-06 03:08:13.902924907 +0000
+++ /home/bf/bf-build/taipan/HEAD/pgsql.build/src/test/regress/results/sqljson_jsontable.out	2024-09-06 03:16:12.978761395 +0000
@@ -1140,7 +1140,10 @@
  Table Function Scan on "json_table"  (cost=0.01..1.00 rows=100 width=32)
    Output: a
    Table Function Call: JSON_TABLE('"a"'::jsonb, '$' AS json_table_path_0 COLUMNS (a text PATH '$'))
-(3 rows)
+ JIT:
+   Functions: 2
+   Options: Inlining false, Optimization false, Expressions true, Deforming true
+(6 rows)
...

Re: pgsql: Add more SQL/JSON constructor functions \ to not use EXPLAIN VERBOSE {{{2}}}

Revert recent SQL/JSON related commits

pageinspect/page.sql fails on big-endian animals (after 05036a315)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2024-09-12%2022%3A54%3A45 - REL_14_STABLE

test page                         ... FAILED      182 ms

--- /export/home/nm/farm/studio64v12_6/REL_14_STABLE/pgsql.build/../pgsql/contrib/pageinspect/expected/page.out	Fri Sep 13 00:54:47 2024
+++ /export/home/nm/farm/studio64v12_6/REL_14_STABLE/pgsql.build/contrib/pageinspect/results/page.out	Fri Sep 13 01:49:16 2024
@@ -242,6 +242,6 @@
   from heap_page_items(get_raw_page('test_sequence', 0));
                    tuple_data_split                    
 -------------------------------------------------------
- {"\\\\x0100000000000000","\\\\x0000000000000000","\\\\x00"}
+ {"\\\\x0000000000000001","\\\\x0000000000000000","\\\\x00"}
 (1 row)

Pgstattuple on Sequences: Seeking Community Feedback on Potential Patch \ buildfarm is unhappy with the new tests

Fix contrib/pageinspect's test for sequences.

pageinspect/page.sql fails on access to temp tables during parallel operation (after 05036a315)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skimmer&dt=2024-09-12%2022%3A38%3A13 - REL_14_STABLE

test page                         ... FAILED      444 ms

--- /u1/tac/build-farm-17/buildroot/REL_14_STABLE/pgsql.build/contrib/pageinspect/expected/page.out	2024-09-12 18:38:15.159791288 -0400
+++ /u1/tac/build-farm-17/buildroot/REL_14_STABLE/pgsql.build/contrib/pageinspect/results/page.out	2024-09-12 19:01:41.660534527 -0400
@@ -240,8 +240,4 @@
 create temporary sequence test_sequence;
 select tuple_data_split('test_sequence'::regclass, t_data, t_infomask, t_infomask2, t_bits)
   from heap_page_items(get_raw_page('test_sequence', 0));
-                   tuple_data_split                    
--------------------------------------------------------
- {"\\\\x0100000000000000","\\\\x0000000000000000","\\\\x00"}
-(1 row)
-
+ERROR:  cannot access temporary tables during a parallel operation

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skimmer&dt=2024-09-12%2022%3A00%3A02 - REL_12_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skimmer&dt=2024-09-12%2022%3A18%3A33 - REL_13_STABLE

Pgstattuple on Sequences: Seeking Community Feedback on Potential Patch \ temporary sequence can't be used in this test

Fix contrib/pageinspect's test for sequences.

merge.sql fails due to ExclusiveLock not owned, in v15, v16 (after 51ff46de2)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2024-09-24%2022%3A29%3A15 - REL_16_STABLE

--- /home/buildfarm/build-farm-17/buildroot/REL_16_STABLE/pgsql/src/test/regress/expected/merge.out	2024-09-24 18:29:05.348210581 -0400
+++ /home/buildfarm/build-farm-17/buildroot/REL_16_STABLE/pgsql.build/testrun/regress/regress/results/merge.out	2024-09-24 18:29:52.270236567 -0400
@@ -404,6 +404,8 @@
 ON t.tid = s.sid
 WHEN NOT MATCHED THEN
 	INSERT VALUES (4, NULL);
+WARNING:  you don't own a lock of type ExclusiveLock
+WARNING:  you don't own a lock of type ExclusiveLock

race condition in pg_class \ the pushes contained at least one defect

Fix use of uninitialized value in previous commit.

Recently added intra-grant-inplace-db.spec fails on slow/JIT-enabled machines

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=habu&dt=2024-07-18%2003%3A08%3A08 - REL_12_STABLE

test intra-grant-inplace-db       ... FAILED     4302 ms


=======================
 1 of 98 tests failed. 
=======================

---
regression.diffs
--- /home/fedora/17-habu/buildroot/REL_12_STABLE/pgsql.build/src/test/isolation/expected/intra-grant-inplace-db.out	2024-07-18 03:08:32.946251561 +0000
+++ /home/fedora/17-habu/buildroot/REL_12_STABLE/pgsql.build/src/test/isolation/output_iso/results/intra-grant-inplace-db.out	2024-07-18 03:26:41.886968008 +0000
@@ -21,8 +21,7 @@
 	WHERE datname = current_catalog
 		AND age(datfrozenxid) > (SELECT min(age(x)) FROM frozen_witness);
 
-?column?              
-----------------------
-datfrozenxid retreated
-(1 row)
+?column?
+--------
+(0 rows)

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=urutu&dt=2024-07-22%2018%3A00%3A46 - REL_13_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-07-24%2005%3A21%3A05 - REL_12_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=taipan&dt=2024-07-28%2012%3A20%3A37 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=urutu&dt=2024-08-08%2012%3A01%3A17 - REL_12_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=oystercatcher&dt=2024-09-17%2003%3A00%3A46 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=petalura&dt=2024-09-21%2018%3A44%3A45 - REL_14_STABLE

race condition in pg_class \ intra-grant-inplace-db.spec may fail on a slow machine

Fix data loss at inplace update after heap_update().

password.sql fails due to new length-checking query not reflected in password_1.out

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gecko&dt=2024-10-07%2020%3A30%3A34 - master

not ok 125   + password                                  952 ms

---
regression.diffs
--- /home/linux1/17-gecko/buildroot/HEAD/pgsql.build/src/test/regress/expected/password_1.out	2024-10-07 16:28:24.961175600 -0400
+++ /home/linux1/17-gecko/buildroot/HEAD/pgsql.build/src/test/regress/results/password.out	2024-10-07 16:39:53.941216373 -0400
@@ -128,6 +128,13 @@
  regress_passwd_sha_len2 | t
 (3 rows)

+-- Test that valid hashes that are too long are rejected
+CREATE ROLE regress_passwd10 PASSWORD 'SCRAM-...';
+ERROR:  encrypted password is too long
+DETAIL:  Encrypted passwords must be no longer than 512 bytes.
+ALTER ROLE regress_passwd9 PASSWORD 'SCRAM-...';
+ERROR:  encrypted password is too long
+DETAIL:  Encrypted passwords must be no longer than 512 bytes.

pgsql: Fix test for password hash length limit.

Fix test for password hash length limit.

Recent addition to test_decoding/stream.sql fails on 32-bit (and some other) animals in v14, v15

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=adder&dt=2024-10-07%2010%3A23%3A44 - REL_14_STABLE

test stream                       ... FAILED      186 ms

---
pgsql.build/contrib/test_decoding/regression.diffs
--- /home/bf/bf-build/adder/REL_14_STABLE/pgsql.build/../pgsql/contrib/test_decoding/expected/stream.out	2024-10-07 10:23:43.511063647 +0000
+++ /home/bf/bf-build/adder/REL_14_STABLE/pgsql.build/contrib/test_decoding/results/stream.out	2024-10-07 10:31:09.703092511 +0000
@@ -122,7 +122,7 @@
 SELECT count(*) FROM pg_logical_slot_get_changes('regression_slot', NULL, NULL, 'include-xids', '0', 'skip-empty-xacts', '1', 'stream-changes', '1');
  count 
 -------
-   315
+     0
 (1 row)

(gokiburi and hachi run tests with wal_compression = zstd, default_toast_compression = lz4)

pgsql: Fix fetching default toast value during decoding of in-progress \ the size of records inserted may vary

Stabilize the test added by commit 022564f60c.

Recently added 001_connection_limits.pl fails on Windows

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-10-08%2020%3A21%3A41 - master

231/294 postgresql:postmaster / postmaster/001_connection_limits                        ERROR            28.72s   exit status 25

---
pgsql.build/testrun/postmaster/001_connection_limits/log/001_connection_limits_primary.log
2024-10-08 22:11:10.549 UTC [5080:3] [unknown] LOG:  no match in usermap "regress" for user "regress_regular" authenticated as "pgrunner@EC2AMAZ-P7KGG90"
2024-10-08 22:11:10.549 UTC [5080:4] [unknown] FATAL:  SSPI authentication failed for user "regress_regular"
2024-10-08 22:11:10.549 UTC [5080:5] [unknown] DETAIL:  Connection matched file "C:/prog/bf/root/HEAD/pgsql.build/testrun/postmaster/001_connection_limits/data/t_001_connection_limits_primary_data/pgdata/pg_hba.conf" line 2: "host all all 127.0.0.1/32  sspi include_realm=1 map=regress"

pgsql: Allow roles created by new test to log in under SSPI.

Allow roles created by new test to log in under SSPI.

001_emergency_vacuum.pl fails due to slow server shutdown on perentie

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=perentie&dt=2024-10-05%2000%3A00%3A14 - master

Bailout called.  Further testing stopped:  pg_ctl stop failed
[09:32:28] t/001_emergency_vacuum.pl .. 
Dubious, test returned 255 (wstat 65280, 0xff00)

---
001_emergency_vacuum_main.log
2024-10-05 09:30:28.483 JST [2711201:4] LOG:  received fast shutdown request
2024-10-05 09:30:28.483 JST [2711201:5] LOG:  aborting any active transactions
2024-10-05 09:30:28.485 JST [2711201:6] LOG:  background worker "logical replication launcher" (PID 2711207) exited with exit code 1
2024-10-05 09:30:28.675 JST [2711202:1] LOG:  shutting down
2024-10-05 09:30:28.675 JST [2711202:2] LOG:  checkpoint starting: shutdown immediate
2024-10-05 09:32:28.722 JST [2711201:7] LOG:  received immediate shutdown request
2024-10-05 09:32:28.740 JST [2711201:8] LOG:  database system is shut down

---
regress_log_001_emergency_vacuum
[09:30:28.479](0.000s) ok 6 - failsafe vacuum triggered for small_trunc
### Stopping node "main" using mode fast
# Running: pg_ctl -D /home/bf/buildroot/HEAD/pgsql.build/src/test/modules/xid_wraparound/tmp_check/t_001_emergency_vacuum_main_data/pgdata -m fast stop
waiting for server to shut down........................................................................................................................... failed
pg_ctl: server does not shut down
# pg_ctl stop failed: 256

Testing autovacuum wraparound (including failsafe) \ perentie needs larger PGCTLTIMEOUT

Testing autovacuum wraparound (including failsafe) \ other tests won't be overlapped

XversionUpgrade-xxx-HEAD tests fail due to checksum settings difference

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-10-16%2007%3A03%3A05 - master


---
upgrade.fairywren/HEAD/REL9_2_STABLE-upgrade.log
Performing Consistency Checks
-----------------------------
Checking cluster versions                                     ok

old cluster does not use data checksums but the new one does
Failure, exiting

Enable data checksums by default \ upgrade tests on the buildfarm don't like this

fix for data checksum default change

test_extensions.sql fails on Windows because of different EOL chars

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2024-10-23%2011%3A00%3A37 - master


101/290 postgresql:test_extensions / test_extensions/regress                            ERROR             8.61s   exit status 1

---
pgsql.build/testrun/test_extensions/regress/regression.diffs
--- c:/build-farm-local/buildroot/HEAD/pgsql/src/test/modules/test_extensions/expected/test_extensions.out	2024-10-23 20:03:34 +0900
+++ c:/build-farm-local/buildroot/HEAD/pgsql.build/testrun/test_extensions/regress/results/test_extensions.out	2024-10-23 20:20:10 +0900
@@ -77,7 +77,7 @@
 ERROR:  syntax error at or near "FUNCTIN"
 LINE 1: CREATE FUNCTIN my_erroneous_func(int) RETURNS int LANGUAGE S...
                ^
-QUERY:  CREATE FUNCTIN my_erroneous_func(int) RETURNS int LANGUAGE SQL
+QUERY:  CREATE FUNCTIN my_erroneous_func(int) RETURNS int LANGUAGE SQL
 AS $$ SELECT $1 + 1 $$;
 CONTEXT:  extension script file "test_ext7--2.0--2.1bad.sql", near line 10
 alter extension test_ext7 update to '2.2bad';
...

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2024-10-24%2011%3A00%3A28 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2024-10-25%2011%3A00%3A22 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2024-10-26%2011%3A00%3A16 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2024-10-27%2011%3A00%3A15 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2024-10-28%2011%3A00%3A16 - master

Better error reporting from extension scripts \ hamerkop doesn't like this patch

Strip Windows newlines from extension script files manually.

001_pgbench_with_server.pl fails due to IPC::Run losing stdout/stderr on macOS

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2024-10-02%2002%3A34%3A16 - master

(indri is a macOS animal)

[22:38:14.887](0.014s) ok 362 - pgbench script error: sleep undefined variable status (got 2 vs expected 2)
[22:38:14.887](0.000s) ok 363 - pgbench script error: sleep undefined variable stdout /(?^:processed: 0/1)/
[22:38:14.887](0.000s) not ok 364 - pgbench script error: sleep undefined variable stderr /(?^:sleep: undefined variable)/
[22:38:14.887](0.000s)
[22:38:14.887](0.000s) #   Failed test 'pgbench script error: sleep undefined variable stderr /(?^:sleep: undefined 
variable)/'
#   at t/001_pgbench_with_server.pl line 1242.
[22:38:14.887](0.000s) #                   ''
#     doesn't match '(?^:sleep: undefined variable)'

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sifaka&dt=2024-10-29%2016%3A43%3A25 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2025-01-13%2000%3A20%3A43 - master

IPC::Run accepts bug reports \ pgbench test failed on indri

IPC-Run: Retry _read() on EINTR, instead of losing pipe contents.

intra-grant-inplace-db.spec failed due to test session stuck in LockBufferForCleanup()

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sarus&dt=2024-10-26%2014%3A08%3A58 - master

not ok 42    - intra-grant-inplace-db                 360069 ms

---
pgsql.build/src/test/isolation/output_iso/regression.diffs
--- /home/linux1/17-sarus/buildroot/HEAD/pgsql.build/src/test/isolation/expected/intra-grant-inplace-db.out	2024-10-26 14:08:40.978532918 +0000
+++ /home/linux1/17-sarus/buildroot/HEAD/pgsql.build/src/test/isolation/output_iso/results/intra-grant-inplace-db.out	2024-10-26 14:28:51.808555640 +0000
@@ -9,13 +9,14 @@
 step grant1: 
 	GRANT TEMP ON DATABASE isolation_regression TO regress_temp_grantee;
 
-step vac2: VACUUM (FREEZE); <waiting ...>
+isolationtester: canceling step vac2 after 360 seconds
+step vac2: VACUUM (FREEZE);
+ERROR:  canceling statement due to user request
 step snap3:

heap_inplace_lock vs. autovacuum w/ LOCKTAG_TUPLE

Unpin buffer before inplace update waits for an XID to end.

pg_regress tests fail due to "could not read blocks" error after 2b9b8ebbf

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2024-10-31%2008%3A23%3A03 - master

ok 75        + create_cast                               842 ms
not ok 76    + constraints                              5685 ms
ok 77        + triggers                                18404 ms
ok 78        + select                                   3267 ms
not ok 79    + inherit                                 20746 ms
ok 80        + typed_table                              6472 ms
...

 SELECT *, tableoid::regclass::text FROM SYS_COL_CHECK_TBL;
-  city   |   state    | is_capital | altitude |     tableoid      
----------+------------+------------+----------+-------------------
- Seattle | Washington | f          |      100 | sys_col_check_tbl
-(1 row)
-
+ERROR:  could not read blocks 0..0 in file "global/2672": read only 0 of 8192 bytes

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=schnauzer&dt=2024-10-31%2011%3A10%3A37 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=broadbill&dt=2024-10-31%2013%3A34%3A08 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mamushi&dt=2024-10-31%2016%3A08%3A43 - master

Relcache refactoring \ call to RelationInitPhysicalAddr(relation) missing

Fix refreshing physical relfilenumber on shared index

XversionUpgrade-REL9_2_STABLE-xxx fails on crake after time zone data update

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2024-10-29%2017%3A23%3A45 - master

upgrade.crake/HEAD/dumpdiff-REL9_2_STABLE
--- /home/andrew/bf/root/upgrade.crake/HEAD/origin-REL9_2_STABLE.sql.fixed	2024-10-29 13:40:01.778445456 -0400
+++ /home/andrew/bf/root/upgrade.crake/HEAD/converted-REL9_2_STABLE-to-HEAD.sql.fixed	2024-10-29 13:40:01.780445460 -0400
@@ -206462,12 +206462,12 @@
 1997-02-14 20:32:01-05
 1997-02-15 20:32:01-05
 1997-02-16 20:32:01-05
-0097-02-16 20:32:01-05 BC
-0097-02-16 20:32:01-05
-0597-02-16 20:32:01-05
-1097-02-16 20:32:01-05
-1697-02-16 20:32:01-05
-1797-02-16 20:32:01-05
+0097-02-16 20:35:59-04:56:02 BC
+0097-02-16 20:35:59-04:56:02
+0597-02-16 20:35:59-04:56:02
+1097-02-16 20:35:59-04:56:02
+1697-02-16 20:35:59-04:56:02
+1797-02-16 20:35:59-04:56:02
 1897-02-16 20:32:01-05
 1997-02-16 20:32:01-05
 2097-02-16 20:32:01-05

pgsql: Update time zone data files to tzdata release 2024b.\ side-effects of 2024b on PST8PDT and other SysV-derived timezones

pgsql: Update time zone data files to tzdata release 2024b.\ old branches were rebuilt using 'America/New_York"

sepgsql/ddl.sql fails due to unexpected output after 89e51abcb

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rhinoceros&dt=2024-10-31%2020%3A52%3A13 - master

# +++ regress install-check in contrib/sepgsql +++
# using postmaster on /tmp/buildfarm-w9a0n0, port 5678
ok 1         - label                                    1298 ms
ok 2         - dml                                      1007 ms
not ok 3     - ddl                                      1003 ms
...

---
contrib/sepgsql/regression.diffs
--- /opt/src/pgsql-git/build-farm-root/HEAD/pgsql.build/contrib/sepgsql/expected/ddl.out	2024-05-13 03:52:12.247155159 -0700
+++ /opt/src/pgsql-git/build-farm-root/HEAD/pgsql.build/contrib/sepgsql/results/ddl.out	2024-10-31 14:04:13.083215399 -0700
@@ -154,6 +154,8 @@
 CREATE FUNCTION regtest_func(text,int[]) RETURNS bool LANGUAGE plpgsql
 	   AS 'BEGIN RAISE NOTICE ''regtest_func => %'', $1; RETURN true; END';
 LOG:  SELinux: allowed { search } scontext=unconfined_u:unconfined_r:sepgsql_regtest_superuser_t:s0 tcontext=system_u:object_r:sepgsql_schema_t:s0 tclass=db_schema name="pg_catalog" permissive=0
+LINE 1: CREATE FUNCTION regtest_func(text,int[]) RETURNS bool LANGUA...
+  
...

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rhinoceros&dt=2024-11-01%2002%3A52%3A12 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rhinoceros&dt=2024-11-01%2001%3A52%3A14 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rhinoceros&dt=2024-11-01%2008%3A52%3A12 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rhinoceros&dt=2024-11-01%2012%3A52%3A12 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rhinoceros&dt=2024-11-01%2015%3A52%3A12 - master

pgsql: Make all ereport() calls within gram.y provide error locations. \ tests of sepgsql need a refresh

Update contrib/sepgsql regression tests for commit 89e51abcb.

001_pg_bsd_indent.pl fails on Solaris/AIX due to illegal diff option

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2024-11-02%2020%3A06%3A10 - REL_16_STABLE

# +++ tap check in src/tools/pg_bsd_indent +++

#   Failed test 'pg_bsd_indent output matches for binary'
#   at t/001_pg_bsd_indent.pl line 50.
...

---
pgsql.build/src/tools/pg_bsd_indent/tmp_check/log/regress_log_001_pg_bsd_indent
# Running: diff -upd /export/home/nm/farm/studio64v12_6/REL_16_STABLE/pgsql/src/tools/pg_bsd_indent/tests/binary.0.stdout binary.out
/usr/bin/diff: illegal option -- p

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2024-11-03%2007%3A31%3A13 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sungazer&dt=2024-11-03%2020%3A21%3A01 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=tern&dt=2024-11-03%2020%3A27%3A56 - REL_16_STABLE

pgsql: Use portable diff options in pg_bsd_indent's regression test.

Use portable diff options in pg_bsd_indent's regression test.

plperl_env.sql fails with `vcregress plcheck` due to REGRESS_OPTS lost (after 8fe3e697a)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bowerbird&dt=2024-11-11%2014%3A30%3A05 - REL_12_STABLE

test plperl_env                   ... FAILED      120 ms

---
pgsql.build/src/pl/plperl/regression.diffs
--- H:/prog/bf/root/REL_12_STABLE/pgsql.build/src/pl/plperl/expected/plperl_env.out	2024-11-11 10:00:00.848816600 -0500
+++ H:/prog/bf/root/REL_12_STABLE/pgsql.build/src/pl/plperl/results/plperl_env.out	2024-11-11 10:00:05.226265200 -0500
@@ -5,6 +5,7 @@
    RETURNS text[]
    AS '/lib/regress.dll', 'get_environ'
    LANGUAGE C STRICT;
+ERROR:  could not access file "/lib/regress.dll": No such file or directory
 -- fetch the process environment

pgsql: src/tools/msvc: Respect REGRESS_OPTS in plcheck.

src/tools/msvc: Respect REGRESS_OPTS in plcheck.

XversionUpgrade-REL_12_STABLE-XXX fails due to referenced library missing (after b7e3a52a8)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2024-11-11%2018%3A50%3A23 - master

upgrade.crake/HEAD/REL_12_STABLE-upgrade.log
...
Checking for presence of required libraries                   fatal

Your installation references loadable libraries that are missing from the
new installation.  You can add these libraries to the new installation,
or remove the functions using them from the old installation.  A list of
problem libraries is in the file:
    /home/andrew/bf/root/upgrade.crake/HEAD/inst/REL_12_STABLE-upgrade/pg_upgrade_output.d/20241111T140702.275/loadable_libraries.txt
Failure, exiting

---
upgrade.crake/HEAD/inst/REL_12_STABLE-20241111T140702.275/loadable_libraries.txt
could not load library "/home/andrew/bf/root/REL_12_STABLE/pgsql.build/src/pl/plperl/../../../src/test/regress/regress.so": ERROR:  could not access file "/home/andrew/bf/root/REL_12_STABLE/pgsql.build/src/pl/plperl/../../../src/test/regress/regress.so": No such file or directory
In database: pl_regression_plperl

Fix cross-version upgrade tests.

plperl_env.sql fails with meson due to line numbers mismatch because of comments not stripped

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2024-11-11%2014%3A26%3A57 - master

 42/303 postgresql:plperl / plperl/regress                                              ERROR              2.33s   exit status 1

---
pgsql.build/testrun/plperl/regress/regression.diffs
--- /home/bf/bf-build/skink-master/HEAD/pgsql/src/pl/plperl/expected/plperl_env.out	2024-11-11 14:27:00.761078836 +0000
+++ /home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/plperl/regress/results/plperl_env.out	2024-11-11 14:28:37.729351724 +0000
@@ -49,5 +49,5 @@
    }
 
 $$ LANGUAGE plperl;
-WARNING:  attempted alteration of $ENV{TEST_PLPERL_ENV_FOO} at line 12.
+WARNING:  attempted alteration of $ENV{TEST_PLPERL_ENV_FOO} at line 43.
 NOTICE:  environ unaffected

Avoid bizarre meson behavior with backslashes in command arguments.

privileges.sql and rowsecurity.sql fail due to lack of non-superuser connections for parallel workers after 5a2fed911

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sawshark&dt=2024-11-11%2020%3A12%3A59 - master

not ok 114   + privileges                              15831 ms
...
not ok 121   + rowsecurity                              7502 ms

---
pgsql.build/src/test/regress/regression.diffs
--- /home/builder/pgbf_builds/HEAD/pgsql.build/src/test/regress/expected/privileges.out	Mon Nov 11 22:12:42 2024
+++ /home/builder/pgbf_builds/HEAD/pgsql.build/src/test/regress/results/privileges.out	Mon Nov 11 22:17:26 2024
@@ -73,11 +73,7 @@
 SET ROLE regress_priv_user3;
 GRANT regress_priv_user1 TO regress_priv_user4;
 SELECT grantor::regrole FROM pg_auth_members WHERE roleid = 'regress_priv_user1'::regrole and member = 'regress_priv_user4'::regrole;
-      grantor       
---------------------
- regress_priv_user2
-(1 row)
-
+ERROR:  remaining connection slots are reserved for roles with the SUPERUSER attribute
 RESET ROLE;
...
--- /home/builder/pgbf_builds/HEAD/pgsql.build/src/test/regress/expected/rowsecurity.out	Mon Nov 11 22:12:42 2024
+++ /home/builder/pgbf_builds/HEAD/pgsql.build/src/test/regress/results/rowsecurity.out	Mon Nov 11 22:17:17 2024
@@ -113,30 +113,7 @@
 (3 rows)
 
 \\d document
-        Table "regress_rls_schema.document"
...
+ERROR:  remaining connection slots are reserved for roles with the SUPERUSER attribute

Parallel workers use AuthenticatedUserId for connection privilege checks.

test_regex.sql fails on PPC/AIX animals in v14/v15 after 2496c3f6f

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hornet&dt=2024-11-15%2023%3A49%3A38 - REL_15_STABLE

test test_regex                   ... FAILED      686 ms

---
pgsql.build/src/test/modules/test_regex/regression.diffs
--- /home/nm/farm/xlc64/REL_15_STABLE/pgsql.build/src/test/modules/test_regex/expected/test_regex.out	2024-11-15 23:48:42.000000000 +0000
+++ /home/nm/farm/xlc64/REL_15_STABLE/pgsql.build/src/test/modules/test_regex/results/test_regex.out	2024-11-16 05:04:14.000000000 +0000
@@ -2080,11 +2080,7 @@
  (2 rows)
  
  select * from test_regex('[^\\d\\D]', '0123456789abc*', 'ILPE');
-                        test_regex                       
- --------------------------------------------------------
-  {0,REG_UBBS,REG_UNONPOSIX,REG_ULOCALE,REG_UIMPOSSIBLE}
- (1 row)
- 
+ ERROR:  invalid regular expression: out of memory
  -- check char classes' handling of newlines

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mandrill&dt=2024-11-17%2008%3A22%3A22 - REL_15_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=tern&dt=2024-11-17%2002%3A29%3A18 - REL_15_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mandrill&dt=2024-11-17%2002%3A24%3A03 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mandrill&dt=2024-11-17%2002%3A24%3A03 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=tern&dt=2024-11-16%2022%3A00%3A12 - REL_14_STABLE

BUG #18708: regex problem \ malloc(0) returning NULL triggers error

Fix recently-exposed portability issue in regex optimization.

RISC-V animals fail sporadically due to memory-related issues

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2024-08-20%2017%3A59%3A12 - HEAD

not ok 104   + hash_index                              14846 ms
# (test process exited with exit code 2)

---
pgsql.build/src/test/regress/log/postmaster.log
2024-08-20 20:56:47.318 CEST [2179731:95] LOG:  server process (PID 2184722) was terminated by signal 11: Segmentation fault
2024-08-20 20:56:47.318 CEST [2179731:96] DETAIL:  Failed process was running: COPY hash_f8_heap FROM 
'/home/pgbf/buildroot/HEAD/pgsql.build/src/test/regress/data/hash.data';

---
stack trace: pgsql.build/src/test/regress/tmp_check/data/core
Core was generated by `postgres: pgbf regression [local] COPY                                        '.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000002ac8e62674 in heap_multi_insert (relation=0x3f9525c890, slots=0x2ae68a5b30, ntuples=<optimized out>, 
cid=<optimized out>, options=<optimized out>, bistate=0x2ae6891c18) at heapam.c:2296
2296            tuple->t_tableOid = slots[i]->tts_tableOid;
...
$1 = {si_signo = 11,  ... _sigfault = {si_addr = 0x2ae600cbcc}, ..

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2024-08-24%2016%3A32%3A23 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2024-08-26%2016%3A20%3A46 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2024-09-03%2016%3A38%3A46 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2024-09-16%2023%3A07%3A46 - REL_17_STABLE?
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2024-10-30%2022%3A10%3A20 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2024-11-09%2015%3A01%3A23 - REL_12_STABLE

RISC-V animals sporadically produce weird memory-related failures

RISC-V animals sporadically produce weird memory-related failures \ RISC-V animals upgraded

select_distinct.sql/select_distinct_on.sql fail due to name conflict (after a8ccf4e93)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=schnauzer&dt=2024-11-26%2000%3A51%3A20 - master

not ok 91    + select_distinct                          1053 ms
not ok 92    + select_distinct_on                       1010 ms

---
pgsql.build/src/test/regress/regression.diffs
--- /home/pgbf/buildroot/HEAD/pgsql.build/src/test/regress/expected/select_distinct.out	Tue Nov 26 01:51:23 2024
+++ /home/pgbf/buildroot/HEAD/pgsql.build/src/test/regress/results/select_distinct.out	Tue Nov 26 01:52:52 2024
@@ -537,31 +537,13 @@
 SET max_parallel_workers_per_gather=2;
 EXPLAIN (COSTS OFF)
 SELECT DISTINCT y, x FROM distinct_tbl limit 10;
-                                         QUERY PLAN                                          
----------------------------------------------------------------------------------------------
- Limit
-   ->  Unique
-         ->  Gather Merge
-               Workers Planned: 1
-               ->  Unique
-                     ->  Parallel Index Only Scan using distinct_tbl_x_y_idx on distinct_tbl
-(6 rows)
-
+ERROR:  relation "distinct_tbl" does not exist
+LINE 2: SELECT DISTINCT y, x FROM distinct_tbl limit 10;
...
--- /home/pgbf/buildroot/HEAD/pgsql.build/src/test/regress/expected/select_distinct_on.out	Tue Nov 26 01:51:23 2024
+++ /home/pgbf/buildroot/HEAD/pgsql.build/src/test/regress/results/select_distinct_on.out	Tue Nov 26 01:52:52 2024
@@ -126,8 +126,13 @@
 -- the input path's ordering
 --
 CREATE TABLE distinct_tbl (x int, y int, z int);
+ERROR:  relation "distinct_tbl" already exists

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=morepork&dt=2024-11-26%2001%3A13%3A45 - master

Reordering DISTINCT keys to match input path's pathkeys \ the name "distinct_tbl" used in two scripts

Fix test case from a8ccf4e93

011_generated.pl fails due to incorrect expected log line added with 8fcd80258

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2024-11-27%2004%3A17%3A03 - master

# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 11.
[05:44:12] t/011_generated.pl ................. 
Dubious, test returned 255 (wstat 65280, 0xff00)
All 11 subtests passed 

---
pgsql.build/src/test/subscription/tmp_check/log/regress_log_011_generated
[05:41:11.702](0.447s) ok 11 - tab3 incremental replication, when publish_generated_columns=true
#### Begin standard error
psql:<stdin>:1: NOTICE:  dropped replication slot "sub1" on publisher
#### End standard error
#### Begin standard error
psql:<stdin>:3: NOTICE:  created replication slot "sub1" on publisher
#### End standard error
timed out waiting for match: (?^:ERROR: ( [A-Z0-9]:)? logical replication target relation "public.t1" has incompatible generated columns: "c2", "c3") at t/011_generated.pl line 363.
# Postmaster PID for node "publisher" is 2990522
### Stopping node "publisher" using mode immediate

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2024-11-27%2007%3A33%3A03 - master

Improve the error message for logical replication of regular column to generated column\ new test to verify the log was incorrect

Fix buildfarm failure from commit 8fcd80258b.

Tests fail on avocet due to timeout after upgrading buildfarm client to REL_18

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=avocet&dt=2024-11-22%2020%3A11%3A49 - REL_13_STABLE

check (01:21:50)
check-pg_upgrade (02:17:52)
lastcommand (00:14:44)
...
'script_version' => 'REL_18',
...
timed out after 14400 secs

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=avocet&dt=2024-11-22%2016%3A11%3A23 - REL_12_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=avocet&dt=2024-11-23%2000%3A12%3A05 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=avocet&dt=2024-11-23%2004%3A12%3A18 - REL_15_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=avocet&dt=2024-11-23%2008%3A12%3A36 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=avocet&dt=2024-11-23%2012%3A12%3A50 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=avocet&dt=2024-11-23%2016%3A13%3A05 - master

Announcing Release 18 of the PostgreSQL Buildfarm client / timeout should be increased on avocet

Announcing Release 18 of the PostgreSQL Buildfarm client / wait_timeout changed from undefined to 0

regression tests fail with segmentation faults on riscv64 with llvm enabled

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2024-11-30%2018%3A16%3A37 - REL_12_STABLE

2024-11-30 19:34:53.302 CET [13395:4] LOG:  server process (PID 13439) was terminated by signal 11: Segmentation fault
2024-11-30 19:34:53.302 CET [13395:5] DETAIL:  Failed process was running: SELECT '' AS tf_12, BOOLTBL1.*, BOOLTBL2.*
	   FROM BOOLTBL1, BOOLTBL2
	   WHERE BOOLTBL2.f1 <> BOOLTBL1.f1;

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2024-11-30%2018%3A35%3A17 - REL_13_STABLE

RISC-V animals sporadically produce weird memory-related failures \ --with-llvm causes segmentation faults

Miscellaneous regress tests fail due to segfaults/assertion failures after d28dff3f6

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fritillary&dt=2024-12-03%2004%3A13%3A00 - master

# parallel group (20 tests):  regproc txid int4 pg_lsn uuid varchar char float4 name oid float8 text enum int2 int8 money boolean bit numeric rangetypes
ok 2         + boolean                                  1623 ms
ok 3         + char                                      331 ms
ok 4         + name                                      464 ms
ok 5         + varchar                                   328 ms
ok 6         + text                                      736 ms
ok 7         + int2                                     1069 ms
ok 8         + int4                                      272 ms
ok 9         + int8                                     1306 ms
ok 10        + oid                                       554 ms
ok 11        + float4                                    362 ms
ok 12        + float8                                    618 ms
not ok 13    + bit                                      1806 ms
# (test process exited with exit code 2)
not ok 14    + numeric                                  1878 ms
# (test process exited with exit code 2)
ok 15        + txid                                      260 ms
ok 16        + uuid                                      302 ms
ok 17        + enum                                      889 ms
ok 18        + money                                    1331 ms
not ok 19    + rangetypes                               1878 ms
# (test process exited with exit code 2)
ok 20        + pg_lsn                                    293 ms
ok 21        + regproc                                   226 ms
...
---
pgsql.build/src/test/regress/log/postmaster.log
2024-12-03 04:21:42.150 UTC [2773168:10] LOG:  client backend (PID 2773211) was terminated by signal 11: Segmentation fault
2024-12-03 04:21:42.150 UTC [2773168:11] DETAIL:  Failed process was running: SELECT * FROM pg_input_error_info('01010Z01', 'bit(8)');

2024-12-03 04:21:42.862 UTC [2773168:15] LOG:  client backend (PID 2773696) was terminated by signal 11: Segmentation fault
2024-12-03 04:21:42.862 UTC [2773168:16] DETAIL:  Failed process was running: SELECT * FROM pg_input_error_info('@ 30 eons ago', 'interval');

2024-12-03 04:21:44.449 UTC [2773168:26] LOG:  client backend (PID 2773956) was terminated by signal 11: Segmentation fault
2024-12-03 04:21:44.449 UTC [2773168:27] DETAIL:  Failed process was running: SELECT * FROM pg_input_error_info('a <100000> b', 'tsquery');

2024-12-03 04:21:56.425 UTC [2773168:34] LOG:  client backend (PID 2776542) was terminated by signal 6: Aborted
2024-12-03 04:21:56.425 UTC [2773168:35] DETAIL:  Failed process was running: SELECT max(row(a,b)) FROM aggtest;

---
stack trace: pgsql.build/src/test/regress/tmp_check/data/core.2773211
Core was generated by `postgres: centos regression [local] SELECT                                     '.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007fff7d8d915c in __strcmp_power9 () from /lib64/glibc-hwcaps/power10/libc.so.6
#0  0x00007fff7d8d915c in __strcmp_power9 () from /lib64/glibc-hwcaps/power10/libc.so.6
#1  0x00000000100cb30c in equalRowTypes (tupdesc1=<optimized out>, tupdesc2=<optimized out>) at tupdesc.c:644
#2  0x00000000107c4040 in record_type_typmod_compare (a=<optimized out>, b=<optimized out>, size=<optimized out>) at typcache.c:2039
#3  0x00000000107d9ce8 in hash_search_with_hash_value (hashp=0x44ddd060, keyPtr=0x7fffd40b09a8, hashvalue=85290192, action=HASH_FIND, foundPtr=0x7fffd40b0948) at dynahash.c:1021
#4  0x00000000107c3d54 in assign_record_type_typmod (tupDesc=0x44cd6698) at typcache.c:2082
#5  0x00000000107d5734 in internal_get_result_type (funcid=<optimized out>, call_expr=<optimized out>, rsinfo=<optimized out>, resultTypeId=<optimized out>, resultTupleDesc=0x7fffd40b0bb8) at funcapi.c:469
...

---
stack trace: pgsql.build/src/test/regress/tmp_check/data/core.2776542
Core was generated by `postgres: centos regression [local] SELECT                                     '.
Program terminated with signal SIGABRT, Aborted.
#0  0x00007fff7d8a56a8 in __pthread_kill_implementation () from /lib64/glibc-hwcaps/power10/libc.so.6
#0  0x00007fff7d8a56a8 in __pthread_kill_implementation () from /lib64/glibc-hwcaps/power10/libc.so.6
#1  0x00007fff7d847f20 in raise () from /lib64/glibc-hwcaps/power10/libc.so.6
#2  0x00007fff7d82a574 in abort () from /lib64/glibc-hwcaps/power10/libc.so.6
#3  0x00000000107c5d94 in ExceptionalCondition (conditionName=<optimized out>, fileName=<optimized out>, lineNumber=<optimized out>) at assert.c:66
#4  0x00000000100bb928 in TupleDescCompactAttr (tupdesc=0x7fff725a1000, i=0) at ../../../../src/include/access/tupdesc.h:172
#5  heap_deform_tuple (tuple=<optimized out>, tupleDesc=0x7fff725a1000, values=0x44e2b240, isnull=0x44e2b260) at heaptuple.c:1376
#6  0x0000000010721f3c in record_out (fcinfo=0x7fffd40b0ac0) at rowtypes.c:390
#7  0x00000000107d35b0 in FunctionCall1Coll (flinfo=0x44e07038, collation=0, arg1=<optimized out>) at fmgr.c:1139

pgsql: Introduce CompactAttribute array in TupleDesc \ buildfarm shows something is broken

Revert "Introduce CompactAttribute array in TupleDesc"

plperl_setup.sql fails on 32-bit systems because of perl ABI mismatch after 962da900a

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=grison&dt=2024-12-04%2003%3A10%3A08 - master

# +++ regress install-check in src/pl/plperl +++
# using postmaster on /home/pgbf/buildroot/tmp/buildfarm-Sht_Xi, port 5678
not ok 1     - plperl_setup                              403 ms
# (test process exited with exit code 2)
...

---
inst/logfile
2024-12-04 05:33:01.919 CET [2222:18] pg_regress/plperl_setup LOG:  statement: CREATE EXTENSION plperl;
Util.c: loadable library and perl binaries are mismatched (got handshake key 0x9280080, needed 0x9380080)

Cannot find a working 64-bit integer type on Illumos \ system headers included before pg_config.h

Fix header inclusion order in c.h.

select_into.sql fails due to missing BUFFERS OFF (after c2a4078eb)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=tayra&dt=2024-12-11%2009%3A45%3A08 - master

not ok 90    + select_into                               283 ms
...
# 1 of 223 tests failed.

---
---
pgsql.build/src/test/regress/regression.diffs
--- /repos/client-code-REL_18/HEAD/pgsql.build/src/test/regress/expected/select_into.out	2024-12-11 06:45:13.939852597 -0300
+++ /repos/client-code-REL_18/HEAD/pgsql.build/src/test/regress/results/select_into.out	2024-12-11 06:46:20.672076602 -0300
@@ -57,7 +57,9 @@
 --------------------------------------
  ProjectSet (actual rows=3 loops=1)
    ->  Result (actual rows=1 loops=1)
-(2 rows)
+ Planning:
+   Buffers: shared hit=3
+(4 rows)

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=calliphoridae&dt=2024-12-11%2009%3A37%3A02 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bushmaster&dt=2024-12-11%2009%3A37%3A33 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=kestrel&dt=2024-12-11%2009%3A36%3A54 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=serinus&dt=2024-12-11%2009%3A36%3A34 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2024-12-11%2009%3A43%3A03 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2024-12-11%2009%3A42%3A04 - master

Add missing BUFFERS OFF in select_into regression tests

matview.sql and misc_functions.sql fail on cache-release-testing animals (after c2a4078eb)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2024-12-11%2010%3A03%3A03 - master

not ok 118   + matview                                 17804 ms
...
not ok 139   + misc_functions                           4111 ms
...
# 2 of 223 tests failed.

---
pgsql.build/src/test/regress/regression.diffs
--- /home/ec2-user/bf/root/HEAD/pgsql/src/test/regress/expected/matview.out	2024-12-11 10:03:04.454700734 +0000
+++ /home/ec2-user/bf/root/HEAD/pgsql.build/src/test/regress/results/matview.out	2024-12-11 10:06:04.465742830 +0000
@@ -631,7 +631,9 @@
 --------------------------------------
  ProjectSet (actual rows=10 loops=1)
    ->  Result (actual rows=1 loops=1)
-(2 rows)
+ Planning:
+   Buffers: shared hit=145
+(4 rows)
...

--- /home/ec2-user/bf/root/HEAD/pgsql/src/test/regress/expected/misc_functions.out	2024-12-11 10:03:04.454700734 +0000
+++ /home/ec2-user/bf/root/HEAD/pgsql.build/src/test/regress/results/misc_functions.out	2024-12-11 10:06:29.585888248 +0000
@@ -650,7 +650,10 @@
                                     explain_mask_costs                                    
 ------------------------------------------------------------------------------------------
  Function Scan on generate_series g  (cost=N..N rows=30 width=N) (actual rows=30 loops=1)
-(1 row)
+   Buffers: shared hit=58
+ Planning:
+   Buffers: shared hit=174
+(4 rows)
...

Add missing BUFFERS OFF in regression tests, take 2

pg_stat_statements/level_tracking.sql fails on cache-release-testing animals (after c2a4078eb)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2024-12-11%2010%3A23%3A03 - master

not ok 5     - level_tracking                           1608 ms

---
pgsql.build/contrib/pg_stat_statements/regression.diffs
--- /home/ec2-user/bf/root/HEAD/pgsql/contrib/pg_stat_statements/expected/level_tracking.out	2024-12-11 10:23:02.881643853 +0000
+++ /home/ec2-user/bf/root/HEAD/pgsql.build/contrib/pg_stat_statements/results/level_tracking.out	2024-12-11 10:29:40.303947627 +0000
@@ -907,14 +907,18 @@
            QUERY PLAN           
 --------------------------------
  Result (actual rows=1 loops=1)
-(1 row)
+ Planning:
+   Buffers: shared hit=28
+(3 rows)
...

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2024-12-11%2020%3A23%3A03 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2024-12-11%2018%3A43%3A03 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2024-12-11%2011%3A53%3A03 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=avocet&dt=2024-12-11%2015%3A26%3A35 - master

Proposals for EXPLAIN: rename ANALYZE to EXECUTE and extend VERBOSE \ BUFFERS OFF missing in level_tracking.sql

Fix further fallout from EXPLAIN ANALYZE BUFFERS change

009_twophase.pl might fail when replica is lagging behind

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hornet&dt=2024-12-13%2022%3A14%3A10 - REL_13_STABLE

# pump_until: process terminated unexpectedly when searching for "(?^:background_psql: QUERY_SEPARATOR)" with stream: ""
# Looks like your test exited with 29 just after 13.
[00:50:47] t/009_twophase.pl .................... 
Dubious, test returned 29 (wstat 7424, 0x1d00)
Failed 14/27 subtests 

---
pgsql.build/src/test/recovery/tmp_check/log/regress_log_009_twophase
# issuing query via background psql: SELECT count(*) FROM t_009_tbl_standby_mvcc
# pump_until: process terminated unexpectedly when searching for "(?^:background_psql: QUERY_SEPARATOR)" with stream: ""
query failed: psql:<stdin>:6: ERROR:  relation "t_009_tbl_standby_mvcc" does not exist
LINE 1: SELECT count(*) FROM t_009_tbl_standby_mvcc

Visibility bug with prepared transaction with subtransactions on standby \ the test lacks standby synchronization

Make 009_twophase.pl test pass with recovery_min_apply_delay set

snakefly fails in the ssl_passphrase_callback-check stage (after a70e01d43)

make -j1  checkprep >>'/opt/postgres/bf/v11/buildroot/HEAD/pgsql.build'/tmp_install/log/install.log 2>&1
make: *** [temp-install] Error 2

Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~? \ old buildfarm client (v11)

Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~? \ buildfarm client upgraded

stats.sql fails due to unexpected fsyncs (after 9aea73fc6)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=grassquit&dt=2024-12-19%2016%3A28%3A58 - master

215/306 postgresql:recovery / recovery/027_stream_regress                               ERROR           343.00s   exit status 1
stderr:
#   Failed test 'regression tests pass'
#   at /home/bf/bf-build/grassquit/HEAD/pgsql/src/test/recovery/t/027_stream_regress.pl line 95.
#          got: '256'
#     expected: '0'
# Looks like you failed 1 test of 9.

--- /home/bf/bf-build/grassquit/HEAD/pgsql/src/test/regress/expected/stats.out	2024-12-19 04:44:08.779311933 +0000
+++ /home/bf/bf-build/grassquit/HEAD/pgsql.build/testrun/recovery/027_stream_regress/data/results/stats.out	2024-12-19 16:37:41.351784840 +0000
@@ -1333,7 +1333,7 @@
       AND :my_io_sum_shared_after_fsyncs= 0);
  ?column? 
 ----------
- t
+ f
 (1 row)
 
 -- Change the tablespace so that the table is rewritten directly, then SELECT

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=grassquit&dt=2024-12-19%2010%3A43%3A57 - master

per backend I/O statistics \ grassquit failures

Relax regression test for fsync check of backend-level stats

Several buildfarm animals fail tests because of shared memory error

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2024-12-16%2012%3A27%3A01 - master

# poll_query_until timed out executing this query:
#  SELECT last_archived_wal FROM pg_stat_archiver 
# expecting this output:
# 000000010000000000000002
# last actual query output:
# 
# with stderr:
# psql: error: connection to server on socket "/home/bf/proj/bf/build-farm-17/buildroot/tmp/D032mdJ4c4/.s.PGSQL.16723" failed: FATAL:  could not open shared memory segment "/PostgreSQL.1516345622": No such file or directory
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 29 just after 7.
[12:38:23] t/020_archive_status.pl ...............

Several buildfarm animals fail tests because of shared memory error \ REMOVEIPC not configured correctly

Several buildfarm animals fail tests because of shared memory error \ REMOVEIPC was set to yes

posgtres_fdw/query_cancel fails due to an unexpected warning on canceling a statement

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=treehopper&dt=2024-09-30%2019%3A21%3A14 - REL_17_STABLE

ok 1         - postgres_fdw                             7625 ms
not ok 2     - query_cancel                            30166 ms
1..2
# 1 of 2 tests failed.

--- /home/linux1/17-treehopper/buildroot/REL_17_STABLE/pgsql.build/contrib/postgres_fdw/expected/query_cancel.out	2024-09-30 19:20:58.839809149 +0000
+++ /home/linux1/17-treehopper/buildroot/REL_17_STABLE/pgsql.build/contrib/postgres_fdw/results/query_cancel.out	2024-09-30 19:35:01.471960306 +0000
@@ -29,4 +29,5 @@
 -- This would take very long if not canceled:
 SELECT count(*) FROM ft1 a CROSS JOIN ft1 b CROSS JOIN ft1 c CROSS JOIN ft1 d;
 ERROR:  canceling statement due to statement timeout
+WARNING:  could not get result of cancel request due to timeout

---
inst/logfile
2024-09-30 19:34:31.347 UTC [3201033:8] pg_regress/query_cancel LOG:  statement: SET LOCAL statement_timeout = '100ms';
2024-09-30 19:34:31.347 UTC [3201033:9] pg_regress/query_cancel LOG:  statement: SELECT count(*) FROM ft1 a CROSS JOIN ft1 b CROSS JOIN ft1 c CROSS JOIN ft1 d;
2024-09-30 19:34:31.347 UTC [3201034:13] fdw_retry_check LOG:  execute <unnamed>: DECLARE c2 CURSOR FOR
	SELECT count(*) FROM ((("S 1"."T 1" r1 INNER JOIN "S 1"."T 1" r2 ON (TRUE)) INNER JOIN "S 1"."T 1" r4 ON (TRUE)) INNER JOIN "S 1"."T 1" r6 ON (TRUE))
2024-09-30 19:34:31.464 UTC [3201033:10] pg_regress/query_cancel ERROR:  canceling statement due to statement timeout
2024-09-30 19:34:31.464 UTC [3201033:11] pg_regress/query_cancel STATEMENT:  SELECT count(*) FROM ft1 a CROSS JOIN ft1 b CROSS JOIN ft1 c CROSS JOIN ft1 d;
2024-09-30 19:34:31.466 UTC [3201035:1] [unknown] LOG:  connection received: host=[local]
2024-09-30 19:34:31.474 UTC [3201034:14] fdw_retry_check LOG:  statement: FETCH 100 FROM c2
2024-09-30 19:35:01.485 UTC [3201033:12] pg_regress/query_cancel WARNING:  could not get result of cancel request due to timeout

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=froghopper&dt=2024-10-25%2008%3A31%3A55 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=pipit&dt=2024-11-13%2001%3A12%3A28 - master

Add non-blocking version of PQcancel \ A newfound way to break the test

postgres_fdw: re-issue cancel requests a few times if necessary.

Regression tests fail on OpenBSD due to low semmns value

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sawshark&dt=2024-07-22%2001%3A20%3A22 - master

--- /home/builder/pgbf_builds/HEAD/pgsql.build/src/test/regress/expected/prepared_xacts.out	Mon Jul 22 04:20:08 2024
+++ /home/builder/pgbf_builds/HEAD/pgsql.build/src/test/regress/results/prepared_xacts.out	Mon Jul 22 04:21:45 2024
@@ -216,55 +216,4 @@
 rollback;
 -- Disconnect, we will continue testing in a different backend
 \\c -
--- There should still be two prepared transactions
...
+\\connect: connection to server on socket "/home/builder/pgbf_builds/tmp/pg_regress-nFb732/.s.PGSQL.5678" failed: FATAL:  sorry, too many clients already

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sawshark&dt=2024-11-25%2006%3A20%3A22 - REL_17_STABLE

Also transactions.sql times out on OpenBSD

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sawshark&dt=2024-12-11%2012%3A20%3A05 - master

ok 89        - sanity_check                              322 ms
# parallel group (20 tests):  delete prepared_xacts select_having select_distinct_on select_implicit random select_into namespace portals subselect case union select_distinct update hash_index join arrays aggregates btree_index
===================================================
timed out after 14400 secs

Regression tests fail on OpenBSD due to low semmns value

Try to avoid semaphore-related test failures on NetBSD/OpenBSD.

027_stream_regress.pl fails with timeout when waiting for catchup

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2024-05-22%2021%3A55%3A00 - HEAD

Waiting for replication conn standby_1's replay_lsn to pass 0/15218DE8 on primary
[22:07:20.266](292.694s) # poll_query_until timed out executing this query:
# SELECT '0/15218DE8' <= replay_lsn AND state = 'streaming'
#          FROM pg_catalog.pg_stat_replication
#          WHERE application_name IN ('standby_1', 'walreceiver')
# expecting this output:
# t
# last actual query output:
# f
# with stderr:
timed out waiting for catchup at /home/bf/bf-build/skink-master/HEAD/pgsql/src/test/recovery/t/027_stream_regress.pl line 103.

---
027_stream_regress_standby_1.log
2024-05-22 21:57:39.199 UTC [598721][postmaster][:0] LOG:  starting PostgreSQL 17beta1 on x86_64-linux, compiled by gcc-13.2.0, 64-bit
...
2024-05-22 22:05:07.888 UTC [599624][checkpointer][:0] LOG:  restartpoint starting: time
2024-05-22 22:05:21.622 UTC [599624][checkpointer][:0] LOG:  restartpoint complete: wrote 31 buffers (24.2%); 0 WAL file(s) added, 0 removed, 4 recycled; write=11.770 s, sync=0.890 s, total=13.735 s; sync files=423, longest=0.111 s, average=0.003 s; distance=65698 kB, estimate=67034 kB; lsn=0/126ACA48, redo lsn=0/1202D1B8
2024-05-22 22:05:21.622 UTC [599624][checkpointer][:0] LOG:  recovery restart point at 0/1202D1B8
2024-05-22 22:05:21.622 UTC [599624][checkpointer][:0] DETAIL:  Last completed transaction was at log time 2024-05-22 22:01:29.448409+00.
2024-05-22 22:07:20.336 UTC [601831][walreceiver][:0] FATAL:  could not receive data from WAL stream: server closed the connection unexpectedly
		This probably means the server terminated abnormally
		before or while processing the request.
2024-05-22 22:07:20.908 UTC [598721][postmaster][:0] LOG:  received immediate shutdown request
2024-05-22 22:07:21.251 UTC [598721][postmaster][:0] LOG:  database system is shut down

Recent 027_streaming_regress.pl hangs \ Test concurrency reducing

Fixed Test Failures - 2025

regress-running/regress fails on skink due to timeout

(skink is a Valgrind animal)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2024-06-04%2002%3A44%3A19 - HEAD

1/1 postgresql:regress-running / regress-running/regress TIMEOUT        3000.06s   killed by signal 15 SIGTERM

---
inst/logfile ends with:
2024-06-04 03:39:24.664 UTC [3905755][client backend][5/1787:16793] ERROR:  column "c2" of relation "test_add_column" 
already exists
2024-06-04 03:39:24.664 UTC [3905755][client backend][5/1787:16793] STATEMENT:  ALTER TABLE test_add_column
         ADD COLUMN c2 integer, -- fail because c2 already exists
         ADD COLUMN c3 integer primary key;
2024-06-04 03:39:30.815 UTC [3905755][client backend][5/0:0] LOG: could not send data to client: Broken pipe
2024-06-04 03:39:30.816 UTC [3905755][client backend][5/0:0] FATAL: connection to client lost

Recent 027_streaming_regress.pl hangs \ meson TIMEOUT on skink

No such failures since 2024-06-28, looks like something was changed in the environment.

008_fsm_truncation failing on dodo in v14- due to slow fsync

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dodo&dt=2024-06-19%2010%3A15%3A08 - REL_14_STABLE

### Starting node "standby"
# Running: pg_ctl -D /media/pi/250gb/proj/bf2/v17/buildroot/REL_14_STABLE/pgsql.build/src/test/recovery/tmp_check/t_008_fsm_truncation_standby_data/pgdata -l /media/pi/250gb/proj/bf2/v17/buildroot/REL_14_STABLE/pgsql.build/src/test/recovery/tmp_check/log/008_fsm_truncation_standby.log -o --cluster-name=standby start
waiting for server to start........................................................................................................................... stopped waiting
pg_ctl: server did not start in time
# pg_ctl start failed; logfile:

---
008_fsm_truncation_standby.log:
2024-06-19 21:27:30.843 ACST [13244:1] LOG:  starting PostgreSQL 14.12 on armv7l-unknown-linux-gnueabihf, compiled by gcc (GCC) 15.0.0 20240617 (experimental), 32-bit
2024-06-19 21:27:31.768 ACST [13244:2] LOG:  listening on Unix socket "/media/pi/250gb/proj/bf2/v17/buildroot/tmp/vLgcHgvc7O/.s.PGSQL.50013"
2024-06-19 21:27:35.055 ACST [13246:1] LOG:  database system was interrupted; last known up at 2024-06-19 21:26:55 ACST
2024-06-19 21:29:38.320 ACST [13244:3] LOG:  received immediate shutdown request
2024-06-19 21:29:42.130 ACST [13244:4] LOG:  database system is shut down

recoveryCheck/008_fsm_truncation is failing on dodo in v14- (due to slow fsync?)

No such failures since 2024-07-02, looks like something was changed in the environment.

Also 002_limits.pl exited abnormally with 29 just after 2

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dodo&dt=2024-06-20%2007%3A18%3A46 - HEAD

# +++ tap install-check in src/test/modules/xid_wraparound +++
t/001_emergency_vacuum.pl .. ok
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 29 just after 2.
t/002_limits.pl ............ 
Dubious, test returned 29 (wstat 7424, 0x1d00)
All 2 subtests passed 
t/003_wraparounds.pl ....... ok

Test Summary Report
-------------------
t/002_limits.pl          (Wstat: 7424 Tests: 2 Failed: 0)
  Non-zero exit status: 29
  Parse errors: No plan found in TAP output
Files=3, Tests=10, 4235 wallclock secs ( 0.10 usr  0.13 sys + 18.05 cusr 12.76 csys = 31.04 CPU)
Result: FAIL

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dodo&dt=2024-07-02%2016%3A33%3A17 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2024-07-17%2014%3A57%3A13 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2024-07-17%2014%3A58%3A03 - HEAD

recoveryCheck/008_fsm_truncation is failing on dodo in v14- (due to slow fsync?) \ another dodo failure has the same cause

No such failures since 2024-07-17, looks like something was changed in the environment.

deadlock-soft.sql is failing on Fedora 42

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=caiman&dt=2024-11-11%2016%3A02%3A04 - REL_16_STABLE

not ok 24    - deadlock-soft                          741086 ms

---
pgsql.build/src/test/isolation/output_iso/regression.diffs
--- /repos/client-code-REL_18/REL_16_STABLE/pgsql.build/src/test/isolation/expected/deadlock-soft.out	2024-11-11 13:02:04.188815923 -0300
+++ /repos/client-code-REL_18/REL_16_STABLE/pgsql.build/src/test/isolation/output_iso/results/deadlock-soft.out	2024-11-11 13:26:13.849527129 -0300
@@ -7,11 +7,15 @@
 step e2l: LOCK TABLE a2 IN ACCESS EXCLUSIVE MODE; <waiting ...>
 step d1a2: LOCK TABLE a2 IN ACCESS SHARE MODE; <waiting ...>
 step d2a1: LOCK TABLE a1 IN ACCESS SHARE MODE; <waiting ...>
+isolationtester: canceling step d1a2 after 360 seconds
 step d1a2: <... completed>
+ERROR:  canceling statement due to user request
+step d2a1: <... completed>
 step d1c: COMMIT;
+isolationtester: canceling step e1l after 360 seconds
 step e1l: <... completed>
+ERROR:  canceling statement due to user request
 step e1c: COMMIT;
-step d2a1: <... completed>
 step d2c: COMMIT;

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=caiman&dt=2024-11-16%2004%3A24%3A24 - master

deadlock-soft isolation test is failing on newest Fedora

No such failures since 2024-11-16, OS was upgraded since then to Fedora 43, 44.

005_opclass_damage.pl fails on Windows animals due to timeout

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-07-25%2003%3A23%3A19 - HEAD

180/244 postgresql:pg_amcheck / pg_amcheck/005_opclass_damage                           TIMEOUT        3001.43s   exit status 1

---
regress_log_005_opclass_damage
[05:57:13.802](1835.196s) ok 1 - pg_amcheck all schemas, tables and indexes reports no corruption: exit code 0
[05:57:13.802](0.000s) ok 2 - pg_amcheck all schemas, tables and indexes reports no corruption: no stderr
[05:57:13.803](0.001s) ok 3 - pg_amcheck all schemas, tables and indexes reports no corruption: matches
# Running: pg_amcheck -p 10642 postgres
[06:05:32.533](498.730s) ok 4 - pg_amcheck all schemas, tables and indexes reports fickleidx corruption status (got 2 vs expected 2)
[06:05:32.533](0.000s) ok 5 - pg_amcheck all schemas, tables and indexes reports fickleidx corruption stdout /(?^:item order invariant violated for index "fickleidx")/
# Running: pg_amcheck --checkunique -p 10642 postgres

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-07-25%2016%3A02%3A33 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-07-26%2001%3A06%3A33 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-07-26%2006%3A13%3A01 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-07-26%2010%3A31%3A00 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-07-27%2021%3A36%3A58 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-07-27%2009%3A45%3A44 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-07-28%2004%3A45%3A07 - HEAD

fairywren timeout failures on the pg_amcheck/005_opclass_damage test

Simplify executor's determination of whether to use parallelism.

001_pgbench_with_server.pl fails due to IPC::Run losing stdout/stderr on macOS

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2025-01-13%2000%3A20%3A43 - master

(indri is a macOS animal)

[22:38:14.887](0.014s) ok 362 - pgbench script error: sleep undefined variable status (got 2 vs expected 2)
[22:38:14.887](0.000s) ok 363 - pgbench script error: sleep undefined variable stdout /(?^:processed: 0/1)/
[22:38:14.887](0.000s) not ok 364 - pgbench script error: sleep undefined variable stderr /(?^:sleep: undefined variable)/
[22:38:14.887](0.000s)
[22:38:14.887](0.000s) #   Failed test 'pgbench script error: sleep undefined variable stderr /(?^:sleep: undefined 
variable)/'
#   at t/001_pgbench_with_server.pl line 1242.
[22:38:14.887](0.000s) #                   ''
#     doesn't match '(?^:sleep: undefined variable)'

Other occurrences:
https://wiki.postgresql.org/wiki/Known_Buildfarm_Test_Failures_-_Archive#001_pgbench_with_server.pl_fails_due_to_IPC::Run_losing_stdout.2Fstderr_on_macOS

IPC::Run accepts bug reports \ pgbench test failed on indri

IPC-Run: Retry _read() on EINTR, instead of losing pipe contents.

initdb fails during make check due to lack of semaphores (after c758119e5)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sawshark&dt=2025-01-06%2021%3A20%3A05 - master

PATH="/home/builder/pgbf_builds/HEAD/pgsql.build/tmp_install/home/builder/pgbf_builds/HEAD/inst/bin:/home/builder/pgbf_builds/HEAD/pgsql.build/src/test/regress:$PATH" LD_LIBRARY_PATH="/home/builder/pgbf_builds/HEAD/pgsql.build/tmp_install/home/builder/pgbf_builds/HEAD/inst/lib" INITDB_TEMPLATE='/home/builder/pgbf_builds/HEAD/pgsql.build'/tmp_install/initdb-template  initdb --auth trust --no-sync --no-instructions --lc-messages=C --no-clean '/home/builder/pgbf_builds/HEAD/pgsql.build'/tmp_install/initdb-template >>'/home/builder/pgbf_builds/HEAD/pgsql.build'/tmp_install/log/initdb-template.log 2>&1
gmake: *** [../../../src/Makefile.global:425: temp-install] Error 1

---
pgsql.build/tmp_install/log/initdb-template.log
creating configuration files ... ok
running bootstrap script ... 2025-01-06 23:20:42.883 EET [60766] FATAL:  could not create semaphores: No space left on device
2025-01-06 23:20:42.883 EET [60766] DETAIL:  Failed system call was semget(389899, 20, 03600).

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sawshark&dt=2025-01-07%2003%3A20%3A05 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sawshark&dt=2025-01-07%2016%3A20%3A05 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sawshark&dt=2025-01-07%2020%3A20%3A05 - master

allow changing autovacuum_max_workers without restarting \ sawshark broken due to 13 new semaphores added

Lower default value of autovacuum_worker_slots in initdb as needed.

XversionUpgrade fails with pg_dump error after e65dbc992

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-01-23%2010%3A17%3A03 - master

upgrade.crake/HEAD/REL_10_STABLE-dump1.log
pg_dump: error: query failed: ERROR:  column "publish_gencols_none" does not exist
LINE 1: ...elete, false AS pubtruncate, false AS pubviaroot, PUBLISH_GE...
                                                             ^
pg_dump: detail: Query was: SELECT p.tableoid, p.oid, p.pubname, p.pubowner, p.puballtables, p.pubinsert, p.pubupdate, p.pubdelete, false AS pubtruncate, false AS pubviaroot, PUBLISH_GENCOLS_NONE AS pubgencols_type FROM pg_publication p
pg_dumpall: error: pg_dump failed on database "template1", exiting

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-01-23%2011%3A27%3A01 - master

Pgoutput not capturing the generated columns \ BF failed with dump error

Fix buildfarm failure introduced by commit e65dbc9927.

foreign_key.sql fails due to lack of ORDER BY (after b663b9436)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=morepork&dt=2025-01-23%2023%3A35%3A57 - master

diff -U3 /home/pgbf/buildroot/HEAD/pgsql.build/src/test/regress/expected/foreign_key.out /home/pgbf/buildroot/HEAD/pgsql.build/src/test/regress/results/foreign_key.out
--- /home/pgbf/buildroot/HEAD/pgsql.build/src/test/regress/expected/foreign_key.out	Fri Jan 24 00:35:56 2025
+++ /home/pgbf/buildroot/HEAD/pgsql.build/src/test/regress/results/foreign_key.out	Fri Jan 24 00:39:20 2025
@@ -1751,8 +1751,8 @@
 SELECT conname, convalidated FROM pg_constraint WHERE conrelid = 'fk_notpartitioned_fk'::regclass;
             conname             | convalidated 
 --------------------------------+--------------
- fk_notpartitioned_fk_a_b_fkey  | f
  fk_notpartitioned_fk_a_b_fkey1 | f
+ fk_notpartitioned_fk_a_b_fkey  | f
 (2 rows)
 ...

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mereswine&dt=2025-01-24%2011%3A29%3A21 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=taipan&dt=2025-01-23%2017%3A14%3A31 - master

Allow NOT VALID foreign key constraints on partitioned tables, \ some of the queries need ORDER BY

Fix instability in recently added regression tests

contrib-sepgsqlCheck on several animals due to having postgres|pgsql in installation path (after aeb8ea361)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=alligator&dt=2025-01-24%2011%3A50%3A20 - master

make -j1  checkprep >>'/home/postgres/proj/build-farm-17/buildroot/HEAD/pgsql.build'/tmp_install/log/install.log 2>&1
make: *** [../../src/Makefile.global:424: temp-install] Error 2
log files for step contrib-sepgsqlCheck:

Convert sepgsql tests to TAP \ check_install_is_complete expects to find files in wrong place

Fix check_install_is_complete

pg_amcheck/002_nonesuch,pl fails on Windows due to unexpected SSPI error (after eef4a33f6)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-01-23%2014%3A52%3A11 - master

131/301 postgresql:pg_amcheck / pg_amcheck/002_nonesuch                                 ERROR            47.45s   exit status 1
...
[16:23:32.590](0.001s) #   Failed test 'checking with a non-existent user stderr /(?^:role "no_such_user" does not exist)/'
#   at C:/prog/bf/root/HEAD/pgsql/src/bin/pg_amcheck/t/002_nonesuch.pl line 86.
[16:23:32.591](0.001s) #                   'pg_amcheck: error: connection to server at "127.0.0.1", port 10972 failed: FATAL:  SSPI authentication failed for user "no_such_user"
# '
#     doesn't match '(?^:role "no_such_user" does not exist)'
# Running: pg_amcheck template1

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-01-24%2006%3A40%3A08 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-01-25%2005%3A02%3A14 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-01-26%2008%3A42%3A35 - master

pg_createsubscriber TAP test wrapping makes command options hard to read. \ new test for amcheck.has to do with SSPI authentication

pg_amcheck: Fix test failure on Windows with non-existing role

module-test_misc-check fails with timeout on snakefly and copperhead (after ac00ff1c9)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=snakefly&dt=2025-02-10%2015%3A10%3A04 - REL_13_STABLE

module-commit_ts-check (00:00:18) 	lastcommand (00:00:04)...

===================================================
timed out after 14400 secs

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2025-02-10%2017%3A01%3A14 - REL_13_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=snakefly&dt=2025-02-10%2015%3A11%3A03 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=snakefly&dt=2025-02-10%2015%3A11%3A03 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=snakefly&dt=2025-02-10%2015%3A12%3A04 - REL_15_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=snakefly&dt=2025-02-10%2015%3A13%3A04 - REL_16_STABLE

Also new test t_001_test_escape fails on ARM animals

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=widowbird&dt=2025-02-10%2016%3A30%3A07 - REL_13_STABLE

#   Failed test 'test_escape returns 0'
#   at t/001_test_escape.pl line 25.
#          got: ''
#     expected: '1'
# Looks like you failed 1 test of 2.
[17:39:50] t/001_test_escape.pl .. 
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/2 subtests

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=turaco&dt=2025-02-10%2016%3A15%3A07 - REL_13_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dikkop&dt=2025-02-10%2016%3A12%3A18 - REL_13_STABLE

(no link to the public discussion)

Fix type in test_escape test

002_pg_upgrade.pl/check fails on mereswine due to a backend killed during execution of infinite_recurse.sql

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mereswine&dt=2024-06-26%2002%3A10%3A45 - REL_15_STABLE

(mereswine is an armv7 machine)

#   Failed test 'regression tests pass'
#   at t/002_pg_upgrade.pl line 160.
#          got: '256'
#     expected: '0'

#   Failed test 'dump before running pg_upgrade'
#   at t/002_pg_upgrade.pl line 208.

---
regress_log_002_pg_upgrade
     errors                       ... ok        12770 ms
     infinite_recurse             ... FAILED (test process exited with exit code 2)    31232 ms
test sanity_check                 ... FAILED (test process exited with exit code 2)      370 ms

---
002_pg_upgrade_old_node.log
2024-06-26 02:49:06.742 PDT [29121:4] LOG:  server process (PID 30908) was terminated by signal 9: Killed
2024-06-26 02:49:06.742 PDT [29121:5] DETAIL:  Failed process was running: select infinite_recurse();

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mereswine&dt=2024-07-03%2002%3A10%3A35 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mereswine&dt=2024-08-23%2002%3A10%3A26 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mereswine&dt=2024-11-29%2003%3A10%3A27 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mereswine&dt=2025-01-01%2003%3A10%3A48 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mereswine&dt=2025-01-10%2003%3A10%3A41 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mereswine&dt=2025-01-17%2003%3A10%3A31 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mereswine&dt=2025-01-17%2006%3A12%3A16 - master

infinite_recurse hitting OOM condititon on mereswine

mereswine doesn't run tests anymore (since 2025-02-05)

without_overlaps.sql fails due to expected error missing (after 1772d554b)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2025-01-22%2001%3A29%3A35 - master

--- /Users/buildfarm/bf-data/HEAD/pgsql.build/src/test/regress/expected/without_overlaps.out	2025-01-21 20:29:36
+++ /Users/buildfarm/bf-data/HEAD/pgsql.build/src/test/regress/results/without_overlaps.out	2025-01-21 20:43:08
@@ -1792,8 +1792,6 @@
   SET valid_at = CASE WHEN lower(valid_at) = '2018-01-01' THEN daterange('2018-01-01', '2018-01-05')
                       WHEN lower(valid_at) = '2018-02-01' THEN daterange('2018-01-05', '2018-03-01') END
   WHERE id = '[6,7)';
-ERROR:  update or delete on table "temporal_rng" violates RESTRICT setting of foreign key constraint "temporal_fk_rng2rng_fk" on table "temporal_fk_rng2rng"

SQL:2011 application time \ that commit seems to be causing occasional buildfarm failures

Cache NO ACTION foreign keys separately from RESTRICT foreign keys

XversionUpgrade from pre-v13 fails with fmtId-related Assertion (after 3e98c8ce5)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-02-10%2016%3A26%3A40 - REL_13_STABLE

upgrade.drongo/REL_13_STABLE/REL9_5_STABLE-upgrade.log
Checking for hash indexes                                   Assertion failed: fmtIdEncoding != -1, file C:\\prog\\bf\\root\\REL_13_STABLE\\pgsql.build\\src\\fe_utils\\string_utils.c, line 89

(no link to the public discussion)

Adapt appendPsqlMetaConnect() to the new fmtId() encoding expectations.

FileTextArrayFDW-build fails due to lack of argument for vacuum_delay_point (after e5b0b0ce1)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-02-11%2022%3A42%3A02 - master

file_textarray_fdw.c: In function \342\200\230file_acquire_sample_rows\342\200\231:
file_textarray_fdw.c:945:17: error: too few arguments to function \342\200\230vacuum_delay_point\342\200\231
  945 |                 vacuum_delay_point();
      |                 ^~~~~~~~~~~~~~~~~~
In file included from file_textarray_fdw.c:31:
/home/andrew/bf/root/HEAD/inst/include/postgresql/server/commands/vacuum.h:362:13: note: declared here
  362 | extern void vacuum_delay_point(bool is_analyze);
      |             ^~~~~~~~~~~~~~~~~~
make: *** [/home/andrew/bf/root/HEAD/inst/lib/postgresql/pgxs/src/makefiles/../../src/Makefile.global:956: file_textarray_fdw.o] Error 1

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-02-12%2009%3A28%3A57 - master

(no link to the public discussion)

adjust to upstream API change

Miscellaneous tests fail on RHEL8/RHEL9 animals with FIPS mode enabled

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=cixiid&dt=2025-02-13%2008%3A30%3A04 - REL_13_STABLE

--- /home/ec2-user/18-cixiid/buildroot/REL_13_STABLE/pgsql.build/contrib/pgcrypto/expected/md5.out	2025-02-13 08:30:06.859916289 +0000
+++ /home/ec2-user/18-cixiid/buildroot/REL_13_STABLE/pgsql.build/contrib/pgcrypto/results/md5.out	2025-02-13 08:44:07.024087495 +0000
@@ -2,44 +2,16 @@
 -- MD5 message digest
 --
 SELECT encode(digest('', 'md5'), 'hex');
-              encode              
-----------------------------------
- d41d8cd98f00b204e9800998ecf8427e
-(1 row)
-
+ERROR:  Cannot use "md5": Some PX error (not specified)
 SELECT encode(digest('a', 'md5'), 'hex');

New buildfarm animals with FIPS mode enabled

New buildfarm animals with FIPS mode enabled \ these animals stopped

initdb fails on Valgrind-enabled animal (after 925682260)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-02-14%2018%3A00%3A12 - master

performing post-bootstrap initialization ... ==1526248== VALGRINDERROR-BEGIN
==1526248== Invalid write of size 1
==1526248==    at 0x24A780: heap_vac_scan_next_block (vacuumlazy.c:1621)
==1526248==    by 0x54D59A: read_stream_get_block (read_stream.c:196)
==1526248==    by 0x54DCA7: read_stream_look_ahead (read_stream.c:333)
==1526248==    by 0x54E10E: read_stream_next_buffer (read_stream.c:782)
==1526248==    by 0x24C64D: lazy_scan_heap (vacuumlazy.c:1278)
==1526248==    by 0x24D29C: heap_vacuum_rel (vacuumlazy.c:837)
==1526248==    by 0x39BEC8: table_relation_vacuum (tableam.h:1716)
==1526248==    by 0x39BEC8: vacuum_rel (vacuum.c:2257)
==1526248==    by 0x39D19F: vacuum (vacuum.c:636)
==1526248==    by 0x39DD36: ExecVacuum (vacuum.c:466)
==1526248==    by 0x599010: standard_ProcessUtility (utility.c:862)
==1526248==    by 0x5994C4: ProcessUtility (utility.c:523)
==1526248==    by 0x5968DA: PortalRunUtility (pquery.c:1152)
...

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-02-14%2018%3A59%3A10 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-02-14%2020%3A30%3A29 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-02-14%2020%3A55%3A29 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-02-14%2023%3A52%3A23 - master

Confine vacuum skip logic to lazy_scan_skip \ new wipe_mem() call marked memory "noaccess"

Fix explicit valgrind interaction in read_stream.c.

Testing timed out on check stage (after 6a2275b89)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hachi&dt=2025-02-17%2003%3A05%3A03 - master

ok 73        + index_including_gist                      353 ms
# parallel group (16 tests):  create_cast errors create_aggregate drop_if_exists infinite_recurse

===================================================
timed out after 43200 secs

Also 001_pgbench_with_server.pl failed on due to SIGABRT (after 6a2275b89)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=batta&dt=2025-02-17%2008%3A05%3A03 - master

#   Failed test 'concurrent OID generation stderr /(?^:^$)/'
#   at t/001_pgbench_with_server.pl line 60.
#                   'pgbench: error: client 1 script 0 aborted in command 1 query 0: PANIC:  could not find WAL buffer for 0/18DE0A8
# server closed the connection unexpectedly

2025-02-17 08:11:19.870 UTC [2991217:6] 001_pgbench_with_server.pl PANIC:  could not find WAL buffer for 0/18DE0A8
2025-02-17 08:11:19.870 UTC [2991217:7] 001_pgbench_with_server.pl STATEMENT:  DROP TYPE pg_temp.e;
2025-02-17 08:11:19.872 UTC [2991205:4] LOG:  client backend (PID 2991217) was terminated by signal 6: Aborted
2025-02-17 08:11:19.872 UTC [2991205:5] DETAIL:  Failed process was running: DROP TYPE pg_temp.e;

Also 002_pg_upgrade.pl failed with multiple errors (after 6a2275b89)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gokiburi&dt=2025-02-17%2018%3A05%3A15 - master

# parallel group (20 tests):  security_label init_privs drop_operator lock password tablesample gin spgist collate privileges gist brin replica_identity groupingsets join_hash generated_stored rowsecurity object_address matview identity
not ok 111   + brin                                 24059574 ms
# (test process exited with exit code 2)
not ok 112   + gin                                  24059573 ms
# (test process exited with exit code 2)
not ok 113   + gist                                 24059573 ms
# (test process exited with exit code 2)
not ok 114   + spgist                               24059573 ms
# (test process exited with exit code 2)
not ok 115   + privileges                           24059573 ms
# (test process exited with exit code 2)
ok 116       + init_privs                                 40 ms
ok 117       + security_label                             30 ms
not ok 118   + collate                              24059572 ms
# (test process exited with exit code 2)
not ok 119   + matview                              24059573 ms
# (test process exited with exit code 2)
ok 120       + lock                                       92 ms
not ok 121   + replica_identity                     24059572 ms
# (test process exited with exit code 2)
not ok 122   + rowsecurity                          24059572 ms
# (test process exited with exit code 2)
not ok 123   + object_address                       24059572 ms
# (test process exited with exit code 2)
ok 124       + tablesample                               175 ms
not ok 125   + groupingsets                         24059571 ms
# (test process exited with exit code 2)
ok 126       + drop_operator                              64 ms
ok 127       + password                                  120 ms
not ok 128   + identity                             24059573 ms
# (test process exited with exit code 2)
not ok 129   + generated_stored                     24059571 ms
# (test process exited with exit code 2)
not ok 130   + join_hash                            24059571 ms
# (test process exited with exit code 2)
# parallel group (2 tests):  brin_multi brin_bloom
not ok 131   + brin_bloom                                  6 ms
# (test process exited with exit code 2)
not ok 132   + brin_multi

Get rid of WALBufMappingLock \ BF failure spotted

Revert: Get rid of WALBufMappingLock

explain.sql fails due to change of actual row count format in explain (after ddb17e387)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=conchuela&dt=2025-02-21+21%3A22%3A30 - master

#   Failed test 'regression tests pass'
#   at t/002_pg_upgrade.pl line 263.
#          got: '256'
#     expected: '0'
# Looks like you failed 1 test of 18.
[01:10:31] t/002_pg_upgrade.pl ....... 

...

--- /home/admin/gokiburi/buildroot/HEAD/pgsql.build/src/test/regress/expected/explain.out	2025-02-22 00:59:34.965073667 +0000
+++ /home/admin/gokiburi/buildroot/HEAD/pgsql.build/src/bin/pg_upgrade/tmp_check/results/explain.out	2025-02-22 01:08:21.412701200 +0000
@@ -528,7 +528,7 @@
                              "Plan Rows": 0,                +
                              "Plan Width": 0,               +
                              "Total Cost": 0.0,             +
-                             "Actual Rows": 0.0,            +
+                             "Actual Rows": 0,              +
                              "Actual Loops": 0,             +
                              "Startup Cost": 0.0,           +
                              "Async Capable": false,        +
@@ -575,7 +575,7 @@
                      "Plan Rows": 0,                        +
                      "Plan Width": 0,                       +
                      "Total Cost": 0.0,                     +
-                     "Actual Rows": 0.0,                    +
+                     "Actual Rows": 0,                      +
                      "Actual Loops": 0,                     +
                      "Startup Cost": 0.0,                   +
                      "Async Capable": false,                +
=== EOF ===

explain analyze rows... \ integer output instead of a fractional

Adjust EXPLAIN test case to filter out "Actual Rows" values.

cached-plan-inval.spec fails under -DCLOBBER_CACHE_ALWAYS (after 525392d57)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=trilobite&dt=2025-02-20%2019%3A37%3A12 - master


not ok 3     - cached-plan-inval                      536538 ms

generic plans and "initial" pruning \ test fails under -DCLOBBER_CACHE_ALWAYS

Remove unstable test suite added by 525392d57

XversionUpgrade fails for versions < 10 due to incorrect version evaluation (after 1fd1bd871)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-02-20%2009%3A32%3A03 - master

--- /home/andrew/bf/root/upgrade.crake/HEAD/origin-REL9_2_STABLE.sql.fixed	2025-02-20 04:43:40.461092087 -0500
+++ /home/andrew/bf/root/upgrade.crake/HEAD/converted-REL9_2_STABLE-to-HEAD.sql.fixed	2025-02-20 04:43:40.463092092 -0500
@@ -184,21 +184,87 @@
 --
 SELECT * FROM pg_catalog.pg_restore_relation_stats(
 	'relation', '"MySchema"."Foo"'::regclass,
-	'version', '90224'::integer,
-	'relpages', '0'::integer,
-	'reltuples', '0'::real,
+	'version', '000000'::integer,
+	'relpages', '1'::integer,
+	'reltuples', '1'::real,
 	'relallvisible', '0'::integer
 );
...

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-02-20%2016%3A07%3A03 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-02-20%2016%3A47%3A02 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-02-20%2016%3A47%3A02 - master

Statistics Import and Export \ conversion regexes are wrong for versions < 10

Trial fix for old cross-version upgrades.

XversionUpgrade fails for version 9.2 (12) due to statistics changed (after 1fd1bd871)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-02-20%2018%3A37%3A03 - master

--- /home/andrew/bf/root/upgrade.crake/HEAD/origin-REL9_2_STABLE.sql.fixed	2025-02-20 13:51:31.870393245 -0500
+++ /home/andrew/bf/root/upgrade.crake/HEAD/converted-REL9_2_STABLE-to-HEAD.sql.fixed	2025-02-20 13:51:31.872393250 -0500
@@ -185,20 +185,86 @@
 SELECT * FROM pg_catalog.pg_restore_relation_stats(
 	'relation', '"MySchema"."Foo"'::regclass,
 	'version', '000000'::integer,
-	'relpages', '0'::integer,
-	'reltuples', '0'::real,
+	'relpages', '1'::integer,
+	'reltuples', '1'::real,
 	'relallvisible', '0'::integer
 );
+SELECT * FROM pg_catalog.pg_restore_attribute_stats(
+	'relation', '"MySchema"."Foo"'::regclass,
+	'attname', 'f1'::name,
+	'inherited', 'f'::boolean,
+	'version', '000000'::integer,
+	'null_frac', '0'::float4,
+	'avg_width', '4'::integer,
+	'n_distinct', '-1'::float4
+);

pgsql: Trial fix for old cross-version upgrades \ the order of testing reversed, other changes

Improve robustness of Cross Version Upgrade tests

XversionUpgrade fails for versions [12 .. 16] due to XMLSERIALIZE-related diff (after 984410b92)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-02-21%2008%3A55%3A11 - REL_17_STABLE

--- /home/andrew/bf/root/upgrade.crake/REL_17_STABLE/origin-REL_12_STABLE.sql.fixed	2025-02-21 04:17:35.596334340 -0500
+++ /home/andrew/bf/root/upgrade.crake/REL_17_STABLE/converted-REL_12_STABLE-to-REL_17_STABLE.sql.fixed	2025-02-21 04:17:35.601334352 -0500
@@ -179894,13 +179894,13 @@
 -- Name: xmlview8; Type: VIEW; Schema: public; Owner: buildfarm
 --
 CREATE VIEW public.xmlview8 AS
- SELECT (XMLSERIALIZE(CONTENT 'good'::xml AS character(10)))::character(10) AS "xmlserialize";
+ SELECT (XMLSERIALIZE(CONTENT 'good'::xml AS character(10) NO INDENT))::character(10) AS "xmlserialize";
 ALTER VIEW public.xmlview8 OWNER TO buildfarm;
 --
 -- Name: xmlview9; Type: VIEW; Schema: public; Owner: buildfarm
 --
 CREATE VIEW public.xmlview9 AS
- SELECT XMLSERIALIZE(CONTENT 'good'::xml AS text) AS "xmlserialize";
+ SELECT XMLSERIALIZE(CONTENT 'good'::xml AS text NO INDENT) AS "xmlserialize";
 ALTER VIEW public.xmlview9 OWNER TO buildfarm;
 --
 -- Name: xy_1; Type: TABLE; Schema: public; Owner: buildfarm

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-02-21%2008%3A37%3A02 - REL_16_STABLE

Missing NO INDENT flag in XMLSerialize backward parsing \ The fix has broken cross version upgrade test

Fix cross-version upgrades with XMLSERIALIZE(NO INDENT)

XversionUpgrade fails for pre-v10 versions due to relallvisible change (after 1fd1bd871)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-02-22%2022%3A27%3A03 - master

--- /home/andrew/bf/root/upgrade.crake/HEAD/origin-REL9_6_STABLE.sql.fixed	2025-02-23 09:08:12.744960470 -0500
+++ /home/andrew/bf/root/upgrade.crake/HEAD/converted-REL9_6_STABLE-to-HEAD.sql.fixed	2025-02-23 09:08:12.747960477 -0500
@@ -267992,7 +267992,7 @@
 	'version', '000000'::integer,
 	'relpages', '55'::integer,
 	'reltuples', '10000'::real,
-	'relallvisible', '55'::integer
+	'relallvisible', '53'::integer
 );

pgsql: Trial fix for old cross-version upgrades \ hash indexes reindexed for old versions before making comparison dump

Ignore hash's relallvisible when checking pg_upgrade from pre-v10

XversionUpgrade fails due to inconsistent naming of index expression columns (after 1fd1bd871)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2025-02-20%2017%3A01%3A23 - master

upgrade.copperhead/HEAD/inst/REL_12_STABLE-20250220T191910.066/log/pg_upgrade_internal.log
Restoring database schemas in the new cluster                 
*failure*
Consult the last few lines of "/home/pgbf/buildroot/upgrade.copperhead/HEAD/inst/REL_12_STABLE-upgrade/pg_upgrade_output.d/20250220T191910.066/log/pg_upgrade_dump_56594.log" for
the probable cause of the failure.

---
upgrade.copperhead/HEAD/inst/REL_12_STABLE-20250220T191910.066/log/pg_upgrade_dump_56594.log
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 4163; 0 0 STATISTICS DATA "vcharidx" (no owner)
pg_restore: error: could not execute query: ERROR:  column "text" of relation "vcharidx" does not exist
Command was: SELECT * FROM pg_catalog.pg_restore_relation_stats(
	'relation', '"public"."vcharidx"'::regclass,
	'version', '120022'::integer,
	'relpages', '8'::integer,
	'reltuples', '1000'::real,
	'relallvisible', '0'::integer
);

pgsql: Trial fix for old cross-version upgrades \ inconsistent heuristics for assigning names to index expression columns

Use attnum to identify index columns in pg_restore_attribute_stats()

plpython tests fail on animals with python 3.6 and 3.7 (after c47e8df81)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=longfin&dt=2025-02-26%2015%3A32%3A02 - master

ok 6         - plpython_import                            98 ms
not ok 7     - plpython_spi                             4891 ms
# (test process exited with exit code 2)
not ok 8     - plpython_newline                           30 ms
# (test process exited with exit code 2)
not ok 9     - plpython_void
...

2025-02-26 10:56:41.547 EST [73365:14] LOG:  client backend (PID 73634) was terminated by signal 11: Segmentation fault: 11
2025-02-26 10:56:41.547 EST [73365:15] DETAIL:  Failed process was running: SELECT subtransaction_nested_test('t');

pgsql: Prepare for Python "Limited API" in PL/Python \ Buildfarm's not happy with this

Revert "Prepare for Python "Limited API" in PL/Python"

Miscellaneous tests fail on fairywren due to pg_dump broken (after 8f427187d)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2025-02-26%2010%3A03%3A07 - master

Summary of Failures:

  2/260 postgresql:pg_upgrade / pg_upgrade/005_char_signedness                          ERROR            13.13s   exit status 2
  3/260 postgresql:pg_upgrade / pg_upgrade/003_logical_slots                            ERROR            40.62s   exit status 25
  4/260 postgresql:pg_upgrade / pg_upgrade/004_subscription                             ERROR            62.36s   exit status 25
 33/260 postgresql:pg_upgrade / pg_upgrade/002_pg_upgrade                               ERROR           186.65s   exit status 6
101/260 postgresql:pg_combinebackup / pg_combinebackup/002_compare_backups              ERROR            39.77s   exit status 2
115/260 postgresql:pg_dump / pg_dump/003_pg_dump_with_server                            ERROR             8.38s   exit status 2
118/260 postgresql:pg_dump / pg_dump/004_pg_dump_parallel                               ERROR             8.08s   exit status 4
119/260 postgresql:pg_dump / pg_dump/002_pg_dump                                        ERROR            20.60s   exit status 2
121/260 postgresql:pg_dump / pg_dump/005_pg_dump_filterfile                             ERROR            13.69s   exit status 2
123/260 postgresql:pg_dump / pg_dump/010_dump_connstr                                   ERROR            25.03s   exit status 4
251/260 postgresql:test_pg_dump / test_pg_dump/001_base                                 ERROR            12.95s   exit status 2

---
regress_log_002_compare_backups
# Running: pg_dumpall --no-sync --no-unlogged-table-data --file C:\\tools\\xmsys64\\home\\pgrunner\\bf\\root\\HEAD\\pgsql.build/testrun/pg_combinebackup/002_compare_backups/data/t_002_compare_backups_primary_data/backup/pitr1.dump --dbname port=11246 host=C:/tools/xmsys64/tmp/6bFU_57u3W dbname='postgres'
pg_dumpall: error: pg_dump failed on database "template1", exiting
[10:22:51.456](11.963s) not ok 4 - dump from PITR 1
[10:22:51.456](0.000s) #   Failed test 'dump from PITR 1'

Statistics Import and Export \ pg_dump broken due to pg_strtof specifics

Fix pg_strtof() to not crash on NULL endptr

brin_multi.sql and partition_prune.sql fail due to unexpected index searches count (after 5ead85fbc)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=chevrotain&dt=2025-03-05%2014%3A42%3A05 - master

# 2 of 226 tests failed.

--- /home/debian/17-chevrotain/buildroot/HEAD/pgsql.build/src/test/regress/expected/brin_multi.out	2025-03-05 14:42:16.629570573 +0000
+++ /home/debian/17-chevrotain/buildroot/HEAD/pgsql.build/src/test/regress/results/brin_multi.out	2025-03-05 14:50:55.222887453 +0000
@@ -853,7 +853,7 @@
    Recheck Cond: (a = '2023-01-01'::date)
    ->  Bitmap Index Scan on brin_date_test_a_idx (actual rows=0.00 loops=1)
          Index Cond: (a = '2023-01-01'::date)
-         Index Searches: 1
+         Index Searches: 0
 (5 rows)

...

--- /home/debian/17-chevrotain/buildroot/HEAD/pgsql.build/src/test/regress/expected/partition_prune.out	2025-03-05 14:42:16.633570429 +0000
+++ /home/debian/17-chevrotain/buildroot/HEAD/pgsql.build/src/test/regress/results/partition_prune.out	2025-03-05 14:51:32.673538236 +0000
@@ -3015,10 +3015,10 @@
    ->  Append (actual rows=3.00 loops=2)
          ->  Index Scan using tprt1_idx on tprt_1 (actual rows=2.00 loops=2)
                Index Cond: (col1 < tbl1.col1)
-               Index Searches: 2
+               Index Searches: 0
          ->  Index Scan using tprt2_idx on tprt_2 (actual rows=2.00 loops=1)
...

Showing primitive index scan count in EXPLAIN ANALYZE (for skip scan and SAOP scans) \ issues with debug_parallel_query

Revert "Show index search count in EXPLAIN ANALYZE.

module-ldap_password_funcCheck fails on sifaka after buildfarm client upgrade to REL_19

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sifaka&dt=2025-03-04%2017%3A35%3A40 - master

/Library/Developer/CommandLineTools/usr/bin/make -j1  checkprep >>'/Users/buildfarm/bf-data/HEAD/pgsql.build'/tmp_install/log/install.log 2>&1
make: *** [temp-install] Error 2
log files for step module-ldap_password_funcCheck:

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sifaka&dt=2025-03-04%2018%3A07%3A12 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sifaka&dt=2025-03-04%2018%3A42%3A10 = master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sifaka&dt=2025-03-04%2020%3A02%3A38 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sifaka&dt=2025-03-04%2019%3A53%3A35 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sifaka&dt=2025-03-04%2019%3A44%3A24 - REL_16_STABLE

scalability bottlenecks with (many) partitions (and more) \ logic bug in BF client REL_19

fix logic bug in commit 39b3f8f

stats.sql fails due to unstable ordering (after 8b532771a)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=jay&dt=2025-03-08%2003%3A48%3A58 - master

not ok 220   + stats                                     953 ms
...

--- /home/buildfarm/jay/buildroot/HEAD/pgsql.build/src/test/regress/expected/stats.out	2025-03-08 04:48:51.301450655 +0100
+++ /home/buildfarm/jay/buildroot/HEAD/pgsql.build/src/test/regress/results/stats.out	2025-03-08 05:10:44.609351104 +0100
@@ -39,10 +39,6 @@
 background writer|relation|normal
 background writer|wal|init
 background writer|wal|normal
-checkpointer|relation|init
-checkpointer|relation|normal
-checkpointer|wal|init
-checkpointer|wal|normal
 client backend|relation|bulkread
 client backend|relation|bulkwrite
 client backend|relation|init
@@ -51,6 +47,10 @@
 client backend|temp relation|normal
 client backend|wal|init
 client backend|wal|normal
+checkpointer|relation|init
+checkpointer|relation|normal
+checkpointer|wal|init
+checkpointer|wal|normal
 slotsync worker|relation|bulkread
 slotsync worker|relation|bulkwrite
 slotsync worker|relation|init

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hippopotamus&dt=2025-03-08%2003%3A26%3A16 - master

pgsql: Use stricter ordering in regression test query for pg_stat_io

Use stricter ordering in regression test query for pg_stat_io

002_connection_limits.pl fails on skink due to race condition

(skink is a Valgrind animal)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-03%2022%3A35%3A26 - master

242/321 postgresql:postmaster / postmaster/002_connection_limits                        ERROR              8.78s   exit status 29


regress_log_002_connection_limits
[00:36:47.766](0.000s) ok 4 - reserved_connections limit: matches
process ended prematurely at /home/bf/bf-build/skink-master/HEAD/pgsql/src/test/perl/PostgreSQL/Test/BackgroundPsql.pm line 160.
# Postmaster PID for node "primary" is 1519559
### Stopping node "primary" using mode immediate
# Running: pg_ctl -D /home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/postmaster/002_connection_limits/data/t_002_connection_limits_primary_data/pgdata -m immediate stop
waiting for server to shut down.... done
server stopped
# No postmaster PID for node "primary"
[00:36:48.136](0.370s) # Tests were run but no plan was declared and done_testing() was not seen.
[00:36:48.136](0.000s) # Looks like your test exited with 29 just after 4.

Refactoring postmaster's code to cleanup after child exit \ waiting for message in log

tests: Fix race condition in postmaster/002_connection_limits

003_start_stop.pl fails due to high default timeout

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-06%2009%3A18%3A21 - master

---
regress_log_003_start_stop
### Starting node "main"
# Running: pg_ctl -w -D /home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/postmaster/003_start_stop/data/t_003_start_stop_main_data/pgdata -l /home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/postmaster/003_start_stop/log/003_start_stop_main.log -o --cluster-name=main start
waiting for server to start..... stopped waiting
pg_ctl: could not start server
Examine the log output.
# pg_ctl start failed; see logfile for details: /home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/postmaster/003_start_stop/log/003_start_stop_main.log
# No postmaster PID for node "main"
[10:42:02.734](2.970s) Bail out!  pg_ctl start failed

003_start_stop_main.log
2025-03-06 10:42:02.552 UTC [372451][postmaster][:0] LOG:  1800 s is outside the valid range for parameter "authentication_timeout" (1 s .. 600 s)
2025-03-06 10:42:02.563 UTC [372451][postmaster][:0] FATAL:  configuration file "/home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/postmaster/003_start_stop/data/t_003_start_stop_main_data/pgdata/postgresql.conf" contains errors

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-06%2007%3A10%3A10 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-06%2002%3A32%3A43 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-05%2022%3A20%3A37 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-05%2022%3A20%3A37 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=parula&dt=2025-03-09%2016%3A36%3A59 - master

Refactoring postmaster's code to cleanup after child exit \ increasing PG_TEST_TIMEOUT_DEFAULT vs authentication_timeout

tests: Don't fail due to high default timeout in postmaster/003_start_stop

XversionUpgrade fails due to index stats not updated (after d611f8b15)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-03-07%2018%3A19%3A14 - master

upgrade.crake/HEAD/dumpdiff-REL9_6_STABLE
--- /home/andrew/bf/root/upgrade.crake/HEAD/origin-REL9_6_STABLE.sql.fixed	2025-03-07 13:49:27.618732822 -0500
+++ /home/andrew/bf/root/upgrade.crake/HEAD/converted-REL9_6_STABLE-to-HEAD.sql.fixed	2025-03-07 13:49:27.621732829 -0500
@@ -270836,8 +270836,8 @@
 --
 SELECT * FROM pg_catalog.pg_restore_relation_stats(	'version', '000000'::integer,
 	'relation', 'public.hash_f8_index'::regclass,
-	'relpages', '66'::integer,
-	'reltuples', '10000'::real,
+	'relpages', '0'::integer,
+	'reltuples', '-1'::real,
 	'relallvisible', '0'::integer
 );
...

Statistics Import and Export: difference in statistics dumped \ tests in the wrong order

CREATE INDEX: do update index stats if autovacuum=off.

logical_inspect.spec fails on slow animals due to additional row appeared

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-04%2017%3A35%3A01 - master

 78/324 postgresql:pg_logicalinspect / pg_logicalinspect/isolation                      ERROR             25.43s   exit status 1

--- /home/bf/bf-build/skink-master/HEAD/pgsql/contrib/pg_logicalinspect/expected/logical_inspect.out	2024-10-15 01:07:04.632684683 +0000
+++ /home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/pg_logicalinspect/isolation/results/logical_inspect.out	2025-03-04 18:49:34.659306138 +0000
@@ -42,11 +42,12 @@
 ----------+---------------+----------------------+---------------+----------------------
 consistent|              0|                      |              2|                     2
 consistent|              2|                     2|              0|                      
-(2 rows)
+consistent|              2|                     2|              0|                      
+(3 rows)
 
 step s1_get_logical_snapshot_meta: SELECT COUNT(meta.*) from pg_ls_logicalsnapdir(), pg_get_logical_snapshot_meta(name) as meta;
 count
 -----
-    2
+    3
 (1 row)

Add contrib/pg_logicalsnapinspect \ bgwriter wrote another RUNNING_XACTS during test

pg_logicalinspect: Stabilize isolation tests.

Miscellaneous tests fail on longfin and sifaka with outfuncs/readfuncs warning after 317aba70e)

(longfin and sifaka test -DWRITE_READ_PARSE_PLAN_TREES)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sifaka&dt=2025-03-12%2016%3A58%3A51 - REL_14_STABLE

 68 of 212 tests failed. 
...
--- /Users/buildfarm/bf-data/REL_14_STABLE/pgsql.build/src/test/regress/expected/tablespace.out	2025-03-12 12:59:22
+++ /Users/buildfarm/bf-data/REL_14_STABLE/pgsql.build/src/test/regress/results/tablespace.out	2025-03-12 12:59:23
@@ -242,6 +242,7 @@
 
 -- check \\d output
 \\d testschema.foo
+WARNING:  outfuncs/readfuncs failed to produce equal parse tree
               Table "testschema.foo"
  Column |  Type   | Collation | Nullable | Default 
 --------+---------+-----------+----------+---------
@@ -320,6 +321,7 @@
 (3 rows)
...

Attribute of type record has wrong type error with MERGE ...\ breakage for 13-15

Repair commits 317aba70e et al for -DWRITE_READ_PARSE_PLAN_TREES

Regression tests in v13, v14 fail to start under Valgrind with newer glibc

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-04%2022%3A31%3A25 - REL_14_STABLE

============== creating database "regression"         ==============
psql: error: connection to server on socket "/home/bf/bf-build/skink/tmp/pg_regress-2Wdmyw/.s.PGSQL.6850" failed: server closed the connection unexpectedly
	This probably means the server terminated abnormally
...

---
pgsql.build/src/test/regress/log/postmaster.log
==3534881== VALGRINDERROR-BEGIN
==3534881== Syscall param socketcall.sendto(msg) points to uninitialised byte(s)
==3534881==    at 0x4D975C7: __internal_syscall_cancel (cancellation.c:64)
==3534881==    by 0x4D975EC: __syscall_cancel (cancellation.c:75)
==3534881==    by 0x4E1A1F6: send (send.c:28)
==3534881==    by 0x4F32DC: pgstat_send (pgstat.c:2970)
==3534881==    by 0x4F33C5: pgstat_send_inquiry (pgstat.c:1889)
==3534881==    by 0x4F5508: backend_read_statsfile (pgstat.c:4650)
==3534881==    by 0x4F7812: pgstat_fetch_stat_dbentry (pgstat.c:2710)
==3534881==    by 0x4EB3AB: rebuild_database_list (autovacuum.c:1055)
==3534881==    by 0x4EBF2F: AutoVacLauncherMain (autovacuum.c:635)
==3534881==    by 0x4EC2B1: StartAutoVacLauncher (autovacuum.c:422)
==3534881==    by 0x4FC815: reaper (postmaster.c:3067)
==3534881==    by 0x4D47DAF: ??? (in /usr/lib/x86_64-linux-gnu/libc.so.6)
==3534881==  Address 0x1ffeffedac is on thread 1's stack
==3534881==  in frame #4, created by pgstat_send_inquiry (pgstat.c:1882)
==3534881==  Uninitialised value was created by a stack allocation
==3534881==    at 0x4F3386: pgstat_send_inquiry (pgstat.c:1882)
==3534881== 
==3534881== VALGRINDERROR-END
{
   <insert_a_suppression_name_here>
   Memcheck:Param
   socketcall.sendto(msg)
   fun:__internal_syscall_cancel
   fun:__syscall_cancel
   fun:send
   fun:pgstat_send
   fun:pgstat_send_inquiry
   fun:backend_read_statsfile
   fun:pgstat_fetch_stat_dbentry
   fun:rebuild_database_list
   fun:AutoVacLauncherMain
   fun:StartAutoVacLauncher
   fun:reaper
   obj:/usr/lib/x86_64-linux-gnu/libc.so.6
}

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-03%2019%3A03%3A00 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-01%2019%3A48%3A34 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-03%2018%3A56%3A55 - REL_13_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-04%2022%3A28%3A47 - REL_13_STABLE

Valgrind suppressions in back branches not working

valgrind: Adjust suppressions to handle glibc changes

001_extension_control_path.pl fails when amcheck is not available (after 4f7f7b037)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=snakefly&dt=2025-03-19%2006%3A10%3A04 - master

# +++ tap check in src/test/modules/test_extensions +++

#   Failed test '$system extension is installed correctly on pg_available_extensions'
#   at t/001_extension_control_path.pl line 69.
#          got: 'f'
#     expected: 't'

#   Failed test '$system extension is installed correctly on pg_available_extensions with empty extension_control_path'
#   at t/001_extension_control_path.pl line 76.
#          got: 'f'
#     expected: 't'
# Looks like you failed 2 tests of 5.
[06:43:53] t/001_extension_control_path.pl .. 
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/5 subtests

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=snakefly&dt=2025-03-19%2009%3A46%3A05 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=snakefly&dt=2025-03-19%2013%3A59%3A05 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=snakefly&dt=2025-03-20%2009%3A46%3A05 - master

RFC: Additional Directory for Extensions \ "amcheck" must be an available extension

Fix extension control path tests

002_compare_backups.pl triggers Assert on skink

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-23%2018%3A46%3A11 - master

pgsql.build/testrun/pg_combinebackup/002_compare_backups/log/regress_log_002_compare_backups
### Enabling WAL restore for node "pitr2"
### Starting node "pitr2"
# Running: pg_ctl --wait --pgdata /home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/pg_combinebackup/002_compare_backups/data/t_002_compare_backups_pitr2_data/pgdata --log /home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/pg_combinebackup/002_compare_backups/log/002_compare_backups_pitr2.log --options --cluster-name=pitr2 start
waiting for server to start.................... done
server started
# Postmaster PID for node "pitr2" is 3413596
ack Broken pipe: write( 13, 'SELECT NOT pg_is_in_recovery();' ) at /usr/share/perl5/IPC/Run/IO.pm line 550.

---
pgsql.build/testrun/pg_combinebackup/002_compare_backups/log/002_compare_backups_pitr2.log
2025-03-23 20:40:55.597 UTC [3414840][checkpointer][:0] LOG:  checkpoint starting: end-of-recovery immediate wait
2025-03-23 20:40:55.660 UTC [3419150][client backend][2/2:0] LOG:  statement: SELECT NOT pg_is_in_recovery();
TRAP: failed Assert("TransactionIdPrecedesOrEquals(TransactionXmin, RecentXmin)"), File: "../pgsql/src/backend/storage/ipc/procarray.c", Line: 2132, PID: 3419150
2025-03-23 20:40:55.737 UTC [3414840][checkpointer][:0] LOG:  checkpoint complete: wrote 0 buffers (0.0%), wrote 3 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.033 s, sync=0.006 s, total=0.133 s; sync files=2, longest=0.002 s, average=0.002 s; distance=16384 kB, estimate=16384 kB; lsn=0/5000060, redo lsn=0/5000060
postgres: pitr2: bf postgres [local] SELECT(ExceptionalCondition+0x5f) [0x6ed520]
postgres: pitr2: bf postgres [local] SELECT(+0x46e33d) [0x57633d]
postgres: pitr2: bf postgres [local] SELECT(GetSnapshotData+0x60) [0x5776bd]
postgres: pitr2: bf postgres [local] SELECT(GetNonHistoricCatalogSnapshot+0x53) [0x731645]
postgres: pitr2: bf postgres [local] SELECT(GetCatalogSnapshot+0x28) [0x73271b]
postgres: pitr2: bf postgres [local] SELECT(systable_beginscan+0xc9) [0x25480a]
postgres: pitr2: bf postgres [local] SELECT(+0x5caa96) [0x6d2a96]
postgres: pitr2: bf postgres [local] SELECT(+0x5cad29) [0x6d2d29]
postgres: pitr2: bf postgres [local] SELECT(SearchCatCache+0x18) [0x6d335c]
postgres: pitr2: bf postgres [local] SELECT(SearchSysCache+0x21) [0x6e7dee]
postgres: pitr2: bf postgres [local] SELECT(GetSysCacheOid+0x23) [0x6e8159]
postgres: pitr2: bf postgres [local] SELECT(get_namespace_oid+0x2f) [0x2ddea0]
...

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-04%2017%3A35%3A01 - master

Fix rare assertion failure in standby, if primary is restarted

bitmapops.sql is unstable on slow animals due to autovacuum (after 2b73a8cd3)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-16%2010%3A34%3A17 - master


not ok 171   + bitmapops                              130848 ms

diff -U3 /home/bf/bf-build/skink-master/HEAD/pgsql/src/test/regress/expected/bitmapops.out /home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/recovery/027_stream_regress/data/results/bitmapops.out
--- /home/bf/bf-build/skink-master/HEAD/pgsql/src/test/regress/expected/bitmapops.out	2023-01-04 04:21:33.563501850 +0000
+++ /home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/recovery/027_stream_regress/data/results/bitmapops.out	2025-03-16 12:03:10.495594281 +0000
@@ -31,7 +31,7 @@
 SELECT count(*) FROM bmscantest WHERE a = 1 OR b = 1;
  count 
 -------
-  2485
+  1601
 (1 row)
 
 -- clean up

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=flaviventris&dt=2025-03-17%2020%3A07%3A43 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-17%2001%3A16%3A02 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=kestrel&dt=2025-03-24%2007%3A18%3A54 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-24%2013%3A45%3A02 - master

BitmapHeapScan streaming read user and prelim refactoring \ recheck is performed for pending empty tuples

Fix bitmapheapscan incorrect recheck of NULL tuples

postgres_fdw/t/001_auth_scram.pl fails on Windows in absence of Unix-domain sockets (after 76563f88c)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-03-24%2020%3A34%3A09 - master

238/314 postgresql:postgres_fdw / postgres_fdw/001_auth_scram                           ERROR            71.37s   exit status 4
------------------------------------- 8< -------------------------------------
stderr:
#   Failed test 'loopback trust fails on the same cluster'
#   at C:/prog/bf/root/HEAD/pgsql/contrib/postgres_fdw/t/001_auth_scram.pl line 95.
#          got: '2'
#     expected: '3'
#   Failed test 'expected error from loopback trust (same cluster)'
#   at C:/prog/bf/root/HEAD/pgsql/contrib/postgres_fdw/t/001_auth_scram.pl line 96.
#                   'psql: error: connection to server at "127.0.0.1", port 31059 failed: FATAL:  no pg_hba.conf entry for host "127.0.0.1", user "user01", database "db0", no encryption'
#     doesn't match '(?^:failed: authentication method requirement "scram-sha-256")'
#   Failed test 'loopback password fails on a different cluster'
#   at C:/prog/bf/root/HEAD/pgsql/contrib/postgres_fdw/t/001_auth_scram.pl line 106.
#          got: '2'
#     expected: '3'
#   Failed test 'expected error from loopback password (different cluster)'
#   at C:/prog/bf/root/HEAD/pgsql/contrib/postgres_fdw/t/001_auth_scram.pl line 107.
#                   'psql: error: connection to server at "127.0.0.1", port 31059 failed: FATAL:  no pg_hba.conf entry for host "127.0.0.1", user "user01", database "db0", no encryption'
#     doesn't match '(?^:failed: authentication method requirement "scram-sha-256")'
# Looks like you failed 4 tests of 7.

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-03-25%2002%3A11%3A12 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-03-25%2015%3A07%3A46 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-03-26%2004%3A33%3A53 - master

pgsql: postgres_fdw: improve security checks \ This patch is failing on "drongo"

postgres_fdw: Fix tests on some Windows variants

pg_overexplain fails with debug_parallel_query = regress (after 8d5ceb113)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=alligator&dt=2025-03-26%2018%3A05%3A52 - master

not ok 1     - pg_overexplain                             30 ms

---
pgsql.build/contrib/pg_overexplain/regression.diffs
--- /home/pgbuildfarm/build-farm-19/buildroot/HEAD/pgsql.build/contrib/pg_overexplain/expected/pg_overexplain.out	2025-03-26 13:21:20.718626000 -0500
+++ /home/pgbuildfarm/build-farm-19/buildroot/HEAD/pgsql.build/contrib/pg_overexplain/results/pg_overexplain.out	2025-03-26 13:26:22.123257000 -0500
@@ -387,25 +387,25 @@
  Nested Loop (actual rows=8.00 loops=1)
    Disabled Nodes: 0
    Parallel Safe: true
-   Plan Node ID: 0
+   Plan Node ID: 1
    ->  Append (actual rows=8.00 loops=1)
          Disabled Nodes: 0
          Parallel Safe: true
-         Plan Node ID: 1
+         Plan Node ID: 2
...

pgsql: Fix oversights in commit 8d5ceb113e3f7ddb627bd40b26438a9d2fa0551

Fix oversights in commit 8d5ceb113e3f7ddb627bd40b26438a9d2fa05512

pg_overexplain fails when JIT is enabled (after 8d5ceb113)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bushmaster&dt=2025-03-26%2019%3A15%3A02 - master

not ok 1     - pg_overexplain                             70 ms

---
pgsql.build/contrib/pg_overexplain/regression.diffs
--- /home/bf/bf-build/bushmaster/HEAD/pgsql/contrib/pg_overexplain/expected/pg_overexplain.out	2025-03-26 19:15:03.740031048 +0000
+++ /home/bf/bf-build/bushmaster/HEAD/pgsql.build/contrib/pg_overexplain/results/pg_overexplain.out	2025-03-26 19:40:04.223933483 +0000
@@ -22,12 +22,15 @@
 LINE 1: EXPLAIN (DEBUFF) SELECT 1;
                  ^
 EXPLAIN (DEBUG) SELECT 1;
-                QUERY PLAN                
-------------------------------------------
+                                   QUERY PLAN                                    
+---------------------------------------------------------------------------------
  Result  (cost=0.00..0.01 rows=1 width=4)
    Disabled Nodes: 0
    Parallel Safe: false
    Plan Node ID: 0
+ JIT:
+   Functions: 1
+   Options: Inlining false, Optimization false, Expressions true, Deforming true
  PlannedStmt:
...

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=taipan&dt=2025-03-26%2019%3A08%3A41 - master

pgsql: pg_overexplain: SET jit off when running tests

pg_overexplain: SET jit=off when running tests

pg_overexplain fails on Windows animals due to different rounding result (after 8d5ceb113)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-03-26%2020%3A33%3A20 - master

 83/316 postgresql:pg_overexplain / pg_overexplain/regress                              ERROR            19.29s   exit status 1

---
pgsql.build/testrun/pg_overexplain/regress/regression.diffs
--- C:/prog/bf/root/HEAD/pgsql/contrib/pg_overexplain/expected/pg_overexplain.out	2025-03-26 20:33:47.834896600 +0000
+++ C:/prog/bf/root/HEAD/pgsql.build/testrun/pg_overexplain/regress/results/pg_overexplain.out	2025-03-26 21:57:55.332431300 +0000
@@ -419,7 +419,7 @@
                Plan Node ID: 5
                extParam: 0
                allParam: 0
-         ->  Index Scan using daucus_id_idx on daucus v2_2 (actual rows=0.12 loops=8)
+         ->  Index Scan using daucus_id_idx on daucus v2_2 (actual rows=0.13 loops=8)
                Index Cond: (id = v1.id)
                Index Searches: 8
                Disabled Nodes: 0

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2025-03-27%2011%3A00%3A19 - master

making EXPLAIN extensible \ 1/8 rounded does not produce the same answer

pg_overexplain: Filter out actual row count from test result

check_gin,sql fails on RHEL8/RHEL9 animals with FIPS mode enabled

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gecko&dt=2025-03-29%2020%3A25%3A23 - master

not ok 3     - check_gin                                 783 ms

---
pgsql.build/contrib/amcheck/regression.diffs
--- /home/linux1/17-gecko/buildroot/HEAD/pgsql.build/contrib/amcheck/expected/check_gin.out	2025-03-29 16:23:13.349657448 -0400
+++ /home/linux1/17-gecko/buildroot/HEAD/pgsql.build/contrib/amcheck/results/check_gin.out	2025-03-29 16:43:46.319477202 -0400
@@ -51,8 +51,10 @@
 CREATE TABLE "gin_check_text_array"("Column1" text[]);
 -- posting trees
 INSERT INTO gin_check_text_array select array_agg(md5(round(random()*300)::text)::text) from generate_series(1, 100000) as i group by i % 10000;
+ERROR:  could not com

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=froghopper&dt=2025-03-30%2008%3A24%3A06 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=shikra&dt=2025-03-30%2008%3A30%3A05 - master

Use of md5() makes the test fail on machines with FIPS mode enabled

Remove incidental md5() function use from test

001_aio.pl fails when io_method is set in TEMP_CONFIG

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bumblebee&dt=2025-04-01%2018%3A55%3A01 - master

                  'extra_config' => {
...
                                       'HEAD' => [
...
                                                   'io_method = io_uring'
...
 
# +++ tap check in src/test/modules/test_aio +++

#   Failed test 'worker: io_method set correctly'
#   at t/001_aio.pl line 1467.
#          got: 'io_uring'
#     expected: 'worker'

#   Failed test 'worker: failure to open: detected: expected stdout'
#   at t/001_aio.pl line 859.
#                   '10000'
#     doesn't match '(?^:^$)'

#   Failed test 'worker: failure to open: detected: expected stderr'
#   at t/001_aio.pl line 859.
#                   ''
#     doesn't match '(?^:ERROR:.*could not read blocks 1\\.\\.1 in file "base/.*": No such file or directory)'

#   Failed test 'sync: io_method set correctly'
#   at t/001_aio.pl line 1467.
#          got: 'io_uring'
#     expected: 'sync'
# Looks like you failed 4 tests of 583.
[15:10:44] t/001_aio.pl ......... 
Dubious, test returned 4 (wstat 1024, 0x400)
Failed 4/583 subtests

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bumblebee&dt=2025-04-01%2021%3A00%3A01 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bumblebee&dt=2025-04-02%2000%3A00%3A01 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bumblebee&dt=2025-04-02%2006%3A16%3A01 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bumblebee&dt=2025-04-02%2009%3A46%3A01 - master

AIO v2.5 \ test failure caused by TEMP_CONFIG

tests: Cope with io_method in TEMP_CONFIG in test_aio

001_aio.pl fails on Windows animals due to additional warnings printed

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-04-01%2020%3A15%3A19 - master

295/319 postgresql:test_aio / test_aio/001_aio                                          ERROR            40.63s   exit status 2
...
stderr:
#   Failed test 'worker: create database w/ wal strategy, invalid source: expected stderr'
#   at C:/prog/bf/root/HEAD/pgsql/src/test/modules/test_aio/t/001_aio.pl line 1273.
#                   'psql:<stdin>:18: WARNING:  could not remove directory "base/16514": Directory not empty
# psql:<stdin>:18: WARNING:  some useless files may be left behind in old database directory "base/16514"
# psql:<stdin>:18: ERROR:  invalid page in block 1 of relation base/16489/16510'
#     doesn't match '(?^:^psql:<stdin>:\\d+: ERROR:  invalid page in block 1 of relation base/\\d+/\\d+$)'
#   Failed test 'sync: create database w/ wal strategy, invalid source: expected stderr'
#   at C:/prog/bf/root/HEAD/pgsql/src/test/modules/test_aio/t/001_aio.pl line 1273.
#                   'psql:<stdin>:18: WARNING:  could not remove directory "base/16514": Directory not empty
# psql:<stdin>:18: WARNING:  some useless files may be left behind in old database directory "base/16514"
# psql:<stdin>:18: ERROR:  invalid page in block 1 of relation base/16489/16510'
#     doesn't match '(?^:^psql:<stdin>:\\d+: ERROR:  invalid page in block 1 of relation base/\\d+/\\d+$)'
# Looks like you failed 2 tests of 353.

(test program exited with status code 2)

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2025-04-01%2019%3A03%3A07 - master

AIO v2.5 \ Failure on windows BF machines

tests: Cope with WARNINGs during failed CREATE DB on windows

001_aio.pl fails with *_FORCE_RELEASE defined

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-04-01%2019%3A23%3A07 - master

# +++ tap check in src/test/modules/test_aio +++

#   Failed test 'worker: batch_start() leak & cleanup in implicit xact: expected stderr'
#   at t/001_aio.pl line 318.
#                   'psql:<stdin>:4: ERROR:  starting batch while batch already in progress'
#     doesn't match '(?^:open AIO batch at end)'

#   Failed test 'worker: batch_start() leak & cleanup in explicit xact: expected stderr'
#   at t/001_aio.pl line 328.
#                   'psql:<stdin>:7: ERROR:  starting batch while batch already in progress'
#     doesn't match '(?^:open AIO batch at end)'

#   Failed test 'worker: batch_start(), batch_end() works: expected stderr'
#   at t/001_aio.pl line 350.
#                   'psql:<stdin>:12: ERROR:  starting batch while batch already in progress'
#     doesn't match '(?^:^$)'

#   Failed test 'sync: batch_start() leak & cleanup in implicit xact: expected stderr'
#   at t/001_aio.pl line 318.
#                   'psql:<stdin>:4: ERROR:  starting batch while batch already in progress'
#     doesn't match '(?^:open AIO batch at end)'

#   Failed test 'sync: batch_start() leak & cleanup in explicit xact: expected stderr'
#   at t/001_aio.pl line 328.
#                   'psql:<stdin>:7: ERROR:  starting batch while batch already in progress'
#     doesn't match '(?^:open AIO batch at end)'

#   Failed test 'sync: batch_start(), batch_end() works: expected stderr'
#   at t/001_aio.pl line 350.
#                   'psql:<stdin>:12: ERROR:  starting batch while batch already in progress'
#     doesn't match '(?^:^$)'
# Looks like you failed 6 tests of 353.
[20:37:30] t/001_aio.pl ......... 
Dubious, test returned 6 (wstat 1536, 0x600)
Failed 6/353 subtests 
	(less 3 skipped subtests: 344 okay)
[20:37:34] t/002_io_workers.pl .. ok     4007 ms ( 0.01 usr  0.00 sys +  0.34 cusr  0.23 csys =  0.58 CPU)
[20:37:34]

Test Summary Report
-------------------
t/001_aio.pl       (Wstat: 1536 Tests: 353 Failed: 6)
  Failed tests:  38, 40, 42, 215, 217, 219

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-04-01%2020%3A43%3A08 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-04-01%2021%3A58%3A07 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-04-02%2001%3A07%3A07 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-04-02%2006%3A23%3A06 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-04-02%2009%3A53%3A07 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-04-02%2011%3A33%3A07 - master

AIO v2.5 \ Some subtests fail if RELCACHE_FORCE_RELEASE and CATCACHE_FORCE_RELEASE are defined

tests: Fix incompatibility of test_aio with *_FORCE_RELEASE

pg_dump tests (001_basic.pl and 006_pg_dumpall.pl) fail because of message mismatch

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dikkop&dt=2025-04-04%2020%3A12%3A35 - master

#   Failed test 'When option --exclude-database is used in pg_restore with dump of pg_dump: matches'
#   at t/001_basic.pl line 245.
#                   'pg_restore: error: option --exclude-database can be used only when restoring an archive created by pg_dumpall
# '
#     doesn't match '(?^:pg_restore\\:\\ error\\:\\ option\\ \\-\\-exclude\\-database\\ can\\ be\\ used\\ only\\ when\\ restoring\\ multiple\\ databases\\ by\\ archive\\ of\\ pg_dumpall)'

#   Failed test 'When option --globals-only is not used in pg_restore with dump of pg_dump: matches'
#   at t/001_basic.pl line 250.
#                   'pg_restore: error: option -g/--globals-only can be used only when restoring an archive created by pg_dumpall
# '
#     doesn't match '(?^:pg_restore\\:\\ error\\:\\ option\\ \\-g\\/\\-\\-globals\\-only\\ can\\ be\\ used\\ only\\ when\\ restoring\\ multiple\\ databases\\ by\\ archive\\ of\\ pg_dumpall)'
# Looks like you failed 2 tests of 107.
[22:16:37] t/001_basic.pl ................ 
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/107 subtests 
...
#   Failed test 'When -C is not used in pg_restore with dump of pg_dumpall: matches'
#   at t/006_pg_dumpall.pl line 364.
#                   'pg_restore: error: -C/--create option should be specified when restoring from an archive of created by pg_dumpall
# pg_restore: hint: Try "pg_restore --help" for more information.
# pg_restore: hint: Individual databases can be restored using their specific archives.
# '
#     doesn't match '(?^:pg_restore\\:\\ error\\:\\ \\-C\\/\\-\\-create\\ option\\ should\\ be\\ specified\\ when\\ restoring\\ multiple\\ databases\\ by\\ archive\\ of\\ pg_dumpall)'

#   Failed test 'When --list is used in pg_restore with dump of pg_dumpall: matches'
#   at t/006_pg_dumpall.pl line 372.
#                   'pg_restore: error: option -l/--list cannot be used when restoring an archive created with pg_dumpall
# '
#     doesn't match '(?^:pg_restore\\:\\ error\\:\\ option\\ \\-l\\/\\-\\-list\\ cannot\\ be\\ used\\ when\\ restoring\\ multiple\\ databases\\ by\\ archive\\ of\\ pg_dumpall)'
# Looks like you failed 2 tests of 23.
[22:21:23] t/006_pg_dumpall.pl ...........

pgsql: Add more TAP tests for pg_dumpall \ change of error message not reflected in test

Fix a couple of error messages and tests for them

XversionUpgrade-REL9_3_STABLE-HEAD fails due to WITH ORDINALITY missing in old versions

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-04-04%2020%3A07%3A01 - master

upgrade.crake/HEAD/REL9_3_STABLE-dump1.log

pg_dump: error: query failed: ERROR:  syntax error at or near "WITH ORDINALITY"
LINE 2: ...am FROM pg_catalog.pg_stats s JOIN unnest($1, $2) WITH ORDIN...
                                                             ^
...
pg_dumpall: error: pg_dump failed on database "contrib_regression", exiting

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-04-04%2021%3A37%3A01 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-04-04%2022%3A32%3A01 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-04-05%2001%3A45%3A00 - master

Statistics Import and Export \ test failures due to use of WITH ORDINALITY

pg_dump: Fix query for gathering attribute stats on older versions.

subselect.sql fails due to plan change (after c0962a113)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rhinoceros&dt=2025-04-04%2013%3A52%3A13 - master

================== pgsql.build/src/test/regress/regression.diffs ==================
diff -U3 /opt/src/pgsql-git/build-farm-root/HEAD/pgsql.build/src/test/regress/expected/subselect.out /opt/src/pgsql-git/build-farm-root/HEAD/pgsql.build/src/test/regress/results/subselect.out
--- /opt/src/pgsql-git/build-farm-root/HEAD/pgsql.build/src/test/regress/expected/subselect.out	2025-04-04 06:52:11.514389738 -0700
+++ /opt/src/pgsql-git/build-farm-root/HEAD/pgsql.build/src/test/regress/results/subselect.out	2025-04-04 06:57:47.114824873 -0700
@@ -2769,15 +2769,16 @@
 EXPLAIN (COSTS OFF)
 SELECT c.oid,c.relname FROM pg_class c JOIN pg_am a USING (oid)
 WHERE c.oid IN (VALUES (1), (2));
-                          QUERY PLAN                           
----------------------------------------------------------------
- Hash Join
-   Hash Cond: (a.oid = c.oid)
-   ->  Seq Scan on pg_am a
-   ->  Hash
-         ->  Index Scan using pg_class_oid_index on pg_class c
-               Index Cond: (oid = ANY ('{1,2}'::oid[]))
-(6 rows)
+                       QUERY PLAN                        
+---------------------------------------------------------
+ Merge Join
+   Merge Cond: (c.oid = a.oid)
+   ->  Index Scan using pg_class_oid_index on pg_class c
+         Index Cond: (oid = ANY ('{1,2}'::oid[]))
+   ->  Sort
+         Sort Key: a.oid
+         ->  Seq Scan on pg_am a
+(7 rows)

Replace IN VALUES with ANY in WHERE clauses during optimization \ tests failed on both buildfarm and CI

Stabilize regression test from c0962a113

create_index.sql triggers server crash (after 9ef185168)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=canebrake&dt=2025-04-04%2011%3A30%3A09 - master

not ok 69    + create_index                             5840 ms
# (test process exited with exit code 2)

stack trace: pgsql.build/src/test/regress/tmp_check/data/core
Core was generated by `/home/bf/bf-build/canebrake/HEAD/pgsql.build/tmp_install/home/bf/bf-build/canebrake/HEAD/inst/bin/postgres '' '' '' '' '' '' '''.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000055d30575f935 in get_actual_variable_range (root=root@entry=0x55d306a7b438, vardata=vardata@entry=0x7ffdb2aa26f0, sortop=664, collation=collation@entry=100, min=min@entry=0x0, max=0x55d306a2e4a8) at /home/bf/bf-build/canebrake/HEAD/pgsql.build/../pgsql/src/backend/utils/adt/selfuncs.c:6354
6354			strategy = get_op_opfamily_strategy(sortop, index->sortopfamily[0]);
#0  0x000055d30575f935 in get_actual_variable_range (root=root@entry=0x55d306a7b438, vardata=vardata@entry=0x7ffdb2aa26f0, sortop=664, collation=collation@entry=100, min=min@entry=0x0, max=0x55d306a2e4a8) at /home/bf/bf-build/canebrake/HEAD/pgsql.build/../pgsql/src/backend/utils/adt/selfuncs.c:6354
#1  0x000055d3057647c4 in ineq_histogram_selectivity (root=root@entry=0x55d306a7b438, vardata=vardata@entry=0x7ffdb2aa26f0, opoid=opoid@entry=667, opproc=opproc@entry=0x7ffdb2aa2650, isgt=isgt@entry=true, iseq=iseq@entry=true, collation=100, constval=94364838113304, consttype=25) at /home/bf/bf-build/canebrake/HEAD/pgsql.build/../pgsql/src/backend/utils/adt/selfuncs.c:1130
#2  0x000055d305765282 in scalarineqsel (root=root@entry=0x55d306a7b438, operator=667, isgt=isgt@entry=true, iseq=iseq@entry=true, collation=collation@entry=100, vardata=vardata@entry=0x7ffdb2aa26f0, constval=94364838113304, consttype=25) at /home/bf/bf-build/canebrake/HEAD/pgsql.build/../pgsql/src/backend/utils/adt/selfuncs.c:689
#3  0x000055d3057654c4 in scalarineqsel_wrapper (fcinfo=<optimized out>, isgt=isgt@entry=true, iseq=iseq@entry=true) at /home/bf/bf-build/canebrake/HEAD/pgsql.build/../pgsql/src/backend/utils/adt/selfuncs.c:1460
#4  0x000055d305765599 in scalargesel (fcinfo=<optimized out>) at /home/bf/bf-build/canebrake/HEAD/pgsql.build/../pgsql/src/backend/utils/adt/selfuncs.c:1501
...

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-04-04%2011%3A01%3A56 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-04-04%2011%3A25%3A42 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-04-04%2011%3A38%3A08 - master

Index AM API cleanup \ skink/valgrind started to die

Fix crash/valgrind error

Miscellaneous tests crash on fairywren (after c313fa460)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2025-04-02%2007%3A06%3A04 - master

1/1 postgresql:regress / regress/regress ERROR           147.68s   exit status 1
...
# 65 of 226 tests failed.

---
2025-04-02 08:15:23.686 UTC postmaster[5252] LOG:  client backend (PID 6384) was terminated by exception 0xC0000005
2025-04-02 08:15:23.686 UTC postmaster[5252] DETAIL:  Failed process was running: SELECT * FROM mvtest_tm ORDER BY type;
2025-04-02 08:15:23.686 UTC postmaster[5252] HINT:  See C include file "ntstatus.h" for a description of the hexadecimal value.
2025-04-02 08:15:23.686 UTC postmaster[5252] LOG:  terminating any other active server processes
2025-04-02 08:15:23.749 UTC postmaster[5252] LOG:  all server processes terminated; reinitializing

[PATCH Fix build on MINGW on ARM64 \ fairywren has been failing since that commit]

Revert "Use workaround of __builtin_setjmp only on MINGW on MSVCRT"

002_client.pl fails on skink due to timeout

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-04-03%2000%3A22%3A59 - master

297/333 postgresql:oauth_validator / oauth_validator/002_client                         ERROR             26.41s   exit status 3

---
pgsql.build/testrun/oauth_validator/002_client/log/regress_log_002_client
[10:50:01.014](1.015s) ok 4 - connect_timeout interrupts hung client flow: stderr matches
[10:50:01.022](0.008s) # running 'oauth_hook_client' '--misbehave=no-hook' 'port=31079 host=/tmp/LK5HsBVQo_ user=test oauth_issuer=https://256.256.256.256 oauth_client_id=myID connect_timeout=1'
[10:50:02.108](1.085s) not ok 5 - hook misbehavior: --misbehave=no-hook: stderr matches
[10:50:02.109](0.001s) #   Failed test 'hook misbehavior: --misbehave=no-hook: stderr matches'
#   at /home/bf/bf-build/skink-master/HEAD/pgsql/src/test/modules/oauth_validator/t/002_client.pl line 86.
[10:50:02.109](0.000s) #                   'connection to database failed: connection to server on socket "/tmp/LK5HsBVQo_/.s.PGSQL.31079" failed: timeout expired
# '
#     doesn't match '(?^:user-defined OAuth flow provided neither a token nor an async callback)'
[10:50:02.122](0.013s) # running 'oauth_hook_client' '--misbehave=fail-async' 'port=31079 host=/tmp/LK5HsBVQo_ user=test oauth_issuer=https://256.256.256.256 oauth_client_id=myID connect_timeout=1'
[10:50:03.198](1.076s) not ok 6 - hook misbehavior: --misbehave=fail-async: stderr matches
[10:50:03.199](0.001s) #   Failed test 'hook misbehavior: --misbehave=fail-async: stderr matches'
#   at /home/bf/bf-build/skink-master/HEAD/pgsql/src/test/modules/oauth_validator/t/002_client.pl line 86.
[10:50:03.199](0.000s) #                   'connection to database failed: connection to server on socket "/tmp/LK5HsBVQo_/.s.PGSQL.31079" failed: timeout expired
# '
#     doesn't match '(?^:user-defined OAuth flow failed)'
[10:50:03.200](0.000s) # running 'oauth_hook_client' '--misbehave=no-token' 'port=31079 host=/tmp/LK5HsBVQo_ user=test oauth_issuer=https://256.256.256.256 oauth_client_id=myID connect_timeout=1'
[10:50:04.134](0.935s) ok 7 - hook misbehavior: --misbehave=no-token: stderr matches
[10:50:04.135](0.000s) # running 'oauth_hook_client' '--misbehave=no-socket' 'port=31079 host=/tmp/LK5HsBVQo_ user=test oauth_issuer=https://256.256.256.256 oauth_client_id=myID connect_timeout=1'
[10:50:05.222](1.087s) not ok 8 - hook misbehavior: --misbehave=no-socket: stderr matches
[10:50:05.226](0.004s) #   Failed test 'hook misbehavior: --misbehave=no-socket: stderr matches'
#   at /home/bf/bf-build/skink-master/HEAD/pgsql/src/test/modules/oauth_validator/t/002_client.pl line 86.
[10:50:05.231](0.005s) #                   'connection to database failed: connection to server on socket "/tmp/LK5HsBVQo_/.s.PGSQL.31079" failed: timeout expired
# '
#     doesn't match '(?^:user-defined OAuth flow did not provide a socket for polling)'
[10:50:05.231](0.000s) 1..8
### Stopping node "primary" using mode immediate

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-04-03%2007%3A06%3A19 - master

pgsql: oauth: Remove timeout from t/002_client when not needed

oauth: Remove timeout from t/002_client when not needed

003_check_guc.pl fails due to unexpected enable_self_join_elimination in conf.sample (after c2d329260)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=longfin&dt=2025-04-06%2010%3A28%3A01 - master


#   Failed test 'no parameters missing from guc_tables.c'
#   at t/003_check_guc.pl line 89.
#          got: '1'
#     expected: '0'

#   Failed test 'no parameters marked as NOT_IN_SAMPLE in postgresql.conf.sample'
#   at t/003_check_guc.pl line 92.
#          got: '1'
#     expected: '0'
# Looks like you failed 2 tests of 3.
[06:46:16] t/003_check_guc.pl .............. 
Dubious, test returned 2 (wstat 512, 0x200)

pgsql: Put enable_self_join_elimination into postgresql.conf.sample \ The GUC is marked GUC_NOT_IN_SAMPLE

Revert "Put enable_self_join_elimination into postgresql.conf.sample"

deadlock-parallel.spec fails due to timeout on jit-enabled animals

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=canebrake&dt=2024-04-02%2022%3A20%3A22 - REL_15_STABLE

(canebrake uses --with-llvm, jit=1, jit_above_cost=0 options)

--- /home/bf/bf-build/canebrake/REL_15_STABLE/pgsql/src/test/isolation/expected/deadlock-parallel.out	2023-10-18 23:57:32.904930097 +0000
+++ /home/bf/bf-build/canebrake/REL_15_STABLE/pgsql.build/src/test/isolation/output_iso/results/deadlock-parallel.out	2024-04-03 00:02:29.290675485 +0000
@@ -46,23 +46,15 @@
         1
 (1 row)
 
+isolationtester: canceling step d2a1 after 300 seconds
 step d2a1: <... completed>
-  sum
------
-10000
-(1 row)
-
-lock_share
-----------
-         1
-(1 row)
-
+ERROR:  canceling statement due to user request
 step e1c: COMMIT;
-step d2c: COMMIT;
 step e2l: <... completed>
 lock_excl
 ---------
         1
 (1 row)
 
+step d2c: COMMIT;
 step e2c: COMMIT;

(petalura, pogona, xenodermus and urutu also use --with-llvm, jit=1, jit_above_cost=0 options)

Also, deadlock_parallel.spec fails with CLOBBER_CACHE_ALWAYS (after 0dca5d68d)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=trilobite&dt=2025-04-08%2012%3A53%3A41 - master

--- /home/buildfarm/trilobite/buildroot/HEAD/pgsql.build/src/test/isolation/expected/deadlock-parallel.out	2025-04-08 14:53:43.426017895 +0200
+++ /home/buildfarm/trilobite/buildroot/HEAD/pgsql.build/src/test/isolation/output_iso/results/deadlock-parallel.out	2025-04-08 23:55:23.283202486 +0200
@@ -46,23 +46,15 @@
         1
 (1 row)
 
+isolationtester: canceling step d2a1 after 360 seconds
 step d2a1: <... completed>
-  sum
------
-10000
-(1 row)
-
-lock_share
-----------
-         1
-(1 row)
-
+ERROR:  canceling statement due to user request
 step e1c: COMMIT;
-step d2c: COMMIT;
 step e2l: <... completed>
 lock_excl
 ---------
         1
 (1 row)
 
+step d2c: COMMIT;
 step e2c: COMMIT;

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=avocet&dt=2025-04-05%2019%3A15%3A54 - master

Recent 027_streaming_regress.pl hangs \ deadlock-parallel failures / SQLFunctionCache and generic plans \ two animals have started to fail deadlock-parallel

Fix performance issue in deadlock-parallel isolation test.

install-check-cs_CZ.UTF-8/constraints.sql fails due to locale-dependent ordering (after a379061a2)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=jay&dt=2025-04-07%2017%3A56%3A49 - master

--- /home/buildfarm/jay/buildroot/HEAD/pgsql.build/src/test/regress/expected/constraints.out	2025-04-07 19:57:01.685668669 +0200
+++ /home/buildfarm/jay/buildroot/HEAD/pgsql.build/src/test/regress/results/constraints.out	2025-04-07 20:25:44.639562765 +0200
@@ -1506,8 +1506,8 @@
 EXECUTE get_nnconstraint_info('{notnull_inhparent, notnull_inhchild, notnull_inhgrand}');
       tabname      | conname | convalidated | conislocal | coninhcount 
 -------------------+---------+--------------+------------+-------------
- notnull_inhchild  | nn      | f            | f          |           1
  notnull_inhgrand  | nn      | f            | f          |           2
+ notnull_inhchild  | nn      | f            | f          |           1
  notnull_inhparent | nn      | f            | t          |           0
 (3 rows)
 ...

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=jay&dt=2025-04-07%2018%3A57%3A06 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=jay&dt=2025-04-07%2019%3A50%3A01 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hippopotamus&dt=2025-04-07%2018%3A28%3A12 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hippopotamus&dt=2025-04-07%2019%3A26%3A13 - master

Support NOT VALID / VALIDATE constraint options for named NOT NULL constraints \ some of the test cases have issues with locale-dependent ordering

Use specific collation where needed in new test

XversionUpgrade-REL_17_STABLE-HEAD fails due to missing function (after b1720fe63)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-04-08%2023%3A17%3A00 - master

upgrade.crake/HEAD/inst/REL_17_STABLE-20250408T193051.051/log/pg_upgrade_internal.log
Restoring database schemas in the new cluster                 
*failure*
Consult the last few lines of "/home/andrew/bf/root/upgrade.crake/HEAD/inst/REL_17_STABLE-upgrade/pg_upgrade_output.d/20250408T193051.051/log/pg_upgrade_dump_16384.log" for
the probable cause of the failure.

upgrade.crake/HEAD/inst/REL_17_STABLE-20250408T193051.051/log/pg_upgrade_dump_16384.log
pg_restore: creating FUNCTION "public.set_ttdummy(integer)"
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 2010; 1255 20296 FUNCTION set_ttdummy(integer) buildfarm
pg_restore: error: could not execute query: ERROR:  could not find function "set_ttdummy" in file "/home/andrew/bf/root/saves.crake/HEAD/lib/postgresql/regress.so"
Command was: CREATE FUNCTION "public"."set_ttdummy"(integer) RETURNS integer
    LANGUAGE "c" STRICT
    AS '$libdir/regress.so', 'set_ttdummy';

pgsql: Adjust AdjustUpgrade.pm for commit b1720fe63

Adjust AdjustUpgrade.pm for commit b1720fe63

035_standby_logical_decoding_standby.pl fails due to missing activeslot invalidation

(drongo executes the 035 test for longer than 500 seconds)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-06-06%2012%3A36%3A11 - HEAD

 40/287 postgresql:recovery / recovery/035_standby_logical_decoding                     ERROR          2193.29s   (exit status 255 or signal 127 SIGinvalid)

---
regress_log_035_standby_logical_decoding
[13:55:13.725](34.411s) ok 25 - inactiveslot slot invalidation is logged with vacuum on pg_class
[13:55:13.727](0.002s) not ok 26 - activeslot slot invalidation is logged with vacuum on pg_class
[13:55:13.728](0.001s) #   Failed test 'activeslot slot invalidation is logged with vacuum on pg_class'
#   at C:/prog/bf/root/HEAD/pgsql/src/test/recovery/t/035_standby_logical_decoding.pl line 229.
[14:27:42.995](1949.267s) # poll_query_until timed out executing this query:
# select (confl_active_logicalslot = 1) from pg_stat_database_conflicts where datname = 'testdb'
# expecting this output:
# t
# last actual query output:
# f
# with stderr:
[14:27:42.999](0.004s) not ok 27 - confl_active_logicalslot updated
[14:27:43.000](0.001s) #   Failed test 'confl_active_logicalslot updated'
#   at C:/prog/bf/root/HEAD/pgsql/src/test/recovery/t/035_standby_logical_decoding.pl line 235.
Timed out waiting confl_active_logicalslot to be updated at 
C:/prog/bf/root/HEAD/pgsql/src/test/recovery/t/035_standby_logical_decoding.pl line 235.

---
035_standby_logical_decoding_standby.log:
2024-06-06 13:55:07.715 UTC [9172:7] LOG:  invalidating obsolete replication slot "row_removal_inactiveslot"
2024-06-06 13:55:07.715 UTC [9172:8] DETAIL:  The slot conflicted with xid horizon 754.
2024-06-06 13:55:07.715 UTC [9172:9] CONTEXT:  WAL redo at 0/4020A80 for Heap2/PRUNE_ON_ACCESS: snapshotConflictHorizon: 754, isCatalogRel: T, nplans: 0, nredirected: 0, ndead: 1, nunused: 0, dead: [48]; blkref #0: rel 1663/16384/2610, blk 0
2024-06-06 13:55:14.372 UTC [7532:1] [unknown] LOG:  connection received: host=127.0.0.1 port=55328
2024-06-06 13:55:14.381 UTC [7532:2] [unknown] LOG:  connection authenticated: identity="EC2AMAZ-P7KGG90\\pgrunner" method=sspi (C:/prog/bf/root/HEAD/pgsql.build/testrun/recovery/035_standby_logical_decoding/data/t_035_standby_logical_decoding_standby_data/pgdata/pg_hba.conf:2)
2024-06-06 13:55:14.381 UTC [7532:3] [unknown] LOG:  connection authorized: user=pgrunner database=postgres application_name=035_standby_logical_decoding.pl
2024-06-06 13:55:14.443 UTC [7532:4] 035_standby_logical_decoding.pl LOG:  statement: select (confl_active_logicalslot = 1) from pg_stat_database_conflicts where datname = 'testdb'
2024-06-06 13:55:14.452 UTC [7532:5] 035_standby_logical_decoding.pl LOG:  disconnection: session time: 0:00:00.090 user=pgrunner database=postgres host=127.0.0.1 port=55328
# (there is no `invalidating obsolete replication slot "row_removal_activeslot"` message)
...
2024-06-06 14:27:42.675 UTC [4032:4] 035_standby_logical_decoding.pl LOG:  statement: select (confl_active_logicalslot = 1) from pg_stat_database_conflicts where datname = 'testdb'
2024-06-06 14:27:42.681 UTC [4032:5] 035_standby_logical_decoding.pl LOG:  disconnection: session time: 0:00:00.080 user=pgrunner database=postgres host=127.0.0.1 port=58713
2024-06-06 14:27:43.095 UTC [7892:2] FATAL:  could not receive data from WAL stream: server closed the connection unexpectedly
         This probably means the server terminated abnormally
         before or while processing the request.

Test slots invalidations in 035_standby_logical_decoding.pl only if dead rows are removed \ 035_standby_logical_decoding.pl fails due to bgwriter activity

Stabilize 035_standby_logical_decoding.pl

syscache-update-pruned.spec fails on Valgrind animal due to unfixed bug not detected

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-03%2019%3A52%3A38 - master

--- /home/bf/bf-build/skink-master/HEAD/pgsql/src/test/modules/injection_points/expected/syscache-update-pruned.out	2025-01-25 19:30:50.005386842 +0000
+++ /home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/injection_points/isolation/results/syscache-update-pruned.out	2025-03-03 21:08:02.025314915 +0000
@@ -75,6 +75,7 @@
 	SELECT FROM injection_points_wakeup('heap_update-before-pin');
  <waiting ...>
 step grant1: <... completed>
+ERROR:  tuple concurrently deleted
 step wakegrant4: <... completed>
 step inspect4: 
 	SELECT relhastriggers, relhassubclass FROM pg_class
@@ -82,6 +83,6 @@
 
 relhastriggers|relhassubclass
 --------------+--------------
-f             |f             
+t             |t             
 (1 row)

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-13%2021%3A36%3A01 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-21%2019%3A09%3A59 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-23%2021%3A38%3A58 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-04-06%2000%3A50%3A36 - master

BUG #17821: Assertion failed in heap_update() due to heap pruning \ isolation permutation behaves as if the bug was fixed

Fix test races between syscache-update-pruned.spec and autovacuum

002_pg_upgrade fails due to timeout under Valgrind

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-04-02%2015%3A24%3A53 - master

256/333 postgresql:pg_upgrade / pg_upgrade/002_pg_upgrade                               TIMEOUT        10000.58s   killed by signal 15 SIGTERM


# All 226 tests passed.
[18:18:19.083](7101.600s) ok 5 - regression tests pass

---
pgsql.build/testrun/pg_upgrade/002_pg_upgrade/log/regress_log_002_pg_upgrade
Creating dump of global objects                               ok
Creating dump of database schemas                             death by signal at /home/bf/bf-build/skink-master/HEAD/pgsql/src/test/perl/PostgreSQL/Test/Cluster.pm line 181.
# Postmaster PID for node "old_node" is 1401171
### Stopping node "old_node" using mode immediate
# Running: pg_ctl --pgdata /home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_old_node_data/pgdata --mode immediate stop
waiting for server to shut down.... done
server stopped
# No postmaster PID for node "old_node"
# Postmaster PID for node "dst_node" is 967766
### Stopping node "dst_node" using mode immediate
# Running: pg_ctl --pgdata /home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/pg_upgrade/002_pg_upgrade/data/t_002_pg_upgrade_dst_node_data/pgdata --mode immediate stop
waiting for server to shut down.... done
server stopped
# No postmaster PID for node "dst_node"
# No postmaster PID for node "new_node"
[19:03:08.854](361.782s) # Tests were run but no plan was declared and done_testing() was not seen.
[19:03:08.855](0.000s) # Looks like your test exited with 4 just after 17.

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-04-02%2019%3A46%3A13 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-04-03%2007%3A06%3A19 - master

Test to dump and restore objects left behind by regression \ pg_upgrade tests have been failing on skink/valgrind

Set log_statement=none in t/002_pg_upgrade.pl

pgp-info.sql fails under Valgrind (after 749a9e20c)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-04-05%2020%3A52%3A38 - master

 82/334 postgresql:pgcrypto / pgcrypto/regress                                          ERROR            585.28s   exit status 2

---
pgsql.build/testrun/pgcrypto/regress/log/postmaster.log
2025-04-05 22:49:17.105 UTC client backend[2917101] pg_regress/pgp-info STATEMENT:  select pgp_key_id(dearmor(seckey)) from keytbl where id=4;
==2917549== VALGRINDERROR-BEGIN
==2917549== Invalid write of size 1
==2917549==    at 0x11D4AD9C: px_crypt_shacrypt (crypt-sha.c:605)
==2917549==    by 0x11D54B50: run_crypt_sha (px-crypt.c:76)
==2917549==    by 0x11D54BCB: px_crypt (px-crypt.c:119)
==2917549==    by 0x11D4BCBB: pg_crypt (pgcrypto.c:228)
==2917549==    by 0x3BBCEA: ExecInterpExpr (execExprInterp.c:1001)
==2917549==    by 0x3B790E: ExecInterpExprStillValid (execExprInterp.c:2299)
==2917549==    by 0x48FD40: ExecEvalExprSwitchContext (executor.h:466)
==2917549==    by 0x48FD40: evaluate_expr (clauses.c:5012)
==2917549==    by 0x48FF08: evaluate_function (clauses.c:4519)
==2917549==    by 0x492054: simplify_function (clauses.c:4108)
==2917549==    by 0x4901FA: eval_const_expressions_mutator (clauses.c:2593)
==2917549==    by 0x432CDE: expression_tree_mutator_impl (nodeFuncs.c:3486)
==2917549==    by 0x48FFB9: eval_const_expressions_mutator (clauses.c:3727)
==2917549==  Address 0x82fa740 is 912 bytes inside a recently re-allocated block of size 8,192 alloc'd
==2917549==    at 0x4844818: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==2917549==    by 0x71EF75: AllocSetContextCreateInternal (aset.c:444)
==2917549==    by 0x3D17AE: CreateExprContextInternal (execUtils.c:260)
==2917549==    by 0x3D1CA8: CreateExprContext (execUtils.c:310)
==2917549==    by 0x3D1ED8: MakePerTupleExprContext (execUtils.c:462)
==2917549==    by 0x48FDBF: evaluate_expr (clauses.c:5013)
==2917549==    by 0x48FF08: evaluate_function (clauses.c:4519)
==2917549==    by 0x492054: simplify_function (clauses.c:4108)
==2917549==    by 0x4901FA: eval_const_expressions_mutator (clauses.c:2593)
==2917549==    by 0x432CDE: expression_tree_mutator_impl (nodeFuncs.c:3486)
==2917549==    by 0x48FFB9: eval_const_expressions_mutator (clauses.c:3727)
==2917549==    by 0x432EFD: expression_tree_mutator_impl (nodeFuncs.c:3572)
==2917549== 
==2917549== VALGRINDERROR-END

Modern SHA2- based password hashes for pgcrypto \ Valgrind did find issue

Follow-up fixes for SHA-2 patch (commit 749a9e20c)

001_aio.pl fails under Valgrind

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-04-02%2015%3A24%3A53 - master

331/333 postgresql:test_aio / test_aio/001_aio                                          ERROR            343.77s   exit status 29

pgsql.build/testrun/test_aio/001_aio/log/001_aio_io_uring.log
2025-04-02 19:33:58.897 UTC [1807359][client backend][3/6:0] DEBUG:  io 192       |op read |target smgr|state SUBMITTED       : wait_one io_gen: 5, ref_gen: 5, cycle 0
2025-04-02 19:33:58.899 UTC [1807359][client backend][3/6:0] LOG:  short read injection point called, is enabled: 0
==1807359== VALGRINDERROR-BEGIN
==1807359== Invalid read of size 2
==1807359==    at 0x59C5AC: PageIsNew (bufpage.h:237)
==1807359==    by 0x59C5AC: PageIsVerified (bufpage.c:108)
==1807359==    by 0x567570: buffer_readv_complete_one (bufmgr.c:6873)
==1807359==    by 0x567570: buffer_readv_complete (bufmgr.c:6996)
==1807359==    by 0x567570: shared_buffer_readv_complete (bufmgr.c:7153)
==1807359==    by 0x55DAB2: pgaio_io_call_complete_shared (aio_callback.c:256)
==1807359==    by 0x55D3F1: pgaio_io_process_completion (aio.c:512)
==1807359==    by 0x55F23A: pgaio_uring_drain_locked (method_io_uring.c:370)
==1807359==    by 0x55F4B8: pgaio_uring_wait_one (method_io_uring.c:449)
==1807359==    by 0x55C402: pgaio_io_wait (aio.c:587)
==1807359==    by 0x55C5B0: pgaio_wref_wait (aio.c:900)
==1807359==    by 0x8639240: read_rel_block_ll (test_aio.c:440)
==1807359==    by 0x3B90DC: ExecInterpExpr (execExprInterp.c:953)
==1807359==    by 0x3B4DCE: ExecInterpExprStillValid (execExprInterp.c:2299)
==1807359==    by 0x3F7C57: ExecEvalExprNoReturn (executor.h:445)
==1807359==  Address 0x8fa400e is in a rw- anonymous segment
==1807359== 
==1807359== VALGRINDERROR-END

Other occurrences:

AIO v2.5 \ enabling liburing support for skink led to failure

aio: Make AIO more compatible with valgrind

028_row_filter.pl, 008_min_recovery_point.pl fail due to pgstat-related assert triggered

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-04-11%2007%3A41%3A36 - master

335/335 postgresql:subscription / subscription/028_row_filter                           ERROR           8381.24s   exit status 29

---
regress_log_028_row_filter
[10:59:49.985](12.605s) ok 2 - check table tab_rf_x should not be filtered
#### Begin standard error
psql:<stdin>:1: NOTICE:  dropped replication slot "tap_sub" on publisher
#### End standard error
#### Begin standard error
psql:<stdin>:1: NOTICE:  created replication slot "tap_sub" on publisher
#### End standard error
Waiting for all subscriptions in "subscriber" to synchronize data
[13:18:01.005](8291.020s) # poll_query_until timed out executing this query:
# SELECT count(1) = 0 FROM pg_subscription_rel WHERE srsubstate NOT IN ('r', 's');
# expecting this output:
# t
# last actual query output:
# f
# with stderr:

---
028_row_filter_publisher.log
2025-04-11 11:01:06.175 UTC [2975477][walsender][29/0:0] STATEMENT:  START_REPLICATION SLOT "pg_16410_sync_16392_7491957737045826723" LOGICAL 0/17DEB30 (proto_version '4', streaming 'parallel', origin 'any', publication_names '"tap_pub_x","tap_pub_allinschema"')
TRAP: failed Assert("pending_since == 0"), File: "../pgsql/src/backend/utils/activity/pgstat.c", Line: 734, PID: 2975477
postgres: publisher: walsender bf postgres [local] START_REPLICATION(ExceptionalCondition+0x5f) [0x6fb855]
postgres: publisher: walsender bf postgres [local] START_REPLICATION(pgstat_report_stat+0x119) [0x5cad06]
postgres: publisher: walsender bf postgres [local] START_REPLICATION(PostgresMain+0x80f) [0x5b1e84]
postgres: publisher: walsender bf postgres [local] START_REPLICATION(BackendMain+0x59) [0x5aacfe]
postgres: publisher: walsender bf postgres [local] START_REPLICATION(postmaster_child_launch+0x117) [0x4f8e27]
postgres: publisher: walsender bf postgres [local] START_REPLICATION(+0x3f3eec) [0x4fbeec]
postgres: publisher: walsender bf postgres [local] START_REPLICATION(+0x3f5c6b) [0x4fdc6b]
postgres: publisher: walsender bf postgres [local] START_REPLICATION(PostmasterMain+0x1190) [0x4ff26c]
postgres: publisher: walsender bf postgres [local] START_REPLICATION(main+0x1e2) [0x42afe2]
/lib/x86_64-linux-gnu/libc.so.6(+0x29ca8) [0x5b3bca8]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x5b3bd65]
postgres: publisher: walsender bf postgres [local] START_REPLICATION(_start+0x21) [0x1ee761]
2025-04-11 11:01:06.574 UTC [2971921][postmaster][:0] LOG:  client backend (PID 2975477) was terminated by signal 6: Aborted
2025-04-11 11:01:06.574 UTC [2971921][postmaster][:0] DETAIL:  Failed process was running: START_REPLICATION SLOT "pg_16410_sync_16392_7491957737045826723" LOGICAL 0/17DEB30 (proto_version '4', streaming 'parallel', origin 'any', publication_names '"tap_pub_x","tap_pub_allinschema"')

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-04-13%2018%3A55%3A03 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mamba&dt=2025-04-15%2001%3A00%3A04 - master

pending_since assertion failure on skink

Remove assertion based on pending_since in pgstat_report_stat()

045_archive_restartpoint.pl fails on skink due to pg_ctl stop timeout

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-04-20%2015%3A36%3A35 - master

 57/336 postgresql:recovery / recovery/045_archive_restartpoint                         ERROR            614.72s   (exit status 255 or signal 127 SIGinvalid)

---
regress_log_045_archive_restartpoint
# Backup finished
### Stopping node "primary" using mode fast
# Running: pg_ctl --pgdata /home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/recovery/045_archive_restartpoint/data/t_045_archive_restartpoint_primary_data/pgdata --mode fast stop
waiting for server to shut down........................................................................................................................................................................................................................................................................................................................................................................... failed
pg_ctl: server does not shut down

---
045_archive_restartpoint_primary.log
2025-04-20 17:21:23.750 UTC [1576688][postmaster][:0] LOG:  received fast shutdown request
2025-04-20 17:21:23.760 UTC [1576688][postmaster][:0] LOG:  aborting any active transactions
2025-04-20 17:21:24.165 UTC [1576688][postmaster][:0] LOG:  background worker "logical replication launcher" (PID 1577388) exited with exit code 1
2025-04-20 17:21:24.170 UTC [1577180][checkpointer][:0] LOG:  shutting down
2025-04-20 17:21:24.235 UTC [1577180][checkpointer][:0] LOG:  checkpoint starting: shutdown immediate
2025-04-20 17:21:24.333 UTC [1577180][checkpointer][:0] LOG:  checkpoint complete: wrote 0 buffers (0.0%), wrote 0 SLRU buffers; 0 WAL file(s) added, 0 removed, 1 recycled; write=0.004 s, sync=0.001 s, total=0.106 s; sync files=0, longest=0.000 s, average=0.000 s; distance=2048 kB, estimate=2048 kB; lsn=0/14B00028, redo lsn=0/14B00028
2025-04-20 17:27:35.735 UTC [1576688][postmaster][:0] LOG:  received immediate shutdown request
2025-04-20 17:27:35.969 UTC [1577386][archiver][:0] FATAL:  archive command was terminated by signal 3: Quit
2025-04-20 17:27:35.969 UTC [1577386][archiver][:0] DETAIL:  The failed archive command was: cp "pg_wal/00000001000000000000006D" "/home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/recovery/045_archive_restartpoint/data/t_045_archive_restartpoint_primary_data/archives/00000001000000000000006D"
2025-04-20 17:27:36.560 UTC [1576688][postmaster][:0] LOG:  database system is shut down

Back-patch of avoid multiple hard links to same WAL file \ test fails with valgrind

Valgrind config changed to --trace-children=no

040_standby_failover_slots_sync.pl fails due to broken assertion (after 4868c96bc)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sidewinder&dt=2025-04-09%2010%3A36%3A46 - master


# Looks like your test exited with 32 just after 32.
[13:23:27] t/040_standby_failover_slots_sync.pl .. 
Dubious, test returned 32 (wstat 8192, 0x2000)
All 32 subtests passed

---
pgsql.build/src/test/recovery/tmp_check/log/regress_log_040_standby_failover_slots_sync
[13:23:13.580](0.051s) ok 32 - synced slot retained on the new primary
Waiting for replication conn regress_mysub1's replay_lsn to pass 0/60051C0 on standby1
ack Broken pipe: write( 14, 'SELECT '0/60051C0' <= replay_lsn AND state = 'streaming'
         FROM pg_catalog.pg_stat_replication
         WHERE application_name IN ('regress_mysub1', 'walreceiver')' ) at /usr/pkg/lib/perl5/vendor_perl/5.40.0/IPC/Run/IO.pm line 550.
# Postmaster PID for node "publisher" is 25391
### Stopping node "publisher" using mode immediate
# Running: pg_ctl --pgdata /home/pgbf/buildroot/HEAD/pgsql.build/src/test/recovery/tmp_check/t_040_standby_failover_slots_sync_publisher_data/pgdata --mode immediate stop
waiting for server to shut down.... done
server stopped

---
pgsql.build/src/test/recovery/tmp_check/log/040_standby_failover_slots_sync_standby1.log
TRAP: failed Assert("(txn->txn_flags & RBTXN_PREPARE_STATUS_MASK) == (RBTXN_IS_PREPARED | RBTXN_SKIPPED_PREPARE)"), File: "reorderbuffer.c", Line: 2996, PID: 24434
...
2025-04-09 13:23:13.605 CEST [25955:4] 040_standby_failover_slots_sync.pl LOG:  statement: SELECT pg_is_in_recovery()
2025-04-09 13:23:13.614 CEST [25955:5] 040_standby_failover_slots_sync.pl LOG:  disconnection: session time: 0:00:00.013 user=pgbf database=postgres host=[local]
0x9abdc4 <ExceptionalCondition+0x67> at /home/pgbf/buildroot/HEAD/pgsql.build/tmp_install/home/pgbf/buildroot/HEAD/inst/bin/postgres
0x7e0ba7 <ReorderBufferFinishPrepared+0x1cb> at /home/pgbf/buildroot/HEAD/pgsql.build/tmp_install/home/pgbf/buildroot/HEAD/inst/bin/postgres
0x7cf7eb <xact_decode+0x432> at /home/pgbf/buildroot/HEAD/pgsql.build/tmp_install/home/pgbf/buildroot/HEAD/inst/bin/postgres
0x7cf238 <LogicalDecodingProcessRecord+0x63> at /home/pgbf/buildroot/HEAD/pgsql.build/tmp_install/home/pgbf/buildroot/HEAD/inst/bin/postgres
0x7fd8f2 <XLogSendLogical+0x42> at /home/pgbf/buildroot/HEAD/pgsql.build/tmp_install/home/pgbf/buildroot/HEAD/inst/bin/postgres
0x7fe5a2 <WalSndLoop+0x7f> at /home/pgbf/buildroot/HEAD/pgsql.build/tmp_install/home/pgbf/buildroot/HEAD/inst/bin/postgres
0x7ff5b7 <exec_replication_command+0xdc8> at /home/pgbf/buildroot/HEAD/pgsql.build/tmp_install/home/pgbf/buildroot/HEAD/inst/bin/postgres
0x8626e2 <PostgresMain+0xa1f> at /home/pgbf/buildroot/HEAD/pgsql.build/tmp_install/home/pgbf/buildroot/HEAD/inst/bin/postgres
0x85da82 <BackendMain+0x4d> at /home/pgbf/buildroot/HEAD/pgsql.build/tmp_install/home/pgbf/buildroot/HEAD/inst/bin/postgres
0x7b4257 <postmaster_child_launch+0xe8> at /home/pgbf/buildroot/HEAD/pgsql.build/tmp_install/home/pgbf/buildroot/HEAD/inst/bin/postgres
0x7b7ae7 <ServerLoop+0xf92> at /home/pgbf/buildroot/HEAD/pgsql.build/tmp_install/home/pgbf/buildroot/HEAD/inst/bin/postgres
0x7b949a <PostmasterMain+0xd1a> at /home/pgbf/buildroot/HEAD/pgsql.build/tmp_install/home/pgbf/buildroot/HEAD/inst/bin/postgres
0xa36f67 <main+0x529> at /home/pgbf/buildroot/HEAD/pgsql.build/tmp_install/home/pgbf/buildroot/HEAD/inst/bin/postgres
2025-04-09 13:23:13.625 CEST [26300:1] [unknown] LOG:  connection received: host=[local]

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mule&dt=2025-04-23%2019%3A30%3A03 - master

Fix slot synchronization with two_phase decoding enabled \ tests for slotsync on two-phase enabled slots failed

Fix assertion failure during decoding from synced slots.

032_relfilenode_reuse.pl fails due to AIO-related error (after 12ce89fd0)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=scorpion&dt=2025-05-09%2022%3A02%3A02 - master

158/336 postgresql:recovery / recovery/032_relfilenode_reuse                            ERROR           201.17s   (exit status 255 or signal 127 SIGinvalid)

---
regress_log_032_relfilenode_reuse
[22:06:06.277](0.225s) ok 8 - standby: post move contents as expected
[22:09:08.082](181.805s) Bail out!  aborting wait: program timed out
stream contents: >><<
pattern searched for: (?^m:warmed_buffers)

---
032_relfilenode_reuse_standby.log
2025-05-09 22:06:07.262 UTC [2110319][startup][35/0:0] CONTEXT:  WAL redo at 0/43E3C58 for Database/DROP: dir 1663/50001
2025-05-09 22:06:07.262 UTC [2110721][client backend][0/2:0] DEBUG:  waiting for free IO with 0 pending, 1 in-flight, 1 idle IOs
2025-05-09 22:06:07.267 UTC [2110721][client backend][0/2:0] DEBUG:  io 0         |op read |target smgr|state SUBMITTED       : waiting for IO before FD 46 gets closed, 1 in-flight IOs
2025-05-09 22:06:07.267 UTC [2110721][client backend][0/2:0] ERROR:  no free IOs despite no in-flight IOs
2025-05-09 22:06:07.267 UTC [2110721][client backend][0/2:0] DETAIL:  0 pending, 0 in-flight, 0 idle IOs
2025-05-09 22:06:07.267 UTC [2110721][client backend][0/2:0] STATEMENT:  SELECT SUM(pg_prewarm(oid)) warmed_buffers FROM pg_class WHERE pg_relation_filenode(oid) != 0;

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=scorpion&dt=2025-04-08%2001%3A36%3A41 - master

AIO v2.5 \ ERROR: no free IOs despite no in-flight IOs

aio: Fix possible state confusions due to interrupt processing

XversionUpgrade-REL_15_STABLE-XXX fails due to output mismatch (after 29f7ce6fe)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2025-05-19%2019%3A34%3A01 - master

upgrade.copperhead/HEAD/dumpdiff-REL_15_STABLE
--- /home/pgbf/buildroot/upgrade.copperhead/HEAD/origin-REL_15_STABLE.sql.fixed	2025-05-19 22:52:13.483629281 +0200
+++ /home/pgbf/buildroot/upgrade.copperhead/HEAD/converted-REL_15_STABLE-to-HEAD.sql.fixed	2025-05-19 22:52:13.527629215 +0200
@@ -182023,10 +182023,10 @@
 -- Name: limit_thousand_v_5; Type: VIEW; Schema: public; Owner: buildfarm
 --
 CREATE VIEW public.limit_thousand_v_5 AS
- SELECT onek.thousand
+ SELECT thousand
    FROM public.onek
-  WHERE (onek.thousand < 995)
-  ORDER BY onek.thousand
+  WHERE (thousand < 995)
+  ORDER BY thousand
  LIMIT ALL;
 ALTER VIEW public.limit_thousand_v_5 OWNER TO buildfarm;
 --

BUG #18929: After the view is created, ... \ need to do something about output mismatches

Fix cross-version upgrade test failure

021_twophase.pl fails due to race condition

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=kestrel&dt=2025-05-22%2021%3A19%3A22 - master

281/336 postgresql:subscription / subscription/021_twophase                             ERROR            16.78s   exit status 1

---
pgsql.build/testrun/subscription/021_twophase/log/regress_log_021_twophase
[21:24:51.862](0.162s) not ok 24 - should be no prepared transactions on subscriber
[21:24:51.862](0.000s) #   Failed test 'should be no prepared transactions on subscriber'
#   at /home/bf/bf-build/kestrel/HEAD/pgsql/src/test/subscription/t/021_twophase.pl line 438.
[21:24:51.862](0.000s) #          got: '1'
#     expected: '0'
Waiting for replication conn appname_copy's replay_lsn to pass 0/17F07B8 on publisher
done

Random subscription 021_twophase test failure on kestrel

Fix race condition in subscription TAP test 021_twophase

040_standby_failover_slots_sync.pl fails due to broken assertion (after 3ff2a1f0c)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=calliphoridae&dt=2025-04-29%2009%3A11%3A31 - master

326/336 postgresql:recovery / recovery/040_standby_failover_slots_sync                  ERROR           302.48s   exit status 29

---
pgsql.build/testrun/recovery/040_standby_failover_slots_sync/log/regress_log_040_standby_failover_slots_sync
[09:18:05.744](0.098s) ok 29 - the prepared transaction is not replicated to the subscriber
Waiting for replication conn standby1's replay_lsn to pass 0/6005150 on publisher
[09:22:31.249](265.506s) # poll_query_until timed out executing this query:
# SELECT '0/6005150' <= replay_lsn AND state = 'streaming'
#          FROM pg_catalog.pg_stat_replication
#          WHERE application_name IN ('standby1', 'walreceiver')
# expecting this output:
# t
# last actual query output:
# 
# with stderr:
[09:22:31.299](0.049s) # Last pg_stat_replication contents:

---
pgsql.build/testrun/recovery/040_standby_failover_slots_sync/log/040_standby_failover_slots_sync_standby1.log
2025-04-29 09:18:05.160 UTC [1022669][slotsync worker][10/3:0] LOG:  logical decoding found consistent point at 0/5000048
2025-04-29 09:18:05.160 UTC [1022669][slotsync worker][10/3:0] DETAIL:  There are no running transactions.
TRAP: failed Assert("slot->data.two_phase_at <= slot->data.confirmed_flush"), File: "../pgsql/src/backend/replication/logical/slotsync.c", Line: 311, PID: 1022669
postgres: standby1: slotsync worker (ExceptionalCondition+0x83) [0x560fd2e90e59]
postgres: standby1: slotsync worker (+0x44a849) [0x560fd2cbd849]
postgres: standby1: slotsync worker (+0x44b5f3) [0x560fd2cbe5f3]
postgres: standby1: slotsync worker (ReplSlotSyncWorkerMain+0x592) [0x560fd2cbf4fd]
postgres: standby1: slotsync worker (postmaster_child_launch+0x130) [0x560fd2c7b435]
postgres: standby1: slotsync worker (+0x40aaa7) [0x560fd2c7daa7]
postgres: standby1: slotsync worker (+0x40cefd) [0x560fd2c7fefd]
postgres: standby1: slotsync worker (PostmasterMain+0x1466) [0x560fd2c816d9]
postgres: standby1: slotsync worker (main+0x7f0) [0x560fd2bb6292]
/lib/x86_64-linux-gnu/libc.so.6(+0x29ca8) [0x7fa1a4f1eca8]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7fa1a4f1ed65]
postgres: standby1: slotsync worker (_start+0x21) [0x560fd29591a1]
2025-04-29 09:18:05.631 UTC [1023004][not initialized][:0] LOG:  connection received: host=[local]

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mule&dt=2025-05-03%2015%3A30%3A02 - master

Fix slot synchronization with two_phase decoding enabled \ recently added assertion broken

Don't retreat slot's confirmed_flush LSN.

plpython_error.sql fails on shelduck due to old python (after 1a857348e)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=shelduck&dt=2025-06-07%2012%3A48%3A22 - master

--- /home/linux1/17-shelduck/buildroot/HEAD/pgsql.build/src/pl/plpython/expected/plpython_error.out	2025-06-07 12:48:24.306626560 +0000
+++ /home/linux1/17-shelduck/buildroot/HEAD/pgsql.build/src/pl/plpython/results/plpython_error.out	2025-06-07 12:57:41.226736568 +0000
@@ -243,7 +243,7 @@
 plpy.nonexistent
 $$ LANGUAGE plpython3u;
 SELECT toplevel_attribute_error();
-ERROR:  AttributeError: module 'plpy' has no attribute 'nonexistent'
+ERROR:  AttributeError: 'module' object has no attribute 'nonexistent'
 CONTEXT:  Traceback (most recent call last):
   PL/Python function "toplevel_attribute_error", line 2, in <module>
     plpy.nonexistent

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=shelduck&dt=2025-06-08%2012%3A08%3A04 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=shelduck&dt=2025-06-09%2012%3A12%3A09 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=shelduck&dt=2025-06-10%2012%3A08%3A04 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=shelduck&dt=2025-06-11%2013%3A13%3A37 - master

What's our minimum supported Python version? \ shelduck's python is 3.4.10

config_opts: '--with-python' -> '--without-python'

027_stream_regress.pl failed due to AIO-related assert triggered

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sifaka&dt=2025-04-23%2020%3A03%3A24 - master

#   Failed test 'regression tests pass'
#   at t/027_stream_regress.pl line 95.
#          got: '256'
#     expected: '0'
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 29 just after 2.
[16:08:31] t/027_stream_regress.pl ............... 
Dubious, test returned 29 (wstat 7424, 0x1d00)

TRAP: failed Assert("aio_ret->result.status != PGAIO_RS_UNKNOWN"), File: "bufmgr.c", Line: 1605, PID: 79322
0   postgres                            0x0000000100e3df2c ExceptionalCondition + 108
1   postgres                            0x0000000100cbb154 WaitReadBuffers + 616
2   postgres                            0x0000000100f072bc read_stream_next_buffer.cold.1 + 184
3   postgres                            0x0000000100cb6dd8 read_stream_next_buffer + 300
4   postgres                            0x00000001009b75b4 heap_fetch_next_buffer + 136
5   postgres                            0x00000001009ad8c4 heapgettup + 368
6   postgres                            0x00000001009ad364 heap_getnext + 104
7   postgres                            0x00000001009b9770 heapam_index_build_range_scan + 700
8   postgres                            0x00000001009ef4b8 spgbuild + 480
9   postgres                            0x0000000100a41acc index_build + 428
10  postgres                            0x0000000100a43d14 reindex_index + 752
11  postgres                            0x0000000100ad09e0 ExecReindex + 1908
12  postgres                            0x0000000100d04628 ProcessUtilitySlow + 1300
13  postgres                            0x0000000100d03754 standard_ProcessUtility + 1528
14  pg_stat_statements.dylib            0x000000010158d7a0 pgss_ProcessUtility + 632
15  postgres                            0x0000000100d02cec PortalRunUtility + 184
16  postgres                            0x0000000100d02354 PortalRunMulti + 236
17  postgres                            0x0000000100d01d94 PortalRun + 456
18  postgres                            0x0000000100d00e10 exec_simple_query + 1308
...
2025-04-23 16:08:28.834 EDT [78788:4] LOG:  client backend (PID 79322) was terminated by signal 6: Abort trap: 6
2025-04-23 16:08:28.834 EDT [78788:5] DETAIL:  Failed process was running: reindex index spgist_point_idx;

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2025-05-23%2020%3A30%3A07 - master

Non-reproducible AIO failure

aio: Add missing memory barrier when waiting for IO handle

Assert in costsize.c failed on leafhopper

(leafhopper is a graviton4 animal)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2025-01-16%2007%3A41%3A03 - master

#   Failed test 'regression tests pass'
#   at t/027_stream_regress.pl line 95.
#          got: '256'
#     expected: '0'

---
027_stream_regress_primary.log
TRAP: failed Assert("outerstartsel <= outerendsel"), File: "costsize.c", Line: 3678, PID: 823960

2025-01-16 07:47:32.998 UTC [821755:97] LOG:  client backend (PID 823960) was terminated by signal 6: Aborted
2025-01-16 07:47:32.998 UTC [821755:98] DETAIL:  Failed process was running: SELECT t1.oid, t1.typname, p1.oid, p1.proname
	FROM pg_type AS t1, pg_proc AS p1
	WHERE t1.typinput = p1.oid AND p1.provolatile NOT IN ('i', 's');

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2025-01-19%2014%3A21%3A04 - master

leafhopper: Assert(...), File: "costsize.c"

Also select_parallel.sql fails on leafhopper

(leafhopper is a graviton4 animal)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2024-12-16%2023%3A43%3A03 - REL_15_STABLE

#   Failed test 'regression tests pass'
#   at t/027_stream_regress.pl line 81.
#          got: '256'
#     expected: '0'

---
regress_log_027_stream_regress
test select_parallel              ... FAILED      507 ms
...
 1 of 213 tests failed. 
...
--- /home/bf/proj/bf/build-farm-17/REL_15_STABLE/pgsql.build/src/test/regress/expected/select_parallel.out	2024-12-16 23:43:03.742123619 +0000
+++ /home/bf/proj/bf/build-farm-17/REL_15_STABLE/pgsql.build/src/test/recovery/tmp_check/results/select_parallel.out	2024-12-16 23:48:25.102618931 +0000
@@ -551,7 +551,7 @@
    ->  Nested Loop (actual rows=98000 loops=1)
          ->  Seq Scan on tenk2 (actual rows=10 loops=1)
                Filter: (thousand = 0)
-               Rows Removed by Filter: 9990
+               Rows Removed by Filter: 447009543

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2024-12-21%2022%3A18%3A04 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2025-01-02%2009%3A21%3A04 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2025-05-12%2010%3A36%3A04 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2025-05-12%2010%3A37%3A04 - REL_17_STABLE

Also memoize.sql fails on on leafhopper (master)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2024-12-18%2023%3A35%3A04 - master

#   Failed test 'regression tests pass'
#   at t/027_stream_regress.pl line 95.
#          got: '256'
#     expected: '0'
# Looks like you failed 1 test of 9.
[23:42:59] t/027_stream_regress.pl ...............
...
diff -U3 /home/bf/proj/bf/build-farm-17/HEAD/pgsql.build/src/test/regress/expected/memoize.out 
/home/bf/proj/bf/build-farm-17/HEAD/pgsql.build/src/test/recovery/tmp_check/results/memoize.out
--- /home/bf/proj/bf/build-farm-17/HEAD/pgsql.build/src/test/regress/expected/memoize.out 2024-12-18 23:35:04.318987642 
+0000
+++ /home/bf/proj/bf/build-farm-17/HEAD/pgsql.build/src/test/recovery/tmp_check/results/memoize.out 2024-12-18 
23:42:24.806028990 +0000
@@ -179,7 +179,7 @@
                 Hits: 980  Misses: 20  Evictions: Zero  Overflows: 0  Memory Usage: NkB
                 ->  Seq Scan on tenk1 t2 (actual rows=1 loops=N)
                       Filter: ((t1.twenty = unique1) AND (t1.two = two))
-                     Rows Removed by Filter: 9999
+                     Rows Removed by Filter: 9775
  (12 rows)

Also:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2025-05-19%2007%3A07%3A04 - REL_17_STABLE

diff -U3 /home/bf/proj/bf/build-farm-17/REL_17_STABLE/pgsql.build/src/test/regress/expected/expressions.out /home/bf/proj/bf/build-farm-17/REL_17_STABLE/pgsql.build/src/test/regress/results/expressions.out
--- /home/bf/proj/bf/build-farm-17/REL_17_STABLE/pgsql.build/src/test/regress/expected/expressions.out	2025-05-19 07:07:04.690414392 +0000
+++ /home/bf/proj/bf/build-farm-17/REL_17_STABLE/pgsql.build/src/test/regress/results/expressions.out	2025-05-19 07:07:25.279802785 +0000
@@ -340,9 +340,13 @@
 create function myinthash(myint) returns integer strict immutable language
   internal as 'hashint4';
 NOTICE:  argument type myint is only a shell
+ERROR:  ROWS is not applicable when function does not return a set
 create type myint (input = myintin, output = myintout, like = int4);
+ERROR:  current transaction is aborted, commands ignored until end of transaction block
 create cast (int4 as myint) without function;
...

Several buildfarm animals fail tests because of shared memory error \ weird test failures on leafhopper
wrong query results on bf leafhopper

Environment updated

046_checkpoint_logical_slot.pl fails on prion due to timeout

(prion runs tests with -DRELCACHE_FORCE_RELEASE -DCATCACHE_FORCE_RELEASE)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-06-14%2001%3A58%3A06 - master

# poll_query_until timed out executing this query:
#
#         SELECT count(*) > 0 FROM pg_stat_activity
#         WHERE backend_type = 'client backend' AND wait_event = 'logical-replication-slot-advance-segment'
#
# expecting this output:
# t
# last actual query output:
# f
# with stderr:
[04:16:27] t/046_checkpoint_logical_slot.pl ......
Dubious, test returned 29 (wstat 7424, 0x1d00)
No subtests run

Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly \ 046_checkpoint_logical_slot fails on prion

Improve runtime and output of tests for replication slots checkpointing.

046_checkpoint_logical_slot.pl hangs up inside pg_logical_slot_get_changes after server restart

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=flaviventris&dt=2025-06-19%2023%3A47%3A08 - master

340/340 postgresql:recovery / recovery/046_checkpoint_logical_slot                      TIMEOUT        3000.22s   killed by signal 15 SIGTERM
...
stderr:
#   Failed test 'Logical slot still valid'
#   at /home/bf/bf-build/flaviventris/HEAD/pgsql/src/test/recovery/t/046_checkpoint_logical_slot.pl line 134.
#          got: 'death by signal at /home/bf/bf-build/flaviventris/HEAD/pgsql/src/test/perl/PostgreSQL/Test/Cluster.pm line 181.
# '
#     expected: ''
# Looks like you failed 1 test of 1.

pgsql: Improve runtime and output of tests for replication slots checkp \ buildfarm animals have started failing

Temporarily remove 046_checkpoint_logical_slot.pl

invalidation_distribution.specs fails on REL_13_STABLE with -DCLOBBER_CACHE_ALWAYS (since 1230be12f)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=trilobite&dt=2025-06-17%2008%3A24%3A00 - REL_13_STABLE

test invalidation_distribution    ... FAILED     1953 ms

=======================
 1 of 10 tests failed. 
=======================

diff -U3 /home/buildfarm/trilobite/buildroot/REL_13_STABLE/pgsql.build/contrib/test_decoding/expected/invalidation_distribution.out /home/buildfarm/trilobite/buildroot/REL_13_STABLE/pgsql.build/contrib/test_decoding/output_iso/results/invalidation_distribution.out
--- /home/buildfarm/trilobite/buildroot/REL_13_STABLE/pgsql.build/contrib/test_decoding/expected/invalidation_distribution.out	2025-06-17 10:24:24.382768613 +0200
+++ /home/buildfarm/trilobite/buildroot/REL_13_STABLE/pgsql.build/contrib/test_decoding/output_iso/results/invalidation_distribution.out	2025-06-17 15:01:53.921913314 +0200
@@ -31,7 +31,7 @@
 step s2_get_binary_changes: SELECT count(data) FROM pg_logical_slot_get_binary_changes('isolation_slot', NULL, NULL, 'proto_version', '1', 'publication_names', 'pub') WHERE get_byte(data, 0) = 73;
 count
 -----
-    0
+    1
 (1 row)
 
 ?column?

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=trilobite&dt=2025-06-23%2007%3A40%3A52 - REL_13_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=avocet&dt=2025-06-20%2006%3A10%3A11 - REL_13_STABLE

Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 \ new test case fails

Fix cache-dependent test failures in logical decoding.

014_binary.pl might fail when apply worker starts only after timeout of 180 seconds

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=snakefly&dt=2025-02-09%2011%3A45%3A05 - master

[12:04:20.537](1.318s) ok 7 - check synced data on subscriber with custom type
timed out waiting for match: (?^:ERROR: ( [A-Z0-9]+:)? incorrect binary data format) at t/014_binary.pl line 269.
# Postmaster PID for node "publisher" is 28332
### Stopping node "publisher" using mode immediate
...
[12:07:20.933](180.395s) # Tests were run but no plan was declared and done_testing() was not seen.

---
pgsql.build/src/test/subscription/tmp_check/log/014_binary_subscriber.log
2025-02-09 12:04:20.554 UTC [28531:4] 014_binary.pl LOG:  statement: CREATE TABLE public.test_mismatching_types (
	        a int PRIMARY KEY
	    );
2025-02-09 12:04:20.556 UTC [28531:5] 014_binary.pl LOG:  statement: ALTER SUBSCRIPTION tsub REFRESH PUBLICATION;
2025-02-09 12:04:20.568 UTC [28531:6] 014_binary.pl LOG:  disconnection: session time: 0:00:00.015 user=postgres database=postgres host=[local]
2025-02-09 12:07:20.629 UTC [28561:1] LOG:  logical replication apply worker for subscription "tsub" has started
2025-02-09 12:07:20.636 UTC [28563:1] LOG:  logical replication table synchronization worker for subscription "tsub", table "test_mismatching_types" has started
2025-02-09 12:07:20.659 UTC [28563:2] ERROR:  incorrect binary data format
2025-02-09 12:07:20.659 UTC [28563:3] CONTEXT:  COPY test_mismatching_types, line 1, column a
2025-02-09 12:07:20.660 UTC [28344:7] LOG:  background worker "logical replication tablesync worker" (PID 28563) exited with exit code 1

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=snakefly&dt=2025-03-17%2020%3A08%3A05 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=snakefly&dt=2025-05-05%2011%3A10%3A29 - master

Improving the latch handling between logical replication launcher and worker processes. \ race condition between DEFAULT_NAPTIME_PER_CYCLE and $timeout_default

Prevent excessive delays before launching new logrep workers.

Several tests fail with due to broken assertion in slot.c (after eb124c3d6)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=scorpion&dt=2025-06-17%2000%3A40%3A46 - master

156/339 postgresql:pg_basebackup / pg_basebackup/020_pg_receivewal                      ERROR            16.48s   exit status 3

---
pgsql.build/testrun/pg_basebackup/020_pg_receivewal/log/020_pg_receivewal_standby.log
TRAP: failed Assert("s->data.restart_lsn >= s->last_saved_restart_lsn"), File: "../pgsql/src/backend/replication/slot.c", Line: 1813, PID: 3945797
postgres: standby: checkpointer (ExceptionalCondition+0x83) [0x55fa69b79f5e]
postgres: standby: checkpointer (InvalidateObsoleteReplicationSlots+0x53c) [0x55fa69982171]
postgres: standby: checkpointer (CreateCheckPoint+0x9ad) [0x55fa6971feb2]
postgres: standby: checkpointer (CheckpointerMain+0x4b1) [0x55fa6996431c]
postgres: standby: checkpointer (postmaster_child_launch+0x130) [0x55fa69964b41]
postgres: standby: checkpointer (+0x40a1a7) [0x55fa699671a7]
postgres: standby: checkpointer (PostmasterMain+0x1563) [0x55fa6996aed6]
postgres: standby: checkpointer (main+0x7f0) [0x55fa6989f798]
/lib/x86_64-linux-gnu/libc.so.6(+0x29ca8) [0x7f1876a54ca8]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7f1876a54d65]
postgres: standby: checkpointer (_start+0x21) [0x55fa696421a1]

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mamba&dt=2025-06-16%2001%3A00%3A04 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mamba&dt=2025-06-17%2005%3A10%3A36 - master

restart_lsn may point to removed WAL segment after hard restart unexpectedly Assertion failure

Remove excess assert from InvalidatePossiblyObsoleteSlot()

XversionUpgrade-REL_18_STABLE-HEAD fails due to unknown function get_val_in_shmem (after fe07100e8)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-07-02%2017%3A11%3A10 - master

upgrade.crake/HEAD/inst/REL_18_STABLE-20250702T132913.031/log/pg_upgrade_internal.log
Restoring database schemas in the new cluster                 
*failure*
Consult the last few lines of "/home/andrew/bf/root/upgrade.crake/HEAD/inst/REL_18_STABLE-upgrade/pg_upgrade_output.d/20250702T132913.031/log/pg_upgrade_dump_55141.log" for
the probable cause of the failure.

---
upgrade.crake/HEAD/inst/REL_18_STABLE-20250702T132913.031/log/pg_upgrade_dump_55141.log
pg_restore: creating FUNCTION "public.get_val_in_shmem()"
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 221; 1255 55237 FUNCTION get_val_in_shmem() buildfarm
pg_restore: error: could not execute query: ERROR:  could not find function "get_val_in_shmem" in file "/home/andrew/bf/root/saves.crake/HEAD/lib/postgresql/test_dsm_registry.so"
Command was: CREATE FUNCTION "public"."get_val_in_shmem"() RETURNS integer
    LANGUAGE "c"
    AS '$libdir/test_dsm_registry', 'get_val_in_shmem';

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-07-02%2017%3A42%3A01 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2025-07-02%2017%3A43%3A03 - master

add function for creating/attaching hash table in DSM registry / renaming functions wasn't a good idea

Fix cross-version upgrade test breakage from commit fe07100e82

XversionUpgrade-REL9_4_STABLE-XXX fails due to non-existing type (after f295494d3)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-07-04%2018%3A45%3A31 - master

upgrade.crake/HEAD/inst/REL9_4_STABLE-20250704T151600.876/log/pg_upgrade_internal.log
...
Checking for not-null constraint inconsistencies              connection failure: ERROR:  type "pg_catalog.regnamespace" does not exist
LINE 1: ...search_path', '', false);;SELECT cc.relnamespace::pg_catalog...                                                            ^

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-07-04%2018%3A19%3A40 - REL_18_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-07-04%2017%3A53%3A40 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-07-04%2017%3A30%3A26 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-07-04%2017%3A01%3A47 - REL_15_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-07-04%2016%3A35%3A00 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-07-04%2016%3A12%3A01 - REL_13_STABLE

pg_upgrade failed with error ... \ no regnamespace in 9.4

Fix new pg_upgrade query not to rely on regnamespace

prion fails at different stages due to timeout on REL_18_STABLE and master

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-07-01%2017%3A29%3A07 - master

(prion uses -DREALLOCATE_BITMAPSETS -DRELCACHE_FORCE_RELEASE -DCATCACHE_FORCE_RELEASE)

timed out after 14400 secs

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-07-03%2018%3A49%3A07 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-07-04%2006%3A19%3A06 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-07-04%2016%3A29%3A07 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-07-04%2020%3A39%3A06 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-07-01%2017%3A28%3A07 - REL_18_STABLE

Buildfarm animal prion can't complete tests in 4 hours nowadays

Timeout increased

drongo can't get through initdb_cache due to failed assertion (after 8fd9bb1d9)

(drongo uses Visual Studio 2019)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-07-01%2016%3A09%3A21 - master

3/3 postgresql:setup / initdb_cache       FAIL             1.78s   exit status 1

pgsql.build/meson-logs/testsetup.txt
----------------------------------- stderr -----------------------------------
TRAP: failed Assert("SysCache[cacheId]->cc_nkeys == 2"), File: "../pgsql/src/backend/utils/cache/syscache.c", Line: 237, PID: 2684
child process was terminated by exception 0xC0000409

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-07-03%2001%3A37%3A49 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-07-03%2019%3A56%3A21 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-07-05%2000%3A07%3A20 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-07-06%2010%3A34%3A32 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-07-07%2013%3A47%3A18 - master

C11 / VS 2019 \ drongo has been failing in initdb

VS 2019 on drongo has been updated

XversionUpgrade fails due to LSN format changed (after 2633dae2e)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-07-07%2012%3A07%3A01 - master

upgrade.crake/HEAD/dumpdiff-REL_18_STABLE

--- /home/andrew/bf/root/upgrade.crake/HEAD/origin-REL_18_STABLE.sql.fixed	2025-07-07 08:24:38.965908928 -0400
+++ /home/andrew/bf/root/upgrade.crake/HEAD/converted-REL_18_STABLE-to-HEAD.sql.fixed	2025-07-07 08:24:38.971908952 -0400
@@ -69761,237 +69761,237 @@
 \\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	fe80::6e40:8ff:fea9:9fce	fe80::6e40:8ff:fea9:9fce/128	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	empty	\\N	\\N
 \\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	fe80::6e40:8ff:fea9:a3b6	fe80::6e40:8ff:fea9:a3b6/128	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	empty	\\N	\\N
 \\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	fe80::6e40:8ff:fea9:a79e	fe80::6e40:8ff:fea9:a79e/128	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	\\N	empty	\\N	\\N
-\\\\x4d41414141414d41414141414d41414141414d41414141414d41414141414d41414141414d41414141414d4141414141	M	MAAAAA	1005713280000	800	800		8800	(8800,0)	1	0	00:00:01:00:00:00	10.2.37.100/24	10.2.37.0/24	M	2019-09-18	05:27:10	1979-01-29 11:05:09	1972-11-12 13:00:00-05	2 mons 13 days 08:00:00	01:30:20+02	1100100000	0010001001100000	33440000.000000000000000000000000000000	88008800-8800-8800-8800-880088008800	empty	0/18800	(800,800),(0,1)
+\\\\x4d41414141414d41414141414d41414141414d41414141414d41414141414d41414141414d41414141414d4141414141	M	MAAAAA	1005713280000	800	800		8800	(8800,0)	1	0	00:00:01:00:00:00	10.2.37.100/24	10.2.37.0/24	M	2019-09-18	05:27:10	1979-01-29 11:05:09	1972-11-12 13:00:00-05	2 mons 13 days 08:00:00	01:30:20+02	1100100000	0010001001100000	33440000.000000000000000000000000000000	88008800-8800-8800-8800-880088008800	empty	0/00018800	(800,800),(0,1)
...

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-07-07%2014%3A57%3A01 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2025-07-07%2014%3A03%3A06 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2025-07-07%2018%3A03%3A06 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=copperhead&dt=2025-07-07%2016%3A01%3A07 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-07-07%2016%3A01%3A53 - master

Inconsistent LSN format in pg_waldump output \ crake is failing the cross-version upgrade

Adapt pg_upgrade test to pg_lsn output format difference

046_checkpoint_logical_slot.pl hangs up on REL_17_STABLE inside pg_logical_slot_get_changes

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=olingo&dt=2025-07-19%2014%3A07%3A23 - REL_17_STABLE

310/310 postgresql:recovery / recovery/046_checkpoint_logical_slot                      TIMEOUT        3000.25s   killed by signal 15 SIGTERM

stderr:
#   Failed test 'Logical slot still valid'
#   at /home/bf/bf-build/olingo/REL_17_STABLE/pgsql/src/test/recovery/t/046_checkpoint_logical_slot.pl line 143.
#          got: 'death by signal at /home/bf/bf-build/olingo/REL_17_STABLE/pgsql/src/test/perl/PostgreSQL/Test/Cluster.pm line 3477.
# '
#     expected: ''
# Looks like you failed 1 test of 1.

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=grassquit&dt=2025-07-19%2014%3A07%3A56 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mylodon&dt=2025-07-19%2016%3A29%3A32 - master

pg_logical_slot_get_changes waits continously ... \ something wrong in the v17 branch

Fix infinite wait when reading a partially written WAL record

027_stream_regress.pl failed on mamba due to pg_isready timed out (after 1e9b5140c)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mamba&dt=2025-07-28%2007%3A46%3A26 - master

regress_log_027_stream_regress:
...
# Running: pg_isready --host /home/buildfarm/bf-data/tmp/ep8AOH4m7l --port 24781
/home/buildfarm/bf-data/tmp/ep8AOH4m7l:24781 - no response
[08:01:50.899](1505.313s) ok 2 - regression tests pass
[08:01:50.902](0.003s) ok 3 - primary alive after regression test run
[08:01:50.905](0.003s) not ok 4 - standby alive after regression test run
[08:01:50.908](0.003s)
[08:01:50.908](0.000s) #   Failed test 'standby alive after regression test run'
#   at t/027_stream_regress.pl line 104.
[08:01:50.909](0.001s) #          got: '0'
#     expected: '1'


027_stream_regress_standby_1.log:
...
2025-07-28 08:01:47.884 EDT [6985:1] [unknown] LOG:  connection received: host=[local]
2025-07-28 08:01:48.261 EDT [6985:2] [unknown] LOG:  connection authenticated: user="buildfarm" method=trust 
(/home/buildfarm/bf-data/HEAD/pgsql.build/src/test/recovery/tmp_check/t_027_stream_regress_standby_1_data/pgdata/pg_hba.conf:117)
2025-07-28 08:01:48.261 EDT [6985:3] [unknown] LOG:  connection authorized: user=buildfarm database=postgres 
application_name=027_stream_regress.pl
2025-07-28 08:01:51.552 EDT [6985:4] 027_stream_regress.pl LOG: could not send data to client: Broken pipe
2025-07-28 08:01:51.552 EDT [6985:5] 027_stream_regress.pl FATAL: connection to client lost
2025-07-28 08:01:51.552 EDT [6985:6] 027_stream_regress.pl LOG: disconnection: session time: 0:00:03.670 user=buildfarm 
database=postgres host=[local]

Improve error reporting in 027_stream_regress test \ new check failed on mamba

Handle timeout in PostgreSQL::Test::Cluster::is_alive()

002_pg_upgrade.pl failed due to instability of oid order

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hippopotamus&dt=2025-07-28%2015%3A05%3A11 - REL_18_STABLE

[17:10:08] t/002_pg_upgrade.pl ....... 
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/22 subtests 

---
regress_log_002_pg_upgrade
[17:09:56.372](2.577s) not ok 8 - dump outputs from original and restored regression databases match
[17:09:56.372](0.000s)
[17:09:56.372](0.000s) #   Failed test 'dump outputs from original and restored regression databases match'
[17:09:56.372](0.000s) #   at 
/home/buildfarm/hippopotamus/buildroot/REL_18_STABLE/pgsql.build/src/bin/pg_upgrade/../../../src/test/perl/PostgreSQL/Test/Utils.pm line 800.
[17:09:56.373](0.000s) #          got: '1'
#     expected: '0'
=== diff of 
/home/buildfarm/hippopotamus/buildroot/REL_18_STABLE/pgsql.build/src/bin/pg_upgrade/tmp_check/tmp_test_v61D/src_dump.sql_adjusted 
and 
/home/buildfarm/hippopotamus/buildroot/REL_18_STABLE/pgsql.build/src/bin/pg_upgrade/tmp_check/tmp_test_v61D/dest_dump.sql_adjusted
=== stdout ===
--- 
/home/buildfarm/hippopotamus/buildroot/REL_18_STABLE/pgsql.build/src/bin/pg_upgrade/tmp_check/tmp_test_v61D/src_dump.sql_adjusted 
2025-07-28 17:09:55.040029896 +0200
+++ 
/home/buildfarm/hippopotamus/buildroot/REL_18_STABLE/pgsql.build/src/bin/pg_upgrade/tmp_check/tmp_test_v61D/dest_dump.sql_adjusted 
2025-07-28 17:09:56.208057237 +0200
@@ -436960,14 +436960,14 @@
  ALTER TABLE public.insert_tbl
      ADD CONSTRAINT ne_insert_tbl_con CHECK (((x + z) = 1)) NOT ENFORCED;
  --
--- Name: notnull_tbl1_upg nn; Type: CONSTRAINT; Schema: public; Owner: buildfarm
+-- Name: notnull_parent_upg nn; Type: CONSTRAINT; Schema: public; Owner: buildfarm
  --
-ALTER TABLE public.notnull_tbl1_upg
+ALTER TABLE public.notnull_parent_upg
      ADD CONSTRAINT nn NOT NULL a NOT VALID;
  --
--- Name: notnull_parent_upg nn; Type: CONSTRAINT; Schema: public; Owner: buildfarm
+-- Name: notnull_tbl1_upg nn; Type: CONSTRAINT; Schema: public; Owner: buildfarm
  --
-ALTER TABLE public.notnull_parent_upg
+ALTER TABLE public.notnull_tbl1_upg
      ADD CONSTRAINT nn NOT NULL a NOT VALID;
  --
  -- Name: notnul

Test instability when pg_dump orders by OID \ hippopotamus proved need for fix

Sort dump objects independent of OIDs, for the 7 holdout object types.

024_add_drop_pub.pl might fail due to deadlock (on REL_15_STABLE)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=petalura&dt=2025-07-01%2018%3A00%3A58 - REL_15_STABLE

# Looks like your test exited with 29 just after 1.
t/024_add_drop_pub.pl ..............
Dubious, test returned 29 (wstat 7424, 0x1d00)


pgsql.build/src/test/subscription/tmp_check/log/regress_log_024_add_drop_pub
[21:01:34.406](16.501s) ok 1 - check initial data is copied to subscriber
error running SQL: 'psql:<stdin>:1: ERROR:  deadlock detected
DETAIL:  Process 219632 waits for ExclusiveLock on relation 6000 of database 0; blocked by process 218369.
Process 218369 waits for AccessShareLock on object 16387 of class 6100 of database 0; blocked by process 219632.
HINT:  See server log for query details.'
while running 'psql -XAtq -d port=14957 host=/home/bf/bf-build/petalura/tmp/bGI6HuRtfa dbname='postgres' -f - -v 
ON_ERROR_STOP=1' with sql 'ALTER SUBSCRIPTION tap_sub DROP PUBLICATION tap_pub_1' at 
/home/bf/bf-build/petalura/REL_15_STABLE/pgsql.build/../pgsql/src/test/perl/PostgreSQL/Test/Cluster.pm line 1951.


pgsql.build/src/test/subscription/tmp_check/log/024_add_drop_pub_subscriber.log
2025-07-01 21:01:32.682 CEST [218369][logical replication worker][3/6:0] LOG:  logical replication apply worker for 
subscription "tap_sub" has started
...
2025-07-01 21:01:34.771 CEST [219632][client backend][4/14:0] LOG: statement: ALTER SUBSCRIPTION tap_sub DROP 
PUBLICATION tap_pub_1
2025-07-01 21:01:37.355 CEST [219632][client backend][4/14:731] ERROR:  deadlock detected
2025-07-01 21:01:37.355 CEST [219632][client backend][4/14:731] DETAIL:  Process 219632 waits for ExclusiveLock on 
relation 6000 of database 0; blocked by process 218369.
     Process 218369 waits for AccessShareLock on object 16387 of class 6100 of database 0; blocked by process 219632.
     Process 219632: ALTER SUBSCRIPTION tap_sub DROP PUBLICATION tap_pub_1
     Process 218369: <command string not enabled>
2025-07-01 21:01:37.355 CEST [219632][client backend][4/14:731] HINT:  See server log for query details.
2025-07-01 21:01:37.355 CEST [219632][client backend][4/14:731] STATEMENT:  ALTER SUBSCRIPTION tap_sub DROP PUBLICATION 
tap_pub_1

024_add_drop_pub.pl might fail due to deadlock

Fix a deadlock during ALTER SUBSCRIPTION ... DROP PUBLICATION

module-libpq-oauthCheck fails due to missing libcurl/curl.h (after 1443b6c0e)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=snakefly&dt=2025-08-08%2016%3A55%3A07 - master

In file included from test-oauth-curl.c:13:
oauth-curl.c:18:10: fatal error: curl/curl.h: No such file or directory
   18 | #include <curl/curl.h>
      |          ^~~~~~~~~~~~~
compilation terminated.
make: *** [test-oauth-curl.o] Error

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=longfin&dt=2025-08-08%2016%3A35%3A17 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=alligator&dt=2025-08-08%2016%3A11%3A36 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bushmaster&dt=2025-08-08%2016%3A13%3A47 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=jay&dt=2025-08-08%2016%3A13%3A51 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sifaka&dt=2025-08-08%2016%3A20%3A36 - master

Re: pgsql: oauth: Add unit tests for multiplexer handling \ a couple of animals broken

Revert "oauth: Add unit tests for multiplexer handling"

pg_upgrade test fails on Windows due to difference in dumps (after 71ea0d679)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2025-08-11%2014%3A20%3A27 - REL_14_STABLE


c:\\build-farm-local\\buildroot\\REL_14_STABLE\\pgsql.build\\src\\bin\\pg_upgrade>RMDIR /s/q "c:\\build-farm-local\\buildroot\\REL_14_STABLE\\pgsql.build\\src\\bin\\pg_upgrade\\tmp_check\\data.old" 

Comparing old and new cluster dumps

Files c:/build-farm-local/buildroot/REL_14_STABLE/pgsql.build/src/bin/pg_upgrade/tmp_check/dump1.sql and c:/build-farm-local/buildroot/REL_14_STABLE/pgsql.build/src/bin/pg_upgrade/tmp_check/dump2.sql differ
dumps not identical!

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2025-08-11%2014%3A54%3A15 - REL_13_STABLE

Fix MSVC pg_upgrade test

cluster-toast-value-reuse.spec fails due to use of md5 on animals where FIPS mode enabled

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sunfish&dt=2025-08-17%2012%3A30%3A09 - master


diff -U3 /home/ec2-user/18-sunfish/buildroot/HEAD/pgsql.build/src/test/isolation/expected/cluster-toast-value-reuse.out /home/ec2-user/18-sunfish/buildroot/HEAD/pgsql.build/src/test/isolation/output_iso/results/cluster-toast-value-reuse.out
--- /home/ec2-user/18-sunfish/buildroot/HEAD/pgsql.build/src/test/isolation/expected/cluster-toast-value-reuse.out	2025-08-17 12:30:11.548145430 +0000
+++ /home/ec2-user/18-sunfish/buildroot/HEAD/pgsql.build/src/test/isolation/output_iso/results/cluster-toast-value-reuse.out	2025-08-17 12:51:22.645851344 +0000
@@ -1,29 +1,4 @@
 Parsed test spec with 2 sessions
 
 starting permutation: s1_begin s1_update s2_store_chunk_ids s2_cluster s1_commit s2_verify_chunk_ids
-step s1_begin: BEGIN;
...
+setup failed: ERROR:  could not compute MD5 hash: unsupported

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=shikra&dt=2025-08-17%2008%3A30%3A08 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=froghopper&dt=2025-08-17%2008%3A10%3A41 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gecko&dt=2025-08-17%2020%3A21%3A32 - master

pgsql: Add isolation test for TOAST value reuse during CLUSTER \ using md5() raises complaints

Remove md5() call from isolation test for CLUSTER and TOAST

XversionUpgrade-REL_16_STABLE-XXX fails due to MAINTAIN privilege added in v17 (after b61a5c4be)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-08-23%2006%3A03%3A18 - REL_17_STABLE

upgrade.crake/REL_17_STABLE/dumpdiff-REL_16_STABLE
--- /home/andrew/bf/root/upgrade.crake/REL_17_STABLE/origin-REL_16_STABLE.sql.fixed	2025-08-23 02:18:04.897882712 -0400
+++ /home/andrew/bf/root/upgrade.crake/REL_17_STABLE/converted-REL_16_STABLE-to-REL_17_STABLE.sql.fixed	2025-08-23 02:18:04.903882741 -0400
@@ -437958,13 +437958,13 @@
 --
 -- Name: DEFAULT PRIVILEGES FOR TABLES; Type: DEFAULT ACL; Schema: -; Owner: pg_read_all_settings
 --
-ALTER DEFAULT PRIVILEGES FOR ROLE pg_read_all_settings REVOKE SELECT,INSERT,REFERENCES,DELETE,TRIGGER,TRUNCATE,UPDATE ON TABLES FROM pg_read_all_settings;
-ALTER DEFAULT PRIVILEGES FOR ROLE pg_read_all_settings GRANT SELECT,REFERENCES,DELETE,TRIGGER,TRUNCATE,UPDATE ON TABLES TO pg_read_all_settings;
+ALTER DEFAULT PRIVILEGES FOR ROLE pg_read_all_settings REVOKE ALL ON TABLES FROM pg_read_all_settings;
+ALTER DEFAULT PRIVILEGES FOR ROLE pg_read_all_settings GRANT SELECT,REFERENCES,DELETE,TRIGGER,TRUNCATE,MAINTAIN,UPDATE ON TABLES TO pg_read_all_settings;
...

Test instability when pg_dump orders by OID \ TestUpgradeXversion fails

Rewrite previous commit's test for TestUpgradeXversion compatibility.

ecpg test thread/alloc hangs on sidewinder running NetBSD 9.3

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sidewinder&dt=2025-08-22%2011%3A29%3A27 - master

===================================================
timed out after 7200 secs

lastcommand:
ok 60        - thread/thread                             119 ms
ok 61        - thread/thread_implicit                    102 ms
ok 62        - thread/prep                               321 ms
--- EOF ---

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sidewinder&dt=2025-08-27%2016%3A35%3A01 - REL_18_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sidewinder&dt=2025-08-29%2012%3A35%3A01 - master

ecpg test thread/alloc hangs on sidewinder running NetBSD 9.3

sidewinder upgraded to NetBSD 10.1

035_conflicts.pl fails intermittently due to injection point not reached (after 6456c6e2c)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=scorpion&dt=2025-09-11%2001%3A17%3A25 - master

346/346 postgresql:subscription / subscription/035_conflicts                            ERROR           209.20s   (exit status 255 or signal 127 SIGinvalid)

pgsql.build/testrun/subscription/035_conflicts/log/regress_log_035_conflicts
---
[03:25:40.704](0.022s) ok 18 - publisher sees the old row
timed out waiting for match: (?^:sending publisher status request message) at /home/bf/bf-build/scorpion/HEAD/pgsql/src/test/subscription/t/035_conflicts.pl line 503.
# Postmaster PID for node "publisher" is 4059520
### Stopping node "publisher" using mode immediate

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=calliphoridae&dt=2025-09-11%2001%3A27%3A54 - master

Conflict detection for update_deleted in logical replication \ BF failure

Fix intermittent test failure introduced in 6456c6e2c4.

unsafe_tests/setconfig.sql fails due other database name in error context (after 9a71989a8)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=serinus&dt=2025-09-12%2022%3A27%3A42 - master

144/346 postgresql:unsafe_tests / unsafe_tests/regress                                  ERROR             1.42s   exit status 1

pgsql.build/testrun/unsafe_tests/regress/regression.diffs
diff -U3 /home/bf/bf-build/serinus/HEAD/pgsql/src/test/modules/unsafe_tests/expected/setconfig.out /home/bf/bf-build/serinus/HEAD/pgsql.build/testrun/unsafe_tests/regress/results/setconfig.out
--- /home/bf/bf-build/serinus/HEAD/pgsql/src/test/modules/unsafe_tests/expected/setconfig.out	2025-09-13 00:27:43.568923179 +0200
+++ /home/bf/bf-build/serinus/HEAD/pgsql.build/testrun/unsafe_tests/regress/results/setconfig.out	2025-09-13 00:30:38.067562879 +0200
@@ -66,12 +66,12 @@
 DO $$BEGIN EXECUTE format(
 	'ALTER DATABASE %I SET bogus = 0', current_catalog); END$$;
 ERROR:  unrecognized configuration parameter "bogus"
-CONTEXT:  SQL statement "ALTER DATABASE contrib_regression SET bogus = 0"
+CONTEXT:  SQL statement "ALTER DATABASE regression_unsafe_tests SET bogus = 0"
 PL/pgSQL function inline_code_block line 1 at EXECUTE
 DO $$BEGIN EXECUTE format(
 	'ALTER DATABASE %I RESET bogus', current_catalog); END$$;
 ERROR:  unrecognized configuration parameter "bogus"
-CONTEXT:  SQL statement "ALTER DATABASE contrib_regression RESET bogus"
+CONTEXT:  SQL statement "ALTER DATABASE regression_unsafe_tests RESET bogus"

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=melonworm&dt=2025-09-12%2022%3A12%3A54 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=melonworm&dt=2025-09-12%2022%3A12%3A54 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=greenfly&dt=2025-09-12%2022%3A35%3A41 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=scorpion&dt=2025-09-12%2022%3A11%3A45 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=tamandua&dt=2025-09-12%2022%3A29%3A10 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=flaviventris&dt=2025-09-12%2022%3A32%3A33 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=kestrel&dt=2025-09-12%2022%3A27%3A00 - master

pgsql: Avoid context dependency in test case added by 9a71989a8.

Avoid context dependency in test case added by 9a71989a8.

035_conflicts.pl fails due to VACUUM unreliability (after 6456c6e2c)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=tamandua&dt=2025-09-15%2007%3A52%3A08 - master

301/346 postgresql:subscription / subscription/035_conflicts                            ERROR            18.50s   exit status 1

pgsql.build/testrun/subscription/035_conflicts/log/regress_log_035_conflicts
[10:00:08.854](0.073s) not ok 24 - the deleted column is removed
[10:00:08.867](0.013s) #   Failed test 'the deleted column is removed'
#   at /home/bf/bf-build/tamandua/HEAD/pgsql/src/test/subscription/t/035_conflicts.pl line 562.

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=kestrel&dt=2025-09-15%2009%3A08%3A07 - master

Conflict detection for update_deleted in logical replication \ BF failure

Fix intermittent BF failures in 035_conflicts.

035_conflicts.pl fails due to timeout on waiting for retention (after 0d48d393d)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-09-15%2009%3A07%3A45 - master

325/330 postgresql:subscription / subscription/035_conflicts                            ERROR           674.81s   (exit status 255 or signal 127 SIGinvalid)

pgsql.build/testrun/subscription/035_conflicts/log/regress_log_035_conflicts
[11:53:38.727](0.812s) ok 19 - retention is inactive
### Reloading node "subscriber"
# Running: pg_ctl --pgdata C:\\prog\\bf\\root\\HEAD\\pgsql.build/testrun/subscription/035_conflicts\\data/t_035_conflicts_subscriber_data/pgdata reload
server signaled
timed out waiting for match: (?^:logical replication worker for subscription "tap_sub_a_b" will resume retaining the information for detecting conflicts
.*DETAIL:.* Retention is re-enabled as max_retention_duration is set to unlimited.*) at C:/prog/bf/root/HEAD/pgsql/src/test/subscription/t/035_conflicts.pl line 646.
...
[12:02:44.310](0.000s) # Looks like your test exited with 255 just after 19.

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2025-09-15%2023%3A26%3A13 - master

Conflict detection for update_deleted in logical replication \ another BF failure

Fix intermittent BF failures in 035_conflicts.

md5.sql fails on SLES 15 (FIPS) due to unexpected error message

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=goshawk&dt=2025-09-06%2005%3A20%3A05 - master

--- /home/linux1/17-goshawk/buildroot/HEAD/pgsql.build/src/test/regress/expected/md5_1.out	2025-09-06 05:20:02.146504037 +0000
+++ /home/linux1/17-goshawk/buildroot/HEAD/pgsql.build/src/test/regress/results/md5.out	2025-09-06 05:27:57.496484058 +0000
@@ -6,30 +6,30 @@
 -- this test in a separate file, it is easier to manage variant
 -- results.)
 select md5('') = 'd41d8cd98f00b204e9800998ecf8427e' AS "TRUE";
-ERROR:  could not compute MD5 hash: unsupported
+ERROR:  could not compute MD5 hash: disabled for FIPS

Allow tests to pass in OpenSSL FIPS mode \ animals running FIPS mode under SLES 15 are failing

Add regression expected-files for older OpenSSL in FIPS mode.

contrib/pgcrypto fails on SLES 15 (FIPS) due to unexpected error message

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=shoebill&dt=2025-09-16%2017%3A23%3A28 - master

--- /home/linux1/17-shoebill/buildroot/HEAD/pgsql.build/contrib/pgcrypto/expected/md5_1.out	2025-09-16 17:21:15.297302403 +0000
+++ /home/linux1/17-shoebill/buildroot/HEAD/pgsql.build/contrib/pgcrypto/results/md5.out	2025-09-16 17:33:12.347312404 +0000
@@ -2,16 +2,16 @@
 -- MD5 message digest
 --
 SELECT digest('', 'md5');
-ERROR:  Cannot use "md5": Cipher cannot be initialized
+ERROR:  Cannot use "md5": No such hash algorithm

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=shoebill&dt=2025-09-16%2017%3A10%3A34 - REL_18_STABLE

Allow tests to pass in OpenSSL FIPS mode \ animals running FIPS mode under SLES 15 are failing

Add regression expected-files for older OpenSSL in FIPS mode.

Several recovery tests fail with pg_stat_statements loaded (after ed1aad15e)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=batta&dt=2025-09-12%2002%3A05%3A01 - master

regress_log_013_crash_restart:
[02:14:34.966](0.001s) ok 6 - psql monitor died successfully after SIGQUIT
Use of uninitialized value $query in concatenation (.) or string at /home/admin/batta/buildroot/HEAD/pgsql.build/src/test/recovery/../../../src/test/perl/PostgreSQL/Test/Cluster.pm line 2758.
# Stale postmaster.pid file for node "primary": PID 2274620 no longer exists
[02:17:46.974](192.008s) # Tests were run but no plan was declared and done_testing() was not seen.

....
regress_log_022_crash_temp_files
[02:18:20.588](0.001s) ok 4 - second psql session died successfully after SIGKILL
Use of uninitialized value $query in concatenation (.) or string at /home/admin/batta/buildroot/HEAD/pgsql.build/src/test/recovery/../../../src/test/perl/PostgreSQL/Test/Cluster.pm line 2758.
# Stale postmaster.pid file for node "node_crash": PID 2278453 no longer exists
[02:21:32.608](192.020s) # Tests were run but no plan was declared and done_testing() was not seen.
[02:21:32.608](0.000s) # Looks like your test exited with 29 just after 4.

...
regress_log_041_checkpoint_at_promote
[02:26:25.654](0.000s) ok 4 - psql query died successfully after SIGKILL
Use of uninitialized value $query in concatenation (.) or string at /home/admin/batta/buildroot/HEAD/pgsql.build/src/test/recovery/../../../src/test/perl/PostgreSQL/Test/Cluster.pm line 2758.
# No postmaster PID for node "master"
# Stale postmaster.pid file for node "standby1": PID 2312820 no longer exists
[02:29:38.462](192.809s) # Tests were run but no plan was declared and done_testing() was not seen.
[02:29:38.462](0.000s) # Looks like your test exited with 29 just after 4.

Move named LWLock tranche requests to shared memory \ batta failing

Fix re-initialization of LWLock-related shared memory.

stats.spec fails due to zero time diff on Hurd animal fruitcrow

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fruitcrow&dt=2025-09-13%2008%3A04%3A05 - REL_17_STABLE

diff -U3 /home/demo/client-code-REL_19_1/buildroot/REL_17_STABLE/pgsql.build/src/test/isolation/expected/stats_1.out /home/demo/client-code-REL_19_1/buildroot/REL_17_STABLE/pgsql.build/src/test/isolation/output_iso/results/stats.out
--- /home/demo/client-code-REL_19_1/buildroot/REL_17_STABLE/pgsql.build/src/test/isolation/expected/stats_1.out	2025-09-13 09:04:12.000000000 +0100
+++ /home/demo/client-code-REL_19_1/buildroot/REL_17_STABLE/pgsql.build/src/test/isolation/output_iso/results/stats.out	2025-09-13 09:20:44.000000000 +0100
@@ -1278,7 +1278,7 @@
 
 name           |pg_stat_get_function_calls|total_above_zero|self_above_zero
 ---------------+--------------------------+----------------+---------------
-test_stat_func2|                         1|t               |t              
+test_stat_func2|                         1|f               |f              
 (1 row)
 
 step s1_func_stats:

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fruitcrow&dt=2025-09-15%2021%3A06%3A17 - REL_17_STABLE

Also stats.spec failed due to zero function duration

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2025-07-22%2011%3A02%3A15 - master

diff --strip-trailing-cr -U3 c:/build-farm-local/buildroot/HEAD/pgsql/src/test/isolation/expected/stats.out c:/build-farm-local/buildroot/HEAD/pgsql.build/testrun/isolation/isolation/results/stats.out
--- c:/build-farm-local/buildroot/HEAD/pgsql/src/test/isolation/expected/stats.out	2025-07-22 20:08:30 +0900
+++ c:/build-farm-local/buildroot/HEAD/pgsql.build/testrun/isolation/isolation/results/stats.out	2025-07-22 20:30:47 +0900
@@ -3729,7 +3729,7 @@
 
 name          |pg_stat_get_function_calls|total_above_zero|self_above_zero
 --------------+--------------------------+----------------+---------------
-test_stat_func|                         1|t               |t              
+test_stat_func|                         1|f               |f              
 (1 row)
 
 step s1_commit: COMMIT;

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2025-08-03%2011%3A05%3A03 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2025-08-05%2011%3A03%3A59 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2025-08-15%2011%3A03%3A45 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2025-08-19%2013%3A56%3A17 - REL_15_STABLE

GNU/Hurd portability patches \ total elapsed time is zero

Add minimal sleep to stats isolation test functions.

skink fails to create db due to valgrind-detected errors (after 5e8998592)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-10-08%2022%3A45%3A57 - master

\342\226\266 1/1 - test_setup                                110 ms FAIL  
...
2025-10-09 00:47:44.179 CEST client backend[806638] [unknown] FATAL:  the database system is starting up
2025-10-09 00:47:44.180 CEST postmaster[805680] LOG:  database system is ready to accept connections
==806996== VALGRINDERROR-BEGIN
==806996== Invalid read of size 8
==806996==    at 0x57951C: RelationCopyStorageUsingBuffer (bufmgr.c:5221)
==806996==    by 0x579679: CreateAndCopyRelationData (bufmgr.c:5275)
==806996==    by 0x32551D: CreateDatabaseUsingWalLog (dbcommands.c:217)
==806996==    by 0x32A361: createdb (dbcommands.c:1549)
==806996==    by 0x5C0501: standard_ProcessUtility (utility.c:772)
==806996==    by 0x5C08F8: ProcessUtility (utility.c:523)
==806996==    by 0x5BCEE8: PortalRunUtility (pquery.c:1153)
==806996==    by 0x5BD1D5: PortalRunMulti (pquery.c:1310)
==806996==    by 0x5BD52B: PortalRun (pquery.c:788)
==806996==    by 0x5B8FB9: exec_simple_query (postgres.c:1279)
==806996==    by 0x5BB603: PostgresMain (postgres.c:4775)
==806996==    by 0x5B3EC9: BackendMain (backend_startup.c:124)
==806996==  Address 0x93e2000 is in a rw- anonymous segment
==806996== 
==806996== VALGRINDERROR-END
...

ReadRecentBuffer() doesn't scale well \ kink is red due to bufmgr changes

bufmgr: Fix valgrind checking for buffers pinned in StrategyGetBuffer()

009_log_temp_files.pl fails with increased log_error_verbosity (after 76bba0331)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-10-16%2001%3A23%3A06 - master


#   Failed test 'unnamed portal'
#   at t/009_log_temp_files.pl line 40.

#   Failed test 'bind and implicit transaction, temporary file removed'
#   at t/009_log_temp_files.pl line 51.

#   Failed test 'named portal'
#   at t/009_log_temp_files.pl line 65.
...
[02:18:28] t/009_log_temp_files.pl ......... 
Dubious, test returned 8 (wstat 2048, 0x800)
Failed 8/10 subtests

BUG temporary file usage report with extended protocol and unnamed portals \ prion failed because of log_error_verbosity verbose

Override log_error_verbosity to "default" in test 009_log_temp_files

pg_prewarm/001_basic.pl fails on Windows due to authentication failure (after 208927e65)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-10-18%2017%3A15%3A33 - REL_16_STABLE

200/263 postgresql:pg_prewarm / pg_prewarm/001_basic                              ERROR            44.95s   exit status 2


---
pgsql.build/testrun/pg_prewarm/001_basic/log/regress_log_001_basic
...
[19:09:03.922](1.124s) not ok 4 - pg_prewarm failed as expected
[19:09:03.923](0.001s) #   Failed test 'pg_prewarm failed as expected'
#   at C:/prog/bf/root/REL_16_STABLE/pgsql/contrib/pg_prewarm/t/001_basic.pl line 52.
[19:09:04.563](0.640s) not ok 5 - pg_prewarm failed as expected
[19:09:04.564](0.001s) #   Failed test 'pg_prewarm failed as expected'
#   at C:/prog/bf/root/REL_16_STABLE/pgsql/contrib/pg_prewarm/t/001_basic.pl line 57.
connection error: 'psql: error: connection to server at "127.0.0.1", port 17464 failed: FATAL:  SSPI authentication failed for user "test_user"'
while running 'psql -XAtq -d port=17464 host=127.0.0.1 dbname='postgres' -f - -v ON_ERROR_STOP=1 --username test_user' at C:/prog/bf/root/REL_16_STABLE/pgsql/src/test/perl/PostgreSQL/Test/Cluster.pm line 1958.
# Postmaster PID for node "main" is 2596
### Stopping node "main" using mode immediate
# Running: pg_ctl -D C:\\prog\\bf\\root\\REL_16_STABLE\\pgsql.build/testrun/pg_prewarm/001_basic\\data/t_001_basic_main_data/pgdata -m immediate stop
waiting for server to shut down.... done
server stopped
# No postmaster PID for node "main"

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-10-18%2019%3A36%3A16 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-10-18%2021%3A48%3A25 - REL_18_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-10-17%2018%3A34%3A10 - master

pgsql: Allow role created by new test to log in on Windows.

Allow role created by new test to log in on Windows.

006_pg_dump_compress.pl fails on mamba (after 20ec99589)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mamba&dt=2025-10-17%2006%3A09%3A19 - master

#   Failed test 'compression_gzip_dir: pg_restore runs'
#   at t/006_pg_dump_compress.pl line 545.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 2 just after 16.
[03:31:24] t/006_pg_dump_compress.pl ..... 
Dubious, test returned 2 (wstat 512, 0x200)
Failed 1/16 subtests

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mamba&dt=2025-10-18%2006%3A14%3A42 - master

gzgetc() is hazardous to your health

Don't rely on zlib's gzgetc() macro.

groupingsets.sql fails on REL_18_STABLE due to incorrect line expected (after 40c242830)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gokiburi&dt=2025-10-21%2006%3A48%3A05 - REL_18_STABLE

...
# 1 of 228 tests failed.
...
--- /home/admin/gokiburi/buildroot/REL_18_STABLE/pgsql.build/src/test/regress/expected/groupingsets.out	2025-10-21 06:48:06.810240488 +0000
+++ /home/admin/gokiburi/buildroot/REL_18_STABLE/pgsql.build/src/test/regress/results/groupingsets.out	2025-10-21 06:48:31.506024610 +0000
@@ -935,15 +935,14 @@
 -- test pushdown of degenerate HAVING clause
 explain (costs off)
 select count(*) from gstest2 group by grouping sets (()) having false;
-            QUERY PLAN             
------------------------------------
+           QUERY PLAN           
+--------------------------------
  Aggregate
    Group Key: ()
    Filter: false
    ->  Result
-         Replaces: Scan on gstest2
          One-Time Filter: false
-(6 rows)
+(5 rows)
...

Inconsistent Behavior of GROUP BY ROLLUP in v17 vs master \ a mistake in the test case for v18

Fix test case from 40c242830

001_ssltests.pl fails on mamba due to 32-bit Perl used (after 7d129ba54)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mamba&dt=2025-10-20%2006%3A14%3A34 - master

# +++ tap check in src/test/ssl +++

#   Failed test 'pg_stat_ssl with client certificate: matches'
#   at t/001_ssltests.pl line 777.
#                   'pid,ssl,version,cipher,bits,client_dn,client_serial,issuer_dn
# 6847,t,TLSv1.3,TLS_AES_256_GCM_SHA384,256,/CN=ssltestuser,2315702411956921344,/CN=Test CA for PostgreSQL SSL regression test client certs
# (1 row)
# '
#     doesn't match '(?^mx:^pid,ssl,version,cipher,bits,client_dn,client_serial,issuer_dn\\r?\\n
# 				^\\d+,t,TLSv[\\d.]+,[\\w-]+,\\d+,/?CN=ssltestuser,serial=2023071316352400
# ,/?CN\\=Test\\ CA\\ for\\ PostgreSQL\\ SSL\\ regression\\ test\\ client\\ certs\\r?$)'
# Looks like you failed 1 test of 247.
[05:05:25] t/001_ssltests.pl ..

pgsql: Fix thinko in commit 7d129ba54.

Fix thinko in commit 7d129ba54.

rhinoceros fails at stage ssl_passphrase_callbackCheck after adding sepgsql to PG_TEST_EXTRA

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rhinoceros&dt=2025-10-26%2004%3A52%3A08 - REL_15_STABLE

Log for system rhinoceros, Stage ssl_passphrase_callback-check
...
make -j1  checkprep >>'/opt/src/pgsql-git/build-farm-root/REL_15_STABLE/pgsql.build'/tmp_install/log/install.log 2>&1
make: *** [temp-install] Error 2

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rhinoceros&dt=2025-10-26%2005%3A13%3A46 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rhinoceros&dt=2025-10-26%2005%3A37%3A39 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rhinoceros&dt=2025-10-27%2007%3A52%3A11 - REL_17_STABLE

Also, rhinoceros fails at stage ModulesCheck after adding sepgsql to PG_TEST_EXTRA

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rhinoceros&dt=2025-10-26%2006%3A00%3A44 - REL_18_STABLE

# +++ tap check in src/test/modules/oauth_validator +++
Can't locate JSON/PP.pm in @INC (@INC contains: /opt/src/pgsql-git/build-farm-root/REL_18_STABLE/pgsql.build/src/test/modules/oauth_validator/../../../../src/test/perl /opt/src/pgsql-git/build-farm-root/REL_18_STABLE/pgsql.build/src/test/modules/oauth_validator /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at t/001_server.pl line 12.
BEGIN failed--compilation aborted at t/001_server.pl line 12.
t/001_server.pl .. 
Dubious, test returned 2 (wstat 512, 0x200)

contrib/sepgsql regression tests have been broken for months \ PG_TEST_EXTRA to include "sepgsql"

buildfarm client updated

brin/01_workitems.pl failed on Valgrind animal on attempt to pop non-existent snapshot (after a95e3d84c)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-11-04%2012%3A56%3A09 - master

305/354 postgresql:brin / brin/01_workitems                                             ERROR             39.31s   exit status 29

---
pgsql.build/testrun/brin/01_workitems/log/01_workitems_tango.log
2025-11-04 16:44:47.792 CET [2118443][autovacuum worker][108/6:0] ERROR:  canceling autovacuum task
2025-11-04 16:44:47.792 CET [2118443][autovacuum worker][108/6:0] CONTEXT:  processing work entry for relation "postgres.public.brin_packdate_idx"
2025-11-04 16:44:47.810 CET [2118078][autovacuum worker][103/10:0] LOG:  process 2118078 acquired ShareUpdateExclusiveLock on relation 16436 of database 5 after 1414.103 ms
2025-11-04 16:44:47.810 CET [2118078][autovacuum worker][103/10:0] CONTEXT:  waiting for ShareUpdateExclusiveLock on relation 16436 of database 5
==2118443== VALGRINDERROR-BEGIN
==2118443== Invalid read of size 8
==2118443==    at 0x4634F39: PopActiveSnapshot (snapmgr.c:777)
==2118443==    by 0x43F693F: do_autovacuum (autovacuum.c:2561)
==2118443==    by 0x43F6E2B: AutoVacWorkerMain (autovacuum.c:1604)
==2118443==    by 0x43FA9C9: postmaster_child_launch (launch_backend.c:268)
==2118443==    by 0x43FDD9E: StartChildProcess (postmaster.c:3991)
==2118443==    by 0x43FE008: StartAutovacuumWorker (postmaster.c:4055)
==2118443==    by 0x43FF078: process_pm_pmsignal (postmaster.c:3812)
==2118443==    by 0x43FF93C: ServerLoop (postmaster.c:1706)
==2118443==    by 0x4401080: PostmasterMain (postmaster.c:1403)
==2118443==    by 0x432A55F: main (main.c:231)
==2118443==  Address 0x10 is not stack'd, malloc'd or (recently) free'd
==2118443== 
==2118443== VALGRINDERROR-END
...
2025-11-04 16:44:48.799 CET [2109989][postmaster][:0] LOG:  autovacuum worker (PID 2118443) was terminated by signal 11: Segmentation fault
2025-11-04 16:44:48.799 CET [2109989][postmaster][:0] DETAIL:  Failed process was running: autovacuum: BRIN summarize public.brin_packdate_idx 1

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-11-04%2016%3A08%3A08 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-11-04%2019%3A18%3A56 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-11-04%2016%3A16%3A38 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-11-04%2019%3A31%3A42 - REL_17_STABLE

BRIN autosummarization lacking a snapshot \ skink failed

Fix snapshot handling bug in recent BRIN fix

004_timeline_switch.pl failed on Windows animal drongo due to timing (after 17b2d5ec7)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-11-05%2006%3A06%3A57 - master

  8/338 postgresql:recovery / recovery/004_timeline_switch                              ERROR           106.96s   exit status 1

---
pgsql.build/testrun/recovery/004_timeline_switch/log/regress_log_004_timeline_switch
[07:31:07.655](6.394s) ok 2 - check content of standby 2
[07:31:07.657](0.002s) not ok 3 - WAL receiver should not be stopped across timeline jumps
[07:31:07.658](0.001s) #   Failed test 'WAL receiver should not be stopped across timeline jumps'
#   at C:/prog/bf/root/HEAD/pgsql/src/test/recovery/t/004_timeline_switch.pl line 73.

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-11-05%2003%3A50%3A50 - REL_18_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-11-05%2001%3A45%3A13 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-11-04%2023%3A30%3A47 - REL_16_STABLE

Fix fragile walreceiver test

Fix timing-dependent failure in recovery test 004_timeline_switch

036_sequences.pl fails on prion due to increased log_error_verbosity (after 5509055d6)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-11-05%2010%3A30%3A15 - master

# Looks like your test exited with 255 just after 8.
[11:35:21] t/036_sequences.pl ................. 
Dubious, test returned 255 (wstat 65280, 0xff00)

---
pgsql.build/src/test/subscription/tmp_check/log/regress_log_036_sequences
[11:32:20.572](0.162s) ok 8 - REFRESH PUBLICATION will not sync newly published sequence with copy_data as false
timed out waiting for match: (?^:WARNING: ( [A-Z0-9]+:)? mismatched or renamed sequence on subscriber \\("public.regress_s4"\\)\\n.*ERROR: ( [A-Z0-9]+:)? logical replication sequence synchronization failed for subscription "regress_seq_sub") at t/036_sequences.pl line 203.

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-11-05%2021%3A03%3A31 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-11-06%2007%3A00%3A06 - master

Logical Replication of sequences \ test failed on prion due to non-default log_error_verbosity

Fix few issues in commit 5509055d69.

001_sepgsql.pl fails on rhinoceros in v18+ due to sepgsql_regression_test_mode turned off

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rhinoceros&dt=2025-10-29%2021%3A36%3A40 - master

# +++ tap check in contrib/sepgsql +++
# 
# The SELinux boolean 'sepgsql_regression_test_mode' must be
# turned on in order to enable the rules necessary to run the
# regression tests.
# 
# You can turn on this variable using the following commands:
# 
#   $ sudo setsebool sepgsql_regression_test_mode on
# 
# For security reasons, it is suggested that you turn off this
# variable when regression testing is complete and the associated
# rules are no longer needed.
[15:04:03] t/001_sepgsql.pl .. 
Dubious, test returned 255 (wstat 65280, 0xff00)

contrib/sepgsql regression tests have been broken for months \ the boolean is not flipped for tap tests

contrib/sepgsql regression tests have been broken for months \ back to the original configuration

027_stream_regress.pl fails on riscv64 animal due to IO in wrong state

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=greenfly&dt=2025-10-09%2000%3A06%3A03 - master

287/344 postgresql:recovery / recovery/027_stream_regress                               ERROR          1406.65s   exit status 1
...
# 1 of 230 tests failed.
...
--- /home/gburd/build/HEAD/pgsql/src/test/regress/expected/tsearch.out	2025-10-09 00:06:10.612959611 +0000
+++ /home/gburd/build/HEAD/pgsql.build/testrun/recovery/027_stream_regress/data/results/tsearch.out	2025-10-09 00:27:46.697588198 +0000
@@ -163,11 +163,7 @@
 (1 row)
 
 SELECT count(*) FROM test_tsvector WHERE a @@ '!qe <2> qt';
- count 
--------
-     6
-(1 row)
-
+ERROR:  IO in wrong state: 0
 SELECT count(*) FROM test_tsvector WHERE a @@ '!(pl <-> yh)';
  count

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=greenfly&dt=2025-10-17%2009%3A06%3A04 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=greenfly&dt=2025-10-20%2018%3A06%3A04 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=greenfly&dt=2025-10-27%2004%3A06%3A03 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=greenfly&dt=2025-11-06%2010%3A55%3A27 - master

Also 027_stream_regress.pl timed out on riscv64 animal greenfly

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=greenfly&dt=2025-10-08%2017%3A06%3A03 - master

ok 159       + collate.windows.win1252                   275 ms
death by signal at /home/gburd/build/HEAD/pgsql/src/test/perl/PostgreSQL/Test/Cluster.pm line 181.

---
pgsql.build/testrun/recovery/027_stream_regress/log/027_stream_regress_primary.log
2025-10-08 17:39:06.444 UTC [644065:223] pg_regress/select_parallel DETAIL:  prepare: PREPARE pstmt(text, int[]) AS SELECT * FROM fooarr WHERE f1 = $1 AND f2 = $2;
2025-10-08 17:43:46.704 UTC [597231:40] LOG:  checkpoint starting: time
2025-10-08 17:43:46.724 UTC [597231:41] LOG:  checkpoint complete: wrote 0 buffers (0.0%), wrote 2 SLRU buffers; 0 WAL file(s) added, 0 removed, 1 recycled; write=0.001 s, sync=0.001 s, total=0.020 s; sync files=0, longest=0.000 s, average=0.000 s; distance=17569 kB, estimate=56250 kB; lsn=0/111B0C60, redo lsn=0/111B0B58
2025-10-08 18:17:47.975 UTC [597207:369] LOG:  received immediate shutdown request
2025-10-08 18:17:47.976 UTC [644065:224] pg_regress/select_parallel LOG:  could not send data to client: Broken pipe
2025-10-08 18:17:47.976 UTC [644065:225] pg_regress/select_parallel STATEMENT:  EXECUTE pstmt('1', make_some_array(1,2))

IO in wrong state on riscv64

Fix generic read and write barriers for Clang.

040_standby_failover_slots_sync.pl fails due to replication slot not released (after 76b78721c)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=scorpion&dt=2025-11-25%2007%3A38%3A19 - master

[08:43:07.960](0.158s) ok 28 - subscriber1 gets data from primary after standby1 is removed from the synchronized_standby_slots list
### Reloading node "publisher"
# Running: pg_ctl --pgdata /home/bf/bf-build/scorpion/HEAD/pgsql.build/testrun/recovery/040_standby_failover_slots_sync/data/t_040_standby_failover_slots_sync_publisher_data/pgdata reload
server signaled
### Starting node "standby1"
# Running: pg_ctl --wait --pgdata /home/bf/bf-build/scorpion/HEAD/pgsql.build/testrun/recovery/040_standby_failover_slots_sync/data/t_040_standby_failover_slots_sync_standby1_data/pgdata --log /home/bf/bf-build/scorpion/HEAD/pgsql.build/testrun/recovery/040_standby_failover_slots_sync/log/040_standby_failover_slots_sync_standby1.log --options --cluster-name=standby1 start
waiting for server to start.... done
server started
# Postmaster PID for node "standby1" is 1519619
Waiting for replication conn standby1's replay_lsn to pass 0/060051E0 on publisher
[08:47:13.151](245.190s) # poll_query_until timed out executing this query:
# SELECT '0/060051E0' <= replay_lsn AND state = 'streaming'
#          FROM pg_catalog.pg_stat_replication
#          WHERE application_name IN ('standby1', 'walreceiver')
# expecting this output:
# t
# last actual query output:
# 
# with stderr:
[08:47:13.167](0.017s) # Last pg_stat_replication contents:
# 1519462|10|bf|regress_mysub1|||-1|2025-11-25 08:43:07.777794+01||streaming|0/060051E0|0/060051E0|0/060051E0|0/060051E0||||0|async|2025-11-25 08:47:09.233864+01
# 1515586|10|bf|standby2|||-1|2025-11-25 08:43:02.492722+01||streaming|0/06005218|0/06005218|0/06005218|0/06005218||||0|async|2025-11-25 08:47:09.491287+01
# 1517279|10|bf|regress_mysub2|||-1|2025-11-25 08:43:04.808264+01||streaming|0/06005218|0/06005218|0/06005218|0/06005218||||0|async|2025-11-25 08:47:10.173934+01
timed out waiting for catchup at /home/bf/bf-build/scorpion/HEAD/pgsql/src/test/recovery/t/040_standby_failover_slots_sync.pl line 932.

---
pgsql.build/testrun/recovery/040_standby_failover_slots_sync/log/040_standby_failover_slots_sync_standby1.log
TRAP: failed Assert("MyReplicationSlot == NULL"), File: "../pgsql/src/backend/replication/slot.c", Line: 633, PID: 1519654
postgres: standby1: slotsync worker (ExceptionalCondition+0x83) [0x55cbaebfb1f6]
postgres: standby1: slotsync worker (ReplicationSlotAcquire+0x6b) [0x55cbaea0aeea]
postgres: standby1: slotsync worker (+0x459fc7) [0x55cbaea31fc7]
postgres: standby1: slotsync worker (ReplSlotSyncWorkerMain+0x594) [0x55cbaea32f93]
postgres: standby1: slotsync worker (postmaster_child_launch+0x12d) [0x55cbae9ec967]
postgres: standby1: slotsync worker (+0x416fe4) [0x55cbae9eefe4]
postgres: standby1: slotsync worker (+0x419423) [0x55cbae9f1423]
postgres: standby1: slotsync worker (PostmasterMain+0x14c7) [0x55cbae9f2c5b]
postgres: standby1: slotsync worker (main+0x7f0) [0x55cbae92393e]
/lib/x86_64-linux-gnu/libc.so.6(+0x29ca8) [0x7fd1edd69ca8]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7fd1edd69d65]
postgres: standby1: slotsync worker (_start+0x21) [0x55cbae6bf1a1]
2025-11-25 08:43:08.114 CET [1519619][postmaster][:0] LOG:  slot sync worker process (PID 1519654) was terminated by signal 6: Aborted

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=olingo&dt=2025-11-25%2007%3A37%3A09 - master

How can end users know the cause of LR slot sync delays? \ BF failure

Fix a BF failure caused by commit 76b78721ca.

040_standby_failover_slots_sync.pl fails due to newer catalog xmin on standby (after 76b78721c)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=scorpion&dt=2025-11-25%2009%3A03%3A17 - master

288/357 postgresql:recovery / recovery/040_standby_failover_slots_sync                  ERROR           190.18s   (exit status 255 or signal 127 SIGinvalid)

---
regress_log_040_standby_failover_slots_sync
[10:06:11.730](1.327s) ok 11 - check slot sync skip count increments
Waiting for replication conn standby1's replay_lsn to pass 0/030163A8 on publisher
done
timed out waiting for match: (?^:newly created replication slot \\"lsub1_slot\\" is sync-ready now) at /home/bf/bf-build/scorpion/HEAD/pgsql/src/test/recovery/t/040_standby_failover_slots_sync.pl line 278.
# Postmaster PID for node "publisher" is 2611564


---
040_standby_failover_slots_sync_standby1.log
2025-11-25 10:06:11.669 CET [2616754][slotsync worker][10/3:0] LOG:  could not synchronize replication slot "lsub1_slot"
2025-11-25 10:06:11.669 CET [2616754][slotsync worker][10/3:0] DETAIL:  Synchronization could lead to data loss, because the remote slot needs WAL at LSN 0/03000098 and catalog xmin 757, but the standby has LSN 0/03000098 and catalog xmin 758.

How can end users know the cause of LR slot sync delays? \ still failures after 3df4df53b06

Fix test failure caused by commit 76b78721ca.

numeric.sql fails under Valgrind due to accessing uninitialized value (after 0ca3b1697)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-11-27%2002%3A17%3A35 - master

1/1 postgresql:regress / regress/regress ERROR             73.22s   exit status 1
...
==2463062== VALGRINDERROR-BEGIN
==2463062== Conditional jump or move depends on uninitialised value(s)
==2463062==    at 0x418484C: table_block_parallelscan_startblock_init (tableam.c:501)
==2463062==    by 0x4130FB2: heap_scan_stream_read_next_parallel (heapam.c:259)
==2463062==    by 0x446D9F1: read_stream_get_block (read_stream.c:197)
==2463062==    by 0x446E303: read_stream_look_ahead (read_stream.c:463)
==2463062==    by 0x446E898: read_stream_next_buffer (read_stream.c:890)
==2463062==    by 0x4131589: heap_fetch_next_buffer (heapam.c:677)
==2463062==    by 0x4139C45: heapgettup_pagemode (heapam.c:1039)
==2463062==    by 0x413A056: heap_getnextslot (heapam.c:1404)
==2463062==    by 0x42FD7F8: table_scan_getnextslot (tableam.h:1036)
==2463062==    by 0x42FD895: SeqNext (nodeSeqscan.c:81)
==2463062==    by 0x42FDC6E: ExecScanFetch (execScan.h:134)
==2463062==    by 0x42FDC6E: ExecScanExtended (execScan.h:178)
==2463062==    by 0x42FDC6E: ExecSeqScan (nodeSeqscan.c:118)
==2463062==    by 0x42CB3C1: ExecProcNodeFirst (execProcnode.c:469)

**2463062** Valgrind detected 22 error(s) during execution of "SELECT trim_scale(variance(a) * 1e1000) FROM num_variance;"
**2463062** Valgrind detected 22 error(s) during execution of "SELECT variance(a) FROM num_variance;"

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-11-27%2003%3A21%3A21 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-11-27%2007%3A08%3A52 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-11-27%2012%3A38%3A18 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-11-27%2018%3A16%3A34 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-11-27%2022%3A48%3A27 - master

Support tid range scan in parallel? \ This seems to have caused issues on skink

Fix possibly uninitialized HeapScanDesc.rs_startblock

New test index-concurrently-upsert.spec timed out on prion (after bc32a12e0)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-11-24%2016%3A23%3A06 - master

ok 3         - syscache-update-pruned                   7947 ms
---- hang ----

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-11-25%2007%3A05%3A13 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-11-25%2015%3A13%3A04 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-11-26%2001%3A03%3A11 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-11-26%2010%3A49%3A00 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-11-26%2021%3A53%3A13 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-11-27%2008%3A51%3A21 - master

Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY \ one more problem with the new test

Fix new test for CATCACHE_FORCE_RELEASE builds

index-concurrently-upsert.spec fails with *CACHE_FORCE_RELEASE (after 5dee7a603)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-12-02%2015%3A54%3A13 - master

diff -U3 /home/ec2-user/bf/root/HEAD/pgsql/src/test/modules/injection_points/expected/index-concurrently-upsert.out /home/ec2-user/bf/root/HEAD/pgsql.build/src/test/modules/injection_points/output_iso/results/index-concurrently-upsert.out
--- /home/ec2-user/bf/root/HEAD/pgsql/src/test/modules/injection_points/expected/index-concurrently-upsert.out	2025-12-02 15:53:07.591055886 +0000
+++ /home/ec2-user/bf/root/HEAD/pgsql.build/src/test/modules/injection_points/output_iso/results/index-concurrently-upsert.out	2025-12-02 16:01:06.534073815 +0000
@@ -18,12 +18,7 @@
 
 step s1_attach_invalidate_catalog_snapshot: 
 	SELECT injection_points_attach('invalidate-catalog-snapshot-end', 'wait');
-
-injection_points_attach
------------------------
-                       
-(1 row)
-
+ <waiting ...>
 step s4_wakeup_s1_setup: 
 	SELECT CASE WHEN
 			(SELECT pid FROM pg_stat_activity
...

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-12-02%2016%3A33%3A05 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-12-03%2002%3A03%3A57 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-12-03%2003%3A43%3A05 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-12-03%2008%3A03%3A06 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-12-03%2009%3A03%3A05 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-12-03%2009%3A43%3A06 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-12-03%2013%3A53%3A05 - master

Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY \ prion has been failing since 5dee7a603

Put back alternative-output expected files

reindex-concurrently-*.spec tests fail depending on timing

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-11-25%2021%3A55%3A00 - master

129/357 postgresql:injection_points / injection_points/isolation                        ERROR            253.80s   exit status 1
...
diff -U3 /home/bf/bf-build/skink-master/HEAD/pgsql/src/test/modules/injection_points/expected/reindex-concurrently-upsert.out /home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/injection_points/isolation/results/reindex-concurrently-upsert.out
--- /home/bf/bf-build/skink-master/HEAD/pgsql/src/test/modules/injection_points/expected/reindex-concurrently-upsert.out	2025-11-24 17:28:11.027087212 +0100
+++ /home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/injection_points/isolation/results/reindex-concurrently-upsert.out	2025-11-26 00:03:05.522320081 +0100
@@ -205,7 +205,6 @@
                        
 (1 row)
 
-step s1_start_upsert: <... completed>
 step s4_wakeup_to_set_dead: 
 	SELECT injection_points_detach('reindex-relation-concurrently-before-set-dead');
 	SELECT injection_points_wakeup('reindex-relation-concurrently-before-set-dead');
@@ -220,6 +219,7 @@
                        
 (1 row)
 
+step s1_start_upsert: <... completed>
 step s4_wakeup_s2: 
 	SELECT injection_points_detach('exec-insert-before-insert-speculative');
 	SELECT injection_points_wakeup('exec-insert-before-insert-speculative');

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=adder&dt=2025-12-02%2008%3A48%3A24 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=adder&dt=2025-12-03%2009%3A23%3A08 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=flaviventris&dt=2025-12-04%2017%3A28%3A20 - master

Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY \ The "partitioned" test failed

Stabilize tests some more

index-concurrently-upsert.spec fails due to unexpected notice

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-11-29%2021%3A51%3A13 - master

127/357 postgresql:injection_points / injection_points/isolation                        ERROR            267.58s   exit status 1

pgsql.build/testrun/injection_points/isolation/regression.diffs
---
diff -U3 /home/bf/bf-build/skink-master/HEAD/pgsql/src/test/modules/injection_points/expected/index-concurrently-upsert.out /home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/injection_points/isolation/results/index-concurrently-upsert.out
--- /home/bf/bf-build/skink-master/HEAD/pgsql/src/test/modules/injection_points/expected/index-concurrently-upsert.out	2025-11-27 13:38:19.513528475 +0100
+++ /home/bf/bf-build/skink-master/HEAD/pgsql.build/testrun/injection_points/isolation/results/index-concurrently-upsert.out	2025-11-30 00:10:01.697938769 +0100
@@ -107,6 +107,7 @@
 (1 row)
 
 s1: NOTICE:  notice triggered for injection point pre-invalidate-catalog-snapshot-end
+s1: NOTICE:  notice triggered for injection point pre-invalidate-catalog-snapshot-end
 step s1_start_upsert: <... completed>

Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY \ failures from skink

Avoid use of NOTICE to wait for snapshot invalidation

XversionUpgrade-REL_18_STABLE-HEAD fails on attempt to upgrade injection_points (after d52c24b0f)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-12-08%2003%3A47%3A03 - master

upgrade.crake/HEAD/inst/REL_18_STABLE-20251207T230130.153/log/pg_upgrade_internal.log
Restoring database schemas in the new cluster                 
*failure*
Consult the last few lines of "/home/andrew/bf/root/upgrade.crake/HEAD/inst/REL_18_STABLE-upgrade/pg_upgrade_output.d/20251207T230130.153/log/pg_upgrade_dump_55056.log" for
the probable cause of the failure.

---
upgrade.crake/HEAD/inst/REL_18_STABLE-20251207T230130.153/log/pg_upgrade_dump_55056.log
pg_restore: creating EXTENSION "injection_points"
pg_restore: creating COMMENT "EXTENSION "injection_points""
pg_restore: creating FUNCTION "public.injection_points_attach("text", "text")"
pg_restore: creating FUNCTION "public.injection_points_cached("text", "text")"
pg_restore: creating FUNCTION "public.injection_points_detach("text")"
pg_restore: creating FUNCTION "public.injection_points_load("text")"
pg_restore: creating FUNCTION "public.injection_points_run("text", "text")"
pg_restore: creating FUNCTION "public.injection_points_set_local()"
pg_restore: creating FUNCTION "public.injection_points_stats_drop()"
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 230; 1255 55098 FUNCTION injection_points_stats_drop() buildfarm
pg_restore: error: could not execute query: ERROR:  could not find function "injection_points_stats_drop" in file "/home/andrew/bf/root/saves.crake/HEAD/lib/postgresql/injection_points.so"
Command was: CREATE FUNCTION "public"."injection_points_stats_drop"() RETURNS "void"
    LANGUAGE "c" STRICT
    AS '$libdir/injection_points', 'injection_points_stats_drop';

pgsql: injection_points: Remove portions related to custom pgstats \ crake is unhappy with this

Fix failures with cross-version pg_upgrade tests

trilobite and avocet fail due to 4 hours timeout

(trilobite and avocet run tests with -DCLOBBER_CACHE_ALWAYS)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=avocet&dt=2025-12-02%2004%3A10%3A38 - master

===================================================
timed out after 14400 secs

increased duration of stats_ext tests with -DCLOBBER_CACHE_ALWAYS

Related, but not a final fix:
Make stats_ext test faster under cache-clobbering test conditions.

'wait_timeout' => undef changed to 'wait_timeout' => 0 in the buildfarm client configuration

nls.sql fails on a few animals due to es_ES.UTF-8 locale not accepted (after 8c498479d)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=akepa&dt=2025-12-14%2016%3A56%3A05 - master

diff -U3 /home/buildfarm/build-farm-17/buildroot/HEAD/pgsql/src/test/regress/expected/nls_1.out /home/buildfarm/build-farm-17/buildroot/HEAD/pgsql.build/testrun/regress/regress/results/nls.out
--- /home/buildfarm/build-farm-17/buildroot/HEAD/pgsql/src/test/regress/expected/nls_1.out	2025-12-14 11:56:07.354025201 -0500
+++ /home/buildfarm/build-farm-17/buildroot/HEAD/pgsql.build/testrun/regress/regress/results/nls.out	2025-12-14 11:56:30.013541705 -0500
@@ -10,6 +10,7 @@
 -- but it seems that at least on common platforms it doesn't have
 -- to match the actual database encoding.
 SET lc_messages = 'es_ES.UTF-8';
+ERROR:  invalid value for parameter "lc_messages": "es_ES.UTF-8"
 SELECT test_translation();
 NOTICE:  NLS is not enabled
  test_translation

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=akepa&dt=2025-12-14%2017%3A11%3A11 - master

pgsql: Add a regression test to verify that NLS translation works. \ acceptable LC_MESSAGES values more variable

Try a few different locale name spellings in nls.sql.

nls.sql fails on many animals due to lack of es_ES.UTF-8 locale (after 8c498479d)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bumblebee&dt=2025-12-14%2016%3A56%3A02 - master

diff -U3 /u1/tac/build-farm/buildroot/HEAD/pgsql.build/src/test/regress/expected/nls_1.out /u1/tac/build-farm/buildroot/HEAD/pgsql.build/src/test/regress/results/nls.out
--- /u1/tac/build-farm/buildroot/HEAD/pgsql.build/src/test/regress/expected/nls_1.out	2025-12-14 11:56:03.500145052 -0500
+++ /u1/tac/build-farm/buildroot/HEAD/pgsql.build/src/test/regress/results/nls.out	2025-12-14 11:57:16.491736899 -0500
@@ -10,8 +10,24 @@
 -- but it seems that at least on common platforms it doesn't have
 -- to match the actual database encoding.
 SET lc_messages = 'es_ES.UTF-8';
+ERROR:  invalid value for parameter "lc_messages": "es_ES.UTF-8"
 SELECT test_translation();
-NOTICE:  NLS is not enabled
+NOTICE:  translated PRId64 = 424242424242
+NOTICE:  translated PRId32 = -1234
+NOTICE:  translated PRIdMAX = -5678
+NOTICE:  translated PRIdPTR = 9999
...

Also, nls.sql fails due to NLS doesn't work

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=grison&dt=2025-12-14%2019%3A20%3A06 - master

--- /data/pgbf/buildroot/HEAD/pgsql.build/src/test/regress/expected/nls_1.out	2025-12-14 20:20:52.614355959 +0100
+++ /data/pgbf/buildroot/HEAD/pgsql.build/src/test/regress/results/nls.out	2025-12-14 20:33:50.939780584 +0100
@@ -24,7 +24,22 @@
   end loop;
 end $$;
 SELECT test_translation();
-NOTICE:  NLS is not enabled
+NOTICE:  translated PRId64 = 424242424242
+NOTICE:  translated PRId32 = -1234
+NOTICE:  translated PRIdMAX = -5678
+NOTICE:  translated PRIdPTR = 9999
+NOTICE:  translated PRIu64 = 424242424242
+NOTICE:  translated PRIu32 = 1234
...

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=nicator&dt=2025-12-14%2019%3A08%3A07 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=branta&dt=2025-12-14%2018%3A08%3A20 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=treehopper&dt=2025-12-14%2018%3A08%3A38 - master

Also, NLS translation works partially

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=basilisk&dt=2025-12-14%2018%3A28%3A03 - master

diff -U3 /mnt/build/HEAD/pgsql/src/test/regress/expected/nls_1.out /mnt/build/HEAD/pgsql.build/src/test/regress/results/nls.out
--- /mnt/build/HEAD/pgsql/src/test/regress/expected/nls_1.out
+++ /mnt/build/HEAD/pgsql.build/src/test/regress/results/nls.out
@@ -24,7 +24,22 @@
   end loop;
 end $$;
 SELECT test_translation();
-NOTICE:  NLS is not enabled
+NOTICE:  translated PRId64 = 424242424242
+NOTICE:  translated PRId32 = -1234
+NOTICE:  translated PRIdMAX = -5678
+NOTICE:  translated PRIdPTR = 9999
+NOTICE:  traducido PRIu64 = 424242424242
+NOTICE:  traducido PRIu32 = 1234
+NOTICE:  translated PRIuMAX = 5678
+NOTICE:  translated PRIuPTR = 9999

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=basilisk&dt=2025-12-15%2004%3A35%3A44 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=basilisk&dt=2025-12-15%2011%3A07%3A00 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=basilisk&dt=2025-12-15%2019%3A06%3A52 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dogfish&dt=2025-12-14%2019%3A11%3A47 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dogfish&dt=2025-12-15%2005%3A19%3A50 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dogfish&dt=2025-12-15%2012%3A04%3A02 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dogfish&dt=2025-12-15%2019%3A44%3A15 - master

pgsql: Add a regression test to verify that NLS translation works. \ buildfarm failures on bumblebee and akepa

Looks like we can't test NLS on machines that lack any es_ES locale.

007_multixact_conversion.pl fails due to timeout on jit-enabled animals

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=urutu&dt=2025-12-09%2020%3A40%3A53 - master

t/007_multixact_conversion.pl .. 
Dubious, test returned 29 (wstat 7424, 0x1d00)

---
007_multixact_conversion_basic_oldnode.log:
...
2025-12-09 22:33:39.299 CET [2872679][client backend][21/2:0] LOG: statement: SET log_statement=none
     ;
2025-12-09 22:36:39.025 CET [2871745][postmaster][:0] LOG:  received immediate shutdown request

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=canebrake&dt=2025-12-14%2023%3A53%3A48 - master

POC: make mxidoff 64 bits \ failures of new test 007_multixact_conversion

Increase timeout in multixid_conversion upgrade test

nls.sql fails due to translation doesn't happen (after 7db6809ce)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mylodon&dt=2025-12-15%2020%3A58%3A46 - master

--- /home/bf/bf-build/mylodon/HEAD/pgsql/src/test/regress/expected/nls_1.out	2025-12-15 21:58:47.756271415 +0100
+++ /home/bf/bf-build/mylodon/HEAD/pgsql.build/testrun/regress/regress/results/nls.out	2025-12-15 21:59:18.068075714 +0100
@@ -13,7 +13,6 @@
 -- match the actual database encoding.
 SET lc_messages = 'C.UTF-8';
 SELECT test_translation();
-NOTICE:  NLS is not enabled
 NOTICE:  untranslated PRId64 = 424242424242
 NOTICE:  untranslated PRId32 = -1234
 NOTICE:  untranslated PRIdMAX = -123456789012

Other occurrences:

Also, nls.sql fails due to C.UTF-8 locale not accepted (after 7db6809ce)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=conchuela&dt=2025-12-15%2021%3A25%3A34 - master

--- /home/pgbf/buildroot/HEAD/pgsql.build/src/test/regress/expected/nls_1.out	2025-12-15 22:25:39.075903000 +0100
+++ /home/pgbf/buildroot/HEAD/pgsql.build/src/test/regress/results/nls.out	2025-12-15 22:27:42.008075000 +0100
@@ -12,8 +12,8 @@
 -- by appending a codeset name.  Fortunately it seems that that need not
 -- match the actual database encoding.
 SET lc_messages = 'C.UTF-8';
+ERROR:  invalid value for parameter "lc_messages": "C.UTF-8"
 SELECT test_translation();
-NOTICE:  NLS is not enabled
 NOTICE:  untranslated PRId64 = 424242424242

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=conchuela&dt=2025-12-15%2023%3A25%3A16 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sevengill&dt=2025-12-15%2020%3A58%3A55 - master

PRI?64 vs Visual Studio (2022) \ no translation happens on some Linux machines

Revert "Avoid requiring Spanish locale to test NLS infrastructure."

040_standby_failover_slots_sync.pl fails due to logical failover slot advancing beyond physical replslot

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=serinus&dt=2025-12-15%2011%3A25%3A38 - master

167/360 postgresql:recovery / recovery/040_standby_failover_slots_sync                  ERROR           226.24s   (exit status 255 or signal 127 SIGinvalid)

---
regress_log_040_standby_failover_slots_sync
[12:30:33.403](0.026s) ok 38 - check slot sync skip count increments
Waiting for all subscriptions in "subscriber1" to synchronize data
done
timed out waiting for match: (?^:newly created replication slot \\"lsub1_slot\\" is sync-ready now) at /home/bf/bf-build/serinus/HEAD/pgsql/src/test/recovery/t/040_standby_failover_slots_sync.pl line 1091.

---
040_standby_failover_slots_sync_standby2.log
2025-12-15 12:30:33.502 CET [3015371][client backend][1/2:0] ERROR:  skipping slot synchronization because the received slot sync LSN 0/06017C90 for slot "lsub1_slot" is ahead of the standby position 0/06017C58
2025-12-15 12:30:33.502 CET [3015371][client backend][1/2:0] STATEMENT:  SELECT pg_sync_replication_slots();

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=serinus&dt=2025-12-18%2002%3A17%3A09 - master

Improve pg_sync_replication_slots() to wait for primary to advance \ test synchronizes replication slot without configuring synchronized_standby_slots

Fix intermittent BF failure in 040_standby_failover_slots_sync.

publication.sql fails due to warning caused by insufficient wal_level (after 67c20979c)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=thorntail&dt=2025-12-24%2006%3A31%3A02 - master

diff -U3 /home/nm/farm/sparc64_deb10_gcc_64_ubsan/HEAD/pgsql/src/test/regress/expected/publication.out /home/nm/farm/sparc64_deb10_gcc_64_ubsan/HEAD/pgsql.build/src/test/regress/results/publication.out
--- /home/nm/farm/sparc64_deb10_gcc_64_ubsan/HEAD/pgsql/src/test/regress/expected/publication.out	2025-12-24 09:31:59.952761428 +0300
+++ /home/nm/farm/sparc64_deb10_gcc_64_ubsan/HEAD/pgsql.build/src/test/regress/results/publication.out	2025-12-24 09:53:49.497344501 +0300
@@ -288,8 +288,12 @@
 SET client_min_messages = 'NOTICE';
 CREATE PUBLICATION regress_pub_for_allsequences_alltables_withclause FOR ALL SEQUENCES, ALL TABLES WITH (publish = 'insert');
 NOTICE:  publication parameters are not applicable to sequence synchronization and will be ignored for sequences
+WARNING:  logical decoding must be enabled to publish logical changes
+HINT:  Before creating subscriptions, ensure that "wal_level" is set to "replica" or higher.
 CREATE PUBLICATION regress_pub_for_allsequences_withclause FOR ALL SEQUENCES WITH (publish_generated_columns = 'stored');
 NOTICE:  publication parameters are not applicable to sequence synchronization and will be ignored for sequences
...

POC: enable logical decoding when wal_level replica without a server restart \ BF failure related to commit 67c20979c

Fix regression test failure when wal_level is set to minimal.

Unsorted/Unhelpful Test Failures

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2024-07-22%2023%3A48%3A35 - REL_12_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2024-09-15%2000%3A40%3A56 - REL_15_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2024-10-02%2023%3A12%3A02 - REL_14_STABLE

2024-07-23 02:05:01.488 CEST [11841:3] FATAL:  shmat(id=721420316, addr=0, flags=0x4000) failed: Not enough space

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=lorikeet&dt=2024-07-24%2011%3A56%3A26 - REL_13_STABLE

running bootstrap script ... 2024-07-24 08:07:26.339 EDT [32845] FATAL:  could not create semaphores: No space left on device
2024-07-24 08:07:26.339 EDT [32845] DETAIL:  Failed system call was semget(153403862309413338, 17, 03600).

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=lorikeet&dt=2024-07-24%2012%3A07%3A31 - REL_14_STABLE

running bootstrap script ... 2024-07-24 08:18:18.859 EDT [39978] FATAL:  could not create semaphores: No space left on device
2024-07-24 08:18:18.859 EDT [39978] DETAIL:  Failed system call was semget(126100789568507477, 17, 03600).

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=lorikeet&dt=2024-07-24%2012%3A18%3A23 - REL_15_STABLE

running bootstrap script ... 2024-07-24 08:29:04.947 EDT [47271] FATAL:  could not create semaphores: No space left on device
2024-07-24 08:29:04.947 EDT [47271] DETAIL:  Failed system call was semget(43065671438868489, 17, 03600).

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=lorikeet&dt=2024-07-25%2008%3A54%3A07 - REL_12_STABLE

running bootstrap script ... 2024-07-25 05:03:13.089 EDT [25385] FATAL:  could not create semaphores: No space left on device
2024-07-25 05:03:13.089 EDT [25385] DETAIL:  Failed system call was semget(5828004, 17, 03600).

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=lorikeet&dt=2024-07-25%2009%3A03%3A38 - REL_15_STABLE

running bootstrap script ... 2024-07-25 05:12:52.813 EDT [32431] FATAL:  could not create semaphores: No space left on device
2024-07-25 05:12:52.813 EDT [32431] DETAIL:  Failed system call was semget(344525371495453222, 17, 03600).

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2024-07-24%2003%3A03%3A53 - REL_15_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2024-08-26%2004%3A38%3A23 - REL_14_STABLE

valgrind:  Fatal error at startup: a function redirection
...
valgrind:  Cannot continue -- exiting now.  Sorry.

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2024-07-22%2015%3A43%3A03 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2024-09-27%2013%3A33%3A03 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2024-11-28%2011%3A13%3A03 - REL_17_STABLE

 -- create an extra wide table to test for issues related to that
 -- (temporarily hide query, to avoid the long CREATE TABLE stmt)
 \\set ECHO none
+ERROR:  could not extend file "base/16387/1249" with FileFallocate(): No space left on device

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2024-07-24%2014%3A48%3A43 - REL_15_STABLE

-                           ->  Index Scan using ab_a2_b2_a_idx on ab_a2_b2 ab_5 (never executed)
-                                 Index Cond: (a = a.a)
+                           ->  Seq Scan on ab_a2_b2 ab_5 (never executed)
+                                 Filter: (a.a = a)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2024-07-24%2014%3A01%3A11 - REL_15_STABLE

test sto_using_hash_index         ... FAILED (test process exited with exit code 1)        5 ms
(no test log saved)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2024-07-24%2013%3A33%3A15 - REL_15_STABLE

test sto_using_select             ... FAILED (test process exited with exit code 1)        6 ms
test sto_using_hash_index         ... FAILED (test process exited with exit code 1)        5 ms
(no test log saved)

Temporary (occurred on 2024-07-24 only) environmental issues on leafhopper

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=lorikeet&dt=2024-07-26%2012%3A08%3A44 - REL_17_STABLE

timed out after 10800 secs

checking for suffix of executables...

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=canebrake&dt=2024-08-09%2009%3A14%3A15 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=canebrake&dt=2024-08-08%2019%3A19%3A21 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=canebrake&dt=2024-08-08%2005%3A02%3A34 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=canebrake&dt=2024-08-07%2015%3A11%3A43 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=canebrake&dt=2024-08-06%2006%3A58%3A57 - REL_14_STABLE

+ERROR:  could not import a module for Decimal constructor
+DETAIL:  ImportError: /usr/lib/python3.12/lib-dynload/_contextvars.cpython-312-x86_64-linux-gnu.so: undefined symbol: PyContextVar_Type

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-08-05%2004%3A24%3A54 - HEAD

291/291 postgresql:recovery / recovery/043_wal_replay_wait                              TIMEOUT        3000.17s   exit status 1

[04:47:30.407](1.844s) ok 3 - get timeout on waiting for unreachable LSN
01

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gull&dt=2024-08-06%2014%3A56%3A39 - HEAD

# +++ tap install-check in src/test/modules/test_custom_rmgrs +++
Bailout called.  Further testing stopped:  pg_ctl start failed

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skimmer&dt=2024-08-19%2014%3A23%3A01 - REL_15_STABLE

pg_rewind: error: could not fetch file list: ERROR:  could not load library "/u1/tac/build-farm-17/buildroot/REL_15_STABLE/pgsql.build/tmp_install/u1/tac/build-farm/buildroot/REL_15_STABLE/inst/lib/postgresql/llvmjit.so": libLLVM-16.so: cannot open shared object file: No such file or directory

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=alligator&dt=2024-08-24%2020%3A36%3A55 - REL_14_STABLE

2024-08-25 06:09:30.249 ACST [303452] LOG:  invalid value for parameter "lc_time": "en_AU.UTF-8"
2024-08-25 06:09:30.249 ACST [303452:5] FATAL:  configuration file "/home/postgres/proj/build-farm-17/buildroot/REL_14_STABLE/pgsql.build/src/bin/pg_upgrade/tmp_check/data/postgresql.conf" contains errors
 stopped waiting
pg_ctl: could not start server

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rinkhals&dt=2024-08-26%2019%3A27%3A51 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rinkhals&dt=2024-09-02%2019%3A18%3A59 - master

+ERROR:  could not open shared memory segment "/PostgreSQL.2570984136": No such file or directory

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gokiburi&dt=2024-09-05%2006%3A05%3A06 - master

2024-09-05 06:24:05.855 GMT [3913662] FATAL:  could not reattach to shared memory (key=2229908, addr=0xffffebe13000): Invalid argument
2024-09-05 06:24:05.872 GMT [3913664] FATAL:  could not reattach to shared memory (key=2229908, addr=0xffffebe13000): Invalid argument
...

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=chipmunk&dt=2024-09-01%2023%3A54%3A03 - master

# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 29 just after 24.
[09:46:01] t/018_wal_optimize.pl ................. 
Dubious, test returned 29 (wstat 7424, 0x1d00)
All 24 subtests passed 

---
pgsql.build/src/test/recovery/tmp_check/log/regress_log_018_wal_optimize
[09:45:58.805](1.411s) ok 24 - wal_level = replica, TRUNCATE INSERT PREPARE
connection error: 'psql:<stdin>:5: server closed the connection unexpectedly
	This probably means the server terminated abnormally
	before or while processing the request.
psql:<stdin>:5: error: connection to server was lost'
while running 'psql -XAtq -d port=28557 host=/home/pgbfarm/buildroot/tmp/3D1U2ctc_K dbname='postgres' -f - -v ON_ERROR_STOP=1' at /home/pgbfarm/buildroot/HEAD/pgsql.build/src/test/recovery/../../../src/test/perl/PostgreSQL/Test/Cluster.pm line 2138.
# Stale postmaster.pid file for node "node_minimal": PID 30563 no longer exists
# Stale postmaster.pid file for node "node_replica": PID 30644 no longer exists

---
pgsql.build/src/test/recovery/tmp_check/log/018_wal_optimize_node_minimal.log

2024-09-02 09:45:44.777 EEST [30563:3] LOG:  database system is ready to accept connections
...
2024-09-02 09:45:45.403 EEST [30573:4] 018_wal_optimize.pl LOG:  statement: SELECT pg_relation_filepath(oid) FROM pg_class
		   WHERE reltablespace = 0 AND relpersistence <> 't' AND
		   pg_relation_filepath(oid) IS NOT NULL;
2024-09-02 09:45:45.594 EEST [30573:5] 018_wal_optimize.pl LOG:  disconnection: session time: 0:00:00.225 user=pgbfarm database=postgres host=[local]
=== EOF ===

---
pgsql.build/src/test/recovery/tmp_check/log/018_wal_optimize_node_replica.log
2024-09-02 09:45:58.347 EEST [30644:3] LOG:  database system is ready to accept connections
...
2024-09-02 09:45:58.992 EEST [30654:5] 018_wal_optimize.pl LOG:  statement: BEGIN;
2024-09-02 09:45:58.994 EEST [30654:6] 018_wal_optimize.pl LOG:  statement: CREATE TABLE noskip (id serial PRIMARY KEY);
2024-09-02 09:45:59.091 EEST [30654:7] 018_wal_optimize.pl LOG:  statement: INSERT INTO noskip (SELECT FROM generate_series(1, 20000) a) ;
=== EOF ===

(two postmasters (30563 and 30644) just disappeared silently (were killed by OOM killer?))

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-09-03%2017%3A03%3A06 - master

SUCCESS: The process with PID 6304 (child process of PID 6420) has been terminated.
SUCCESS: The process with PID 6344 (child process of PID 6420) has been terminated.
SUCCESS: The process with PID 6420 (child process of PID 5384) has been terminated.
SUCCESS: The process with PID 5384 (child process of PID 4076) has been terminated.
postgresql:amcheck / amcheck/003_cic_2pc time out (After 3000.0 seconds)
246/246 postgresql:amcheck / amcheck/003_cic_2pc                                        TIMEOUT        3000.15s   exit status 1

---
pgsql.build/testrun/amcheck/003_cic_2pc/log/003_cic_2pc_CIC_2PC_test.log
2024-09-03 17:18:59.877 UTC [6804:3] LOG:  database system is ready to accept connections
2024-09-03 17:23:59.868 UTC [4460:1] LOG:  checkpoint starting: time
2024-09-03 17:24:04.992 UTC [4460:2] LOG:  checkpoint complete: wrote 48 buffers (0.3%); 0 WAL file(s) added, 0 removed, 0 recycled; write=5.119 s, sync=0.001 s, total=5.124 s; sync files=0, longest=0.000 s, average=0.000 s; distance=280 kB, estimate=280 kB; lsn=0/1577AD0, redo lsn=0/1577AB0
=== EOF ===

---
pgsql.build/testrun/amcheck/003_cic_2pc/log/regress_log_003_cic_2pc
[17:18:59.429](0.155s) ok 1 - bt_index_check after overlapping 2PC
### Restarting node "CIC_2PC_test"
# Running: pg_ctl -w -D C:\\tools\\nmsys64\\home\\pgrunner\\bf\\root\\HEAD\\pgsql.build/testrun/amcheck/003_cic_2pc/data/t_003_cic_2pc_CIC_2PC_test_data/pgdata -l C:\\tools\\nmsys64\\home\\pgrunner\\bf\\root\\HEAD\\pgsql.build/testrun/amcheck/003_cic_2pc/log/003_cic_2pc_CIC_2PC_test.log restart
waiting for server to shut down.... done
server stopped
waiting for server to start.... done
server started
# Postmaster PID for node "CIC_2PC_test" is 6804
=== EOF ===

The cause of the failure is not clear, but the test stopped when using BackgroundPsql.

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-09-11%2007%3A24%3A53 - master

SUCCESS: The process with PID 5976 (child process of PID 5928) has been terminated.
SUCCESS: The process with PID 4768 (child process of PID 5928) has been terminated.
SUCCESS: The process with PID 1616 (child process of PID 5928) has been terminated.
SUCCESS: The process with PID 5928 (child process of PID 5664) has been terminated.
SUCCESS: The process with PID 5664 (child process of PID 6668) has been terminated.
postgresql:subscription / subscription/015_stream time out (After 3000.0 seconds)
293/293 postgresql:subscription / subscription/015_stream                               TIMEOUT        3000.15s   exit status 1

---
pgsql.build/testrun/subscription/015_stream/log/015_stream_publisher.log
2024-09-11 09:13:36.886 UTC [512:4] 015_stream.pl LOG:  statement: TRUNCATE TABLE test_tab_2
...
2024-09-11 09:13:38.811 UTC [4320:4] 015_stream.pl LOG:  statement: SELECT '0/20E3BC8' <= replay_lsn AND state = 'streaming'
	         FROM pg_catalog.pg_stat_replication
	         WHERE application_name IN ('tap_sub', 'walreceiver')
2024-09-11 09:13:38.894 UTC [4320:5] 015_stream.pl LOG:  disconnection: session time: 0:00:00.252 user=pgrunner database=postgres host=127.0.0.1 port=58965
2024-09-11 09:17:17.844 UTC [5380:1] LOG:  checkpoint starting: time
2024-09-11 09:17:20.657 UTC [5380:2] LOG:  checkpoint complete: wrote 18 buffers (14.1%); 0 WAL file(s) added, 0 removed, 1 recycled; write=2.715 s, sync=0.001 s, total=2.813 s; sync files=0, longest=0.000 s, average=0.000 s; distance=12451 kB, estimate=12451 kB; lsn=0/21232F8, redo lsn=0/21232A0
=== EOF ===

---


pgsql.build/testrun/subscription/015_stream/log/regress_log_015_stream
[09:13:36.560](4.953s) ok 8 - data replicated to subscriber after dropping index
Waiting for replication conn tap_sub's replay_lsn to pass 0/20E3BC8 on publisher
done
[09:13:39.752](3.191s) # issuing query via background psql: 
# BEGIN;
# INSERT INTO test_tab_2 SELECT i FROM generate_series(1, 5000) s(i);

There is no connection attempt logged on the server side, the test stopped when using BackgroundPsql.

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gecko&dt=2024-09-11%2020%3A10%3A36 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gecko&dt=2024-09-11%2000%3A47%3A53 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gecko&dt=2024-09-11%2000%3A38%3A49 - REL_15_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gecko&dt=2024-09-11%2000%3A29%3A42 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gecko&dt=2024-09-11%2000%3A14%3A33 - REL_13_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gecko&dt=2024-09-11%2000%3A02%3A06 - REL_12_STABLE

+ERROR:  could not compute MD5 hash: unsupported

gecko is running in FIPS 140 mode

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=goshawk&dt=2024-09-12%2016%3A30%3A41 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=goshawk&dt=2024-09-12%2016%3A34%3A16 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=shoebill&dt=2024-09-12%2016%3A21%3A48 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=shoebill&dt=2024-09-12%2016%3A23%3A44 - master

-ERROR:  could not compute MD5 hash: unsupported
+ERROR:  could not compute MD5 hash: disabled for FIPS

goshawk and shoebill running on SUSE Linux Enterprise Server 15 SP2 (FIPS)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2024-09-21%2019%3A25%3A32 - master

LLVM ERROR: ThinLTO cannot create input file: Unknown attribute kind (86) (Producer: 'APPLE_1_1600.0.26.3_0' Reader: 'LLVM 15.0.7')
PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace.

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-09-23%2021%3A04%3A29 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-09-24%2003%3A03%3A07 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-09-24%2007%3A03%3A05 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-09-24%2000%3A45%3A10 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-09-23%2023%3A25%3A02 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-09-24%2006%3A22%3A45 - REL_16_STABLE

+ERROR:  could not load library "C:/tools/xmsys64/home/pgrunner/bf/root/HEAD/pgsql.build/tmp_install/tools/xmsys64/home/pgrunner/bf/root/HEAD/inst/lib/postgresql/plperl.dll": The specified module could not be found.

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-09-24%2016%3A03%3A07 - REL_12_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-09-25%2003%3A34%3A42 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-09-25%2007%3A18%3A30 - REL_17_STABLE

sh: line 1: /home/pgrunner/bf/root/upgrade.fairywren/REL9_2_STABLE/inst/bin/pg_ctl: No such file or directory

/home/bf/bf-build/adder/REL_12_STABLE/pgsql.build/../pgsql/src/pl/plperl/Util.c: loadable library and perl binaries are mismatched (got first handshake key 0x9580080, needed 0x91c0080)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sidewinder&dt=2024-10-25%2015%3A42%3A08 - REL_15_STABLE

Bailout called.  Further testing stopped:  pg_ctl start failed
t/001_constraint_validation.pl .. 
Dubious, test returned 255 (wstat 65280, 0xff00)

No test log saved. Waiting for the Tweak log file collection change to be deployed on buildfarm animals, including sidewinder, to get more information on the failure.

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=caiman&dt=2024-11-07%2003%3A43%3A22 - master

make[2]: Warning: File '../../preproc/ecpg.o' has modification time 70822 s in the future
/repos/client-code-REL_18/HEAD/pgsql.build/src/interfaces/ecpg/preproc/ecpg.c:72:(.text+0x16): undefined reference to `mm_alloc'

2024-12-02 20:49:45.644 CST [54997:1] FATAL:  could not create shared memory segment: No space left on device

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mereswine&dt=2025-01-17%2004%3A09%3A28 - REL_17_STABLE

2025-01-16 22:09:57.095 PST [22738:1] FATAL:  could not map anonymous shared memory: Cannot allocate memory

mereswine doesn't run tests anymore (since 2025-02-05)

2025-01-16 03:59:09.546 CET [26119:1] FATAL:  shmat(id=1006632988, addr=0, flags=0x4000) failed: Not enough space

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=tayra&dt=2025-02-24%2011%3A35%3A14 - master

2025-02-24 08:45:03.621 -03 [227213] ERROR:  invalid value for parameter "TimeZone": "America/Los_Angeles"

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2025-02-28%2010%3A45%3A58 - REL_17_STABLE

pg_restore: error: could not execute query: ERROR:  could not extend file "base/16384/2606": No space left on device
HINT:  Check free disk space.

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=pollock&dt=2025-03-03%2011%3A50%3A00 - master

gcc: error: unrecognized command-line option '-Wmissing-variable-declarations'; did you mean '-Wmissing-declarations'?
gmake[1]: *** [<builtin>: libpq_testclient.o] Error 1

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=grassquit&dt=2025-03-03%2018%3A56%3A10 - master

# initdb failed
...
==3792474==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 69 byte(s) in 1 object(s) allocated from:
    #0 0x7fbbceceed80 in strdup ../../../../src/libsanitizer/asan/asan_interceptors.cpp:578
    #1 0x55d91cd15969 in pg_strdup ../pgsql/src/common/fe_memutils.c:95
    #2 0x55d91cd0e53c in regression_main ../pgsql/src/test/regress/pg_regress.c:2172
    #3 0x55d91cd1289e in main ../pgsql/src/test/regress/pg_regress_main.c:113
    #4 0x7fbbcea33ca7 in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sevengill&dt=2025-03-21%2005%3A12%3A17 - master

running bootstrap script ... 2025-03-21 00:50:39.680 CDT [20143] FATAL:  could not create semaphores: Invalid argument
2025-03-21 00:50:39.680 CDT [20143] DETAIL:  Failed system call was semget(1746746229, 20, 03600).

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sevengill&dt=2025-02-19%2002%3A47%3A40 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sevengill&dt=2025-06-20%2021%3A10%3A26 - master

running bootstrap script ... 2025-06-20 17:27:35.593 CDT [80872] FATAL:  could not create shared memory segment: No space left on device
2025-06-20 17:27:35.593 CDT [80872] DETAIL:  Failed system call was shmget(key=2115162134, size=56, 03600).

valgrind:  A must-be-redirected function
valgrind:  whose name matches the pattern:      strcmp
valgrind:  in an object with soname matching:   ld-linux-x86-64.so.2
valgrind:  was not found whilst processing
valgrind:  symbols from the object with soname: ld-linux-x86-64.so.2

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=kestrel&dt=2025-03-03%2019%3A26%3A36 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=kestrel&dt=2025-03-03%2019%3A46%3A40 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-03%2018%3A48%3A14 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-03%2018%3A52%3A13 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-03-03%2019%3A22%3A29 - master

3/3 postgresql:setup / initdb_cache       FAIL             4.74s   exit status 1
>>> ...  /usr/bin/python3 -c '
...
sp = subprocess.run(sys.argv[2:] + [sys.argv[1]])
sys.exit(sp.returncode)
' .../initdb-template .../initdb --auth trust --no-sync --no-instructions --lc-messages=C --no-clean

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=alligator&dt=2025-02-08%2019%3A36%3A39 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=alligator&dt=2025-02-08%2019%3A35%3A46 - master

2025-02-09 06:25:59.733 ACDT [388413] LOG:  invalid value for parameter "lc_monetary": "en_AU.UTF-8"
2025-02-09 06:25:59.733 ACDT [388413] LOG:  invalid value for parameter "lc_numeric": "en_AU.UTF-8"
2025-02-09 06:25:59.733 ACDT [388413] LOG:  invalid value for parameter "lc_time": "en_AU.UTF-8"
2025-02-09 06:25:59.733 ACDT [388413:4] FATAL:  configuration file "/home/postgres/proj/bfgit/buildroot/HEAD/pgsql.build/src/test/recovery/tmp_check/t_001_stream_rep_primary_data/pgdata/postgresql.conf" contains errors

running bootstrap script ... 2025-03-18 18:22:36.463 EET [94456] FATAL:  could not create semaphores: No space left on device
2025-03-18 18:22:36.463 EET [94456] DETAIL:  Failed system call was semget(312211, 20, 03600).

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2025-04-01%2021%3A55%3A05 - REL_13_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2025-04-01%2021%3A56%3A03 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2025-04-01%2021%3A57%3A03 - REL_15_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2025-04-01%2021%3A58%3A05 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2025-04-01%2021%3A59%3A05 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2025-04-01%2022%3A00%3A06 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=indri&dt=2025-04-01%2022%3A16%3A59 - master

LLVM ERROR: ThinLTO cannot create input file: Invalid attribute group entry (Producer: 'APPLE_1_1700.0.13.3_0' Reader: 'LLVM 17.0.6')
PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace.
Stack dump:
0.	Program arguments: /opt/local/libexec/llvm-17/bin/llvm-lto -thinlto -thinlto-action=thinlink -o postgres.index.bc ...
 #0 0x00000001077ab8ac llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) (/opt/local/libexec/llvm-17/lib/libLLVM.dylib+0x13b8ac)
 #1 0x00000001077a9c10 llvm::sys::RunSignalHandlers() (/opt/local/libexec/llvm-17/lib/libLLVM.dylib+0x139c10)
 #2 0x00000001077abf08 SignalHandler(int) (/opt/local/libexec/llvm-17/lib/libLLVM.dylib+0x13bf08)
 #3 0x000000019a16b624 (/usr/lib/system/libsystem_platform.dylib+0x1804ab624)
 #4 0x000000019a13188c (/usr/lib/system/libsystem_pthread.dylib+0x18047188c)
 #5 0x000000019a03ac60 (/usr/lib/system/libsystem_c.dylib+0x18037ac60)
 #6 0x000000010770af28 llvm::report_fatal_error(llvm::Twine const&, bool) (/opt/local/libexec/llvm-17/lib/libLLVM.dylib+0x9af28)
 #7 0x0000000108bfb26c llvm::ThinLTOCodeGenerator::addModule(llvm::StringRef, llvm::StringRef) (/opt/local/libexec/llvm-17/lib/libLLVM.dylib+0x158b26c)
 #8 0x000000010019106c thinlto::ThinLTOProcessing::thinLink() (/opt/local/libexec/llvm-17/bin/llvm-lto+0x10000906c)
 #9 0x000000010018cca0 main (/opt/local/libexec/llvm-17/bin/llvm-lto+0x100004ca0)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bumblebee&dt=2025-04-10%2015%3A00%3A01 - master

2025-04-10 11:01:15.392 EDT [95004:1] FATAL:  could not setup io_uring queue: Operation not permitted
2025-04-10 11:01:15.392 EDT [95004:2] HINT:  Check if io_uring is disabled via /proc/sys/kernel/io_uring_disabled.

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gull&dt=2025-05-08%2002%3A10%3A18 - master

t/002_pg_upgrade.pl     (Wstat: 9 Tests: 21 Failed: 0)
  Non-zero wait status: 9
  Parse errors: No plan found in TAP output
Files=6, Tests=86, 4386 wallclock secs ( 0.44 usr  0.11 sys + 128.02 cusr 91.16 csys = 219.73 CPU)
Result: FAIL

# Running: pg_dumpall --no-sync --dbname port=22733 host=/tmp/hVp3cVTCY0 dbname='postgres' --file /home/pgsql/build-farm/buildroot-clang/HEAD/pgsql.build/src/bin/pg_upgrade/tmp_check/tmp_test_3hGg/dump2.sql
[02:37:21.325](109.273s) ok 21 - dump after running pg_upgrade
=== EOF ===

(apparently, the last check 'old and new dumps match after pg_upgrade' was not reached)

gull is gone --- there were no test runs after this one

                   'extra_config' => {
                                       'DEFAULT' => [
...
                                                      'io_method=io_uring'
                                                    ],
                                       'HEAD' => [
                                                   'debug_parallel_query = regress'
                                                 ]
                                     },
...
pgsql.build/src/test/regress/log/postmaster.log
2025-05-12 14:51:40.639 GMT [2545686] LOG:  unrecognized configuration parameter "io_method" in file "/home/postgres/proj/bfgit/buildroot/REL_17_STABLE/pgsql.build/src/test/regress/tmp_check/data/postgresql.conf" line 857
2025-05-12 14:51:40.639 GMT [2545686] FATAL:  configuration file "/home/postgres/proj/bfgit/buildroot/REL_17_STABLE/pgsql.build/src/test/regress/tmp_check/data/postgresql.conf" contains errors

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-05-19%2015%3A54%3A29 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-05-19%2016%3A21%3A01 - REL_15_STABLE

upgrade.drongo/REL_15_STABLE/dumpdiff-REL_13_STABLE

--- C:\\prog\\bf/root/upgrade.drongo/REL_15_STABLE/origin-REL_13_STABLE.sql.fixed	2025-05-19 16:44:18.013538300 +0000
+++ C:\\prog\\bf/root/upgrade.drongo/REL_15_STABLE/converted-REL_13_STABLE-to-REL_15_STABLE.sql.fixed	2025-05-19 16:44:18.060398400 +0000
@@ -9229,7 +9229,7 @@
   WHERE (onek.thousand < 995)
   ORDER BY onek.thousand
  OFFSET 10
- FETCH FIRST 5 ROWS WITH TIES;
+ FETCH FIRST (5) ROWS WITH TIES;
 ALTER TABLE public.limit_thousand_v_1 OWNER TO buildfarm;
 --
 -- Name: limit_thousand_v_2; Type: VIEW; Schema: public; Owner: buildfarm
@@ -9250,7 +9250,7 @@
    FROM public.onek
   WHERE (onek.thousand < 995)
   ORDER BY onek.thousand
- FETCH FIRST (NULL::integer + 1) ROWS WITH TIES;
+ FETCH FIRST ((NULL::integer + 1)) ROWS WITH TIES;
 ALTER TABLE public.limit_thousand_v_3 OWNER TO buildfarm;
 --
 -- Name: limit_thousand_v_4; Type: VIEW; Schema: public; Owner: buildfarm

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=broadbill&dt=2025-06-06%2013%3A22%3A31 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=broadbill&dt=2025-06-11%2013%3A22%3A52 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=broadbill&dt=2025-06-11%2013%3A52%3A34 - REL_16_STABLE

ERROR:  could not write to file "base/64200/2680": No space left on device

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dodo&dt=2025-06-06%2015%3A59%3A26 - master

initdb: error: invalid locale settings; check LANG and LC_* environment variables

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dodo&dt=2025-06-10%2003%3A51%3A41 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dodo&dt=2025-08-10%2005%3A04%3A08 - REL_13_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dodo&dt=2025-08-10%2005%3A05%3A08 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dodo&dt=2025-08-10%2005%3A07%3A21 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dodo&dt=2025-11-01%2009%3A06%3A09 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dodo&dt=2025-11-01%2009%3A08%3A10 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dodo&dt=2025-11-05%2017%3A51%3A08 - REL_17_STABLE

timed out after 14400 secs

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bulbul&dt=2025-06-07%2002%3A21%3A43 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bulbul&dt=2025-06-08%2001%3A08%3A05 - master

ERROR:  could not extend file "base/79786/3456_vm": No space left on device

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-02-05%2015%3A26%3A51 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-02-05%2017%3A52%3A03 - master

----
--- /home/andrew/bf/root/HEAD/redis_fdw.build/test/expected/redis_fdw.out	2021-06-29 13:33:37.761589602 -0400
+++ /home/andrew/bf/root/HEAD/redis_fdw.build/test/results/redis_fdw.out	2025-02-05 10:36:42.440034768 -0500
@@ -42,1359 +42,10 @@
     end if;
   end;
 $$;
-\\unset ON_ERROR_STOP
--- ok, empty, so now run the setup script
-\\! redis-cli < test/sql/redis_setup
...
+ERROR:  invalid tabletype (hash) - must be hash, list, set or zset
+CONTEXT:  SQL statement "select                   (select count(*) from db15) +
+        (select count(*) from db15_hash) +
+        (select count(*) from db15_set) +
+        (select count(*) from db15_list) +
+        (select count(*) from db15_zset)"
+PL/pgSQL function inline_code_block line 5 at SQL statement

not ok 1     - redis_fdw                                  14 ms

2025-07-18 16:59:32.504 EDT [2025-07-18 16:59:32 EDT 154991:13] pg_regress/redis_fdw ERROR:  failed to connect to Redis: 1

--- /home/pgbf/buildroot/upgrade.copperhead/REL_13_STABLE/origin-REL_13_STABLE.sql.fixed	2025-08-11 18:39:06.175113869 +0200
+++ /home/pgbf/buildroot/upgrade.copperhead/REL_13_STABLE/converted-REL_13_STABLE-to-REL_13_STABLE.sql.fixed	2025-08-11 18:39:06.215113855 +0200
@@ -2,7 +2,7 @@
 -- PostgreSQL database cluster dump
 --
 
-\\restrict wm7Y7Ihk0dtiYSIwhSVZCN6oZfBi2F9UJSbaYa3Z5yCrpzwxzaRbs6qM9KM2LiE
+\\restrict TmEcosJEfIJz56WH3zuPcqIGJ6JahIR118Dxg7uQq4YUvXEmexcYduGoHlOwFlQ
...

Handle new --restrict-key requirement for dump testing

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=grison&dt=2025-10-11%2006%3A02%3A42 - REL_17_STABLE

2025-10-11 08:45:12.155 CEST [27647] LOG:  invalid value for parameter "lc_monetary": "en_GB.UTF-8"
2025-10-11 08:45:12.155 CEST [27647] LOG:  invalid value for parameter "lc_numeric": "en_GB.UTF-8"
2025-10-11 08:45:12.155 CEST [27647] LOG:  invalid value for parameter "lc_time": "en_GB.UTF-8"
2025-10-11 08:45:12.155 CEST [27647:4] FATAL:  configuration file "/data/pgbf/buildroot/REL_17_STABLE/pgsql.build/src/bin/pg_upgrade/tmp_check/t_003_logical_slots_newpub_data/pgdata/postgresql.conf" contains errors

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=ovenbird&dt=2025-11-14%2009%3A20%3A05 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=ovenbird&dt=2025-11-14%2009%3A21%3A05 - REL_17_STABLE

configure: using compiler=gcc (GCC) 16.0.0 20251114 (experimental)
...
# +++ tap check in src/bin/pg_upgrade +++
[10:41:51] t/001_basic.pl ....... ok     2676 ms ( 0.02 usr  0.00 sys +  2.35 cusr  0.32 csys =  2.69 CPU)

===================================================
timed out after 14400 secs

configure: using compiler=gcc (GCC) 16.0.0 20251125 (experimental)
...
not ok 1     - test_lfind                              25013 ms
# (test process exited with exit code 2)

---
logfile
TRAP: failed Assert("assert_result == result"), File: "../../../../src/include/port/simd.h", Line: 279, PID: 3469299
postgres: buildfarm contrib_regression_test_lfind [local] SELECT(ExceptionalCondition+0x48)[0xa25348]
/home/bf/proj/bf/build-farm-17/HEAD/inst/lib/postgresql/test_lfind.so(+0x10380)[0xffff89d19380]
/home/bf/proj/bf/build-farm-17/HEAD/inst/lib/postgresql/test_lfind.so(test_lfind8_le+0x20)[0xffff89d19bd0]
postgres: buildfarm contrib_regression_test_lfind [local] SELECT[0x6c014c]
postgres: buildfarm contrib_regression_test_lfind [local] SELECT[0x6fc60c]
postgres: buildfarm contrib_regression_test_lfind [local] SELECT(standard_ExecutorRun+0x16c)[0x6c40cc]
postgres: buildfarm contrib_regression_test_lfind [local] SELECT[0x8c55d8]
postgres: buildfarm contrib_regression_test_lfind [local] SELECT(PortalRun+0x208)[0x8c6da8]
postgres: buildfarm contrib_regression_test_lfind [local] SELECT[0x8c27bc]
postgres: buildfarm contrib_regression_test_lfind [local] SELECT(PostgresMain+0x5d0)[0x8c3130]
postgres: buildfarm contrib_regression_test_lfind [local] SELECT(BackendMain+0x4c)[0x8be150]
postgres: buildfarm contrib_regression_test_lfind [local] SELECT(postmaster_child_launch+0x134)[0x804fd4]
postgres: buildfarm contrib_regression_test_lfind [local] SELECT[0x808adc]
postgres: buildfarm contrib_regression_test_lfind [local] SELECT(PostmasterMain+0xb74)[0x80a274]
postgres: buildfarm contrib_regression_test_lfind [local] SELECT(main+0x1d4)[0x4a6cb4]
/lib64/libc.so.6(+0x30558)[0xffffa3262558]
/lib64/libc.so.6(__libc_start_main+0x9c)[0xffffa326263c]
postgres: buildfarm contrib_regression_test_lfind [local] SELECT(_start+0x30)[0x4a7230]
2025-11-25 15:09:38.801 UTC [3467394:4] LOG:  client backend (PID 3469299) was terminated by signal 6: Aborted
2025-11-25 15:09:38.801 UTC [3467394:5] DETAIL:  Failed process was running: SELECT test_lfind8_le();

(The issue is gone with gcc updated to 16.0.0 20251126 (experimental).)

---