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.

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