Known Buildfarm Test Failures

Investigated Test failures

027_stream_regress.pl fails to wait for standby because of incorrect CRC in WAL

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

(dodo is a armv7l machine using SLICING_BY_8_CRC32C and having wal_consistency_checking enabled)

# poll_query_until timed out executing this query:
# SELECT '2/8E09BD70' <= replay_lsn AND state = 'streaming'
#          FROM pg_catalog.pg_stat_replication
#          WHERE application_name IN ('standby_1', 'walreceiver')
# expecting this output:
# t
# last actual query output:
# 
# 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 2.
[17:19:00] t/027_stream_regress.pl ............... 
Dubious, test returned 29 (wstat 7424, 0x1d00)
All 2 subtests passed 


---
027_stream_regress_standby_1.log:

2024-05-02 17:08:18.579 ACST [3404:205] LOG:  restartpoint starting: wal
2024-05-02 17:08:18.401 ACST [3406:7] LOG:  incorrect resource manager data checksum in record at 0/F14D7A60
2024-05-02 17:08:18.579 ACST [3407:2] FATAL:  terminating walreceiver process due to administrator command
2024-05-02 17:08:18.579 ACST [3406:8] LOG:  incorrect resource manager data checksum in record at 0/F14D7A60
...
2024-05-02 17:19:00.093 ACST [3406:2604] LOG:  incorrect resource manager data checksum in record at 0/F14D7A60
2024-05-02 17:19:00.093 ACST [3406:2605] LOG:  waiting for WAL to become available at 0/F1002000
2024-05-02 17:19:00.594 ACST [3406:2606] LOG:  incorrect resource manager data checksum in record at 0/F14D7A60
2024-05-02 17:19:00.594 ACST [3406:2607] LOG:  waiting for WAL to become available at 0/F1002000
2024-05-02 17:19:00.758 ACST [3403:4] LOG:  received immediate shutdown request
2024-05-02 17:19:00.785 ACST [3403:5] LOG:  database system is shut down

WAL record CRC calculated incorrectly because of underlying buffer modification

020_archive_status.pl failed to wait for updated statistics due to send() returned EAGAIN

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=morepork&dt=2024-04-30%2020%3A48%3A34 - REL_13_STABLE

(morepork is running on OpenBSD 6.9)

# poll_query_until timed out executing this query:
# SELECT archived_count FROM pg_stat_archiver
# expecting this output:
# 1
# last actual query output:
# 0
# with stderr:
# Looks like your test exited with 29 just after 4.
[23:01:41] t/020_archive_status.pl ..............
Dubious, test returned 29 (wstat 7424, 0x1d00)
Failed 12/16 subtests

---
020_archive_status_master.log:
2024-04-30 22:57:27.931 CEST [83115:1] LOG:  archive command failed with exit code 1
2024-04-30 22:57:27.931 CEST [83115:2] DETAIL:  The failed archive command was: cp 
"pg_wal/000000010000000000000001_does_not_exist" "000000010000000000000001_does_not_exist"
...
2024-04-30 22:57:28.070 CEST [47962:2] [unknown] LOG:  connection authorized: user=pgbf database=postgres 
application_name=020_archive_status.pl
2024-04-30 22:57:28.072 CEST [47962:3] 020_archive_status.pl LOG: statement: SELECT archived_count FROM pg_stat_archiver
2024-04-30 22:57:28.073 CEST [83115:3] LOG:  could not send to statistics collector: Resource temporarily unavailable

Non-systematic handling of EINTR/EAGAIN/EWOULDBLOCK

031_recovery_conflict.pl fails to detect an expected lock acquisition

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=adder&dt=2024-03-18%2023%3A43%3A00 - HEAD

[23:48:52.521](9.831s) ok 13 - startup deadlock: cursor holding conflicting pin, also waiting for lock, established
[23:55:13.749](381.228s) # poll_query_until timed out executing this query:
# 
# SELECT 'waiting' FROM pg_locks WHERE locktype = 'relation' AND NOT granted;
# 
# expecting this output:
# waiting
# last actual query output:
# 
# with stderr:
[23:55:13.763](0.013s) not ok 14 - startup deadlock: lock acquisition is waiting
[23:55:13.763](0.001s) #   Failed test 'startup deadlock: lock acquisition is waiting'
#   at /home/bf/bf-build/adder/HEAD/pgsql/src/test/recovery/t/031_recovery_conflict.pl line 261.
Waiting for replication conn standby's replay_lsn to pass 0/3450000 on primary
done

---
031_recovery_conflict_standby.log
2024-03-18 23:48:52.526 UTC [3138907][client backend][1/2:0] LOG:  statement: SELECT * FROM test_recovery_conflict_table2;
2024-03-18 23:48:52.690 UTC [3139905][not initialized][:0] LOG:  connection received: host=[local]
2024-03-18 23:48:52.692 UTC [3139905][client backend][2/1:0] LOG:  connection authenticated: user="bf" method=trust (/home/bf/bf-build/adder/HEAD/pgsql.build/testrun/recovery/031_recovery_conflict/data/t_031_recovery_conflict_standby_data/pgdata/pg_hba.conf:117)
2024-03-18 23:48:52.692 UTC [3139905][client backend][2/1:0] LOG:  connection authorized: user=bf database=postgres application_name=031_recovery_conflict.pl
2024-03-18 23:48:53.301 UTC [3136308][startup][34/0:0] LOG:  recovery still waiting after 10.099 ms: recovery conflict on buffer pin
2024-03-18 23:48:53.301 UTC [3136308][startup][34/0:0] CONTEXT:  WAL redo at 0/342CCC0 for Heap2/PRUNE: ...
2024-03-18 23:48:53.301 UTC [3138907][client backend][1/2:0] ERROR:  canceling statement due to conflict with recovery at character 15
2024-03-18 23:48:53.301 UTC [3138907][client backend][1/2:0] DETAIL:  User transaction caused buffer deadlock with recovery.
2024-03-18 23:48:53.301 UTC [3138907][client backend][1/2:0] STATEMENT:  SELECT * FROM test_recovery_conflict_table2;
2024-03-18 23:48:53.301 UTC [3136308][startup][34/0:0] LOG:  recovery finished waiting after 10.633 ms: recovery conflict on buffer pin
2024-03-18 23:48:53.301 UTC [3136308][startup][34/0:0] CONTEXT:  WAL redo at 0/342CCC0 for Heap2/PRUNE: ...
2024-03-18 23:48:53.769 UTC [3139905][client backend][2/2:0] LOG:  statement: SELECT 'waiting' FROM pg_locks WHERE locktype = 'relation' AND NOT granted;

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-10-14%2016%3A39%3A49 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-12-26%2005%3A49%3A14 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-02-01%2007%3A11%3A46 - master

Test 031_recovery_conflict.pl is not immune to autovacuum

031_recovery_conflict.pl fails when a conflict counted twice

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=olingo&dt=2024-05-15%2023%3A03%3A30 - HEAD

(olingo builds postgres with -O1 and address sanitizer)

[23:12:02.127](0.166s) not ok 6 - snapshot conflict: stats show conflict on standby
[23:12:02.130](0.003s) #   Failed test 'snapshot conflict: stats show conflict on standby'
#   at /home/bf/bf-build/olingo/HEAD/pgsql/src/test/recovery/t/031_recovery_conflict.pl line 332.
[23:12:02.130](0.000s) #          got: '2'
#     expected: '1'
...
[23:12:06.848](1.291s) not ok 17 - 5 recovery conflicts shown in pg_stat_database
[23:12:06.887](0.040s) #   Failed test '5 recovery conflicts shown in pg_stat_database'
#   at /home/bf/bf-build/olingo/HEAD/pgsql/src/test/recovery/t/031_recovery_conflict.pl line 286.
[23:12:06.887](0.000s) #          got: '6'
#     expected: '5'
Waiting for replication conn standby's replay_lsn to pass 0/3459160 on primary
done

---
031_recovery_conflict_standby.log:
2024-05-15 23:12:01.959 UTC [1299981][client backend][2/2:0] FATAL: terminating connection due to conflict with recovery
2024-05-15 23:12:01.959 UTC [1299981][client backend][2/2:0] DETAIL:  User query might have needed to see row versions 
that must be removed.
2024-05-15 23:12:01.959 UTC [1299981][client backend][2/2:0] HINT: In a moment you should be able to reconnect to the 
database and repeat your command.
2024-05-15 23:12:01.966 UTC [1299981][client backend][2/2:0] LOG: could not send data to client: Broken pipe
2024-05-15 23:12:01.966 UTC [1299981][client backend][2/2:0] FATAL: terminating connection due to conflict with recovery
2024-05-15 23:12:01.966 UTC [1299981][client backend][2/2:0] DETAIL:  User query might have needed to see row versions 
that must be removed.
2024-05-15 23:12:01.966 UTC [1299981][client backend][2/2:0] HINT: In a moment you should be able to reconnect to the 
database and repeat your command.

Test 031_recovery_conflict fails when a conflict counted twice

001_rep_changes.pl fails due to publisher stuck on shutdown

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=adder&dt=2024-05-16%2014%3A22%3A38 - HEAD

[14:33:02.374](0.333s) ok 23 - update works with dropped subscriber column
### Stopping node "publisher" using mode fast
# Running: pg_ctl -D 
/home/bf/bf-build/adder/HEAD/pgsql.build/testrun/subscription/001_rep_changes/data/t_001_rep_changes_publisher_data/pgdata 
-m fast stop
waiting for server to shut down.. ... ... ... .. failed
pg_ctl: server does not shut down
# pg_ctl stop failed: 256
# Postmaster PID for node "publisher" is 2222549
[14:39:04.375](362.001s) Bail out!  pg_ctl stop failed

---
001_rep_changes_publisher.log
2024-05-16 14:33:02.907 UTC [2238704][client backend][4/22:0] LOG: statement: DELETE FROM tab_rep
2024-05-16 14:33:02.925 UTC [2238704][client backend][:0] LOG: disconnection: session time: 0:00:00.078 user=bf 
database=postgres host=[local]
2024-05-16 14:33:02.939 UTC [2222549][postmaster][:0] LOG:  received fast shutdown request
2024-05-16 14:33:03.000 UTC [2222549][postmaster][:0] LOG:  aborting any active transactions
2024-05-16 14:33:03.049 UTC [2222549][postmaster][:0] LOG: background worker "logical replication launcher" (PID 
2223110) exited with exit code 1
2024-05-16 14:33:03.062 UTC [2222901][checkpointer][:0] LOG: shutting down
2024-05-16 14:39:04.377 UTC [2222549][postmaster][:0] LOG:  received immediate shutdown request
2024-05-16 14:39:04.382 UTC [2222549][postmaster][:0] LOG:  database system is shut down

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dikkop&dt=2024-04-24%2014%3A38%3A35 - HEAD
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2024-07-16%2022%3A45%3A10 - REL_17_STABLE

Also 035_standby_logical_decoding.pl fails on restart of standby (which is a publisher in the test):

001_rep_changes.pl fails due to publisher stuck on shutdown

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

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

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

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

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

Recent 027_streaming_regress.pl hangs \ deadlock-parallel failures

027_stream_regress.pl fails on crake with timeout when waiting for catchup

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2024-07-17%2014%3A56%3A09 - REL_16_STABLE

150/263 postgresql:recovery / recovery/027_stream_regress                         ERROR          1246.17s   exit status 29

---
regress_log_027_stream_regress
[11:24:44.119](225.205s) # poll_query_until timed out executing this query:
# SELECT '2/791D9828' <= replay_lsn AND state = 'streaming'
#          FROM pg_catalog.pg_stat_replication
#          WHERE application_name IN ('standby_1', 'walreceiver')
# expecting this output:
# t
# last actual query output:
# f
# with stderr:
timed out waiting for catchup at /home/andrew/bf/root/REL_16_STABLE/pgsql/src/test/recovery/t/027_stream_regress.pl line 100.

---
027_stream_regress_standby_1.log
2024-07-17 11:24:13.363 EDT [2024-07-17 11:04:06 EDT 1365647:393] LOG:  restartpoint starting: wal
2024-07-17 11:24:22.384 EDT [2024-07-17 11:04:06 EDT 1365647:394] LOG:  restartpoint complete: wrote 92 buffers (71.9%); 0 WAL file(s) added, 1 removed, 3 recycled; write=9.021 s, sync=0.001 s, total=9.022 s; sync files=0, longest=0.000 s, average=0.000 s; distance=63581 kB, estimate=67348 kB; lsn=1/B4A99C78, redo lsn=1/B1053BC8
2024-07-17 11:24:22.384 EDT [2024-07-17 11:04:06 EDT 1365647:395] LOG:  recovery restart point at 1/B1053BC8
2024-07-17 11:24:22.384 EDT [2024-07-17 11:04:06 EDT 1365647:396] DETAIL:  Last completed transaction was at log time 2024-07-17 11:11:58.69292-04.
2024-07-17 11:24:44.260 EDT [2024-07-17 11:04:06 EDT 1365651:2] FATAL:  could not receive data from WAL stream: server closed the connection unexpectedly
		This probably means the server terminated abnormally
		before or while processing the request.

Recent 027_streaming_regress.pl hangs \ crake is failing due to other reasons

027_stream_regress.pl fails due to some IOS plans of queries in create_index.sql changed

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sungazer&dt=2024-03-17%2003%3A03%3A57 - REL_16_STABLE

#   Failed test 'regression tests pass'
#   at t/027_stream_regress.pl line 92.
#          got: '256'
#     expected: '0'
# Looks like you failed 1 test of 6.
[07:07:42] t/027_stream_regress.pl .............. 
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/6 subtests 

---
regress_log_027_stream_regress:
...
not ok 66    + create_index                            27509 ms
...
----
diff -U3 /home/nm/farm/gcc64/REL_16_STABLE/pgsql.build/src/test/regress/expected/create_index.out /home/nm/farm/gcc64/REL_16_STABLE/pgsql.build/src/test/recovery/tmp_check/results/create_index.out
--- /home/nm/farm/gcc64/REL_16_STABLE/pgsql.build/src/test/regress/expected/create_index.out	2023-07-08 15:26:29.000000000 +0000
+++ /home/nm/farm/gcc64/REL_16_STABLE/pgsql.build/src/test/recovery/tmp_check/results/create_index.out	2024-03-17 06:59:01.000000000 +0000
@@ -1916,11 +1916,15 @@
  SELECT unique1 FROM tenk1
  WHERE unique1 IN (1,42,7)
  ORDER BY unique1;
-                       QUERY PLAN                       
- -------------------------------------------------------
-  Index Only Scan using tenk1_unique1 on tenk1
-    Index Cond: (unique1 = ANY ('{1,42,7}'::integer[]))
- (2 rows)
+                             QUERY PLAN                             
+ -------------------------------------------------------------------
+  Sort
+    Sort Key: unique1
+    ->  Bitmap Heap Scan on tenk1
+          Recheck Cond: (unique1 = ANY ('{1,42,7}'::integer[]))
+          ->  Bitmap Index Scan on tenk1_unique1
+                Index Cond: (unique1 = ANY ('{1,42,7}'::integer[]))
+ (6 rows)
  
  SELECT unique1 FROM tenk1
  WHERE unique1 IN (1,42,7)
@@ -1936,12 +1940,13 @@
  SELECT thousand, tenthous FROM tenk1
  WHERE thousand < 2 AND tenthous IN (1001,3000)
  ORDER BY thousand;
-                       QUERY PLAN                       
- -------------------------------------------------------
-  Index Only Scan using tenk1_thous_tenthous on tenk1
-    Index Cond: (thousand < 2)
-    Filter: (tenthous = ANY ('{1001,3000}'::integer[]))
- (3 rows)
+                                       QUERY PLAN                                      
+ --------------------------------------------------------------------------------------
+  Sort
+    Sort Key: thousand
+    ->  Index Only Scan using tenk1_thous_tenthous on tenk1
+          Index Cond: ((thousand < 2) AND (tenthous = ANY ('{1001,3000}'::integer[])))
+ (4 rows)
  
  SELECT thousand, tenthous FROM tenk1
  WHERE thousand < 2 AND tenthous IN (1001,3000)

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sungazer&dt=2025-01-17%2009%3A21%3A57 - REL_15_STABLE

Also 002_pg_upgrade.pl fails due to some IOS plans of queries in create_index.sql changed

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hornet&dt=2024-01-02%2007%3A09%3A09 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sungazer&dt=2023-11-15%2006%3A16%3A15 - HEAD

To what extent should tests rely on VACUUM ANALYZE? \ create_index failures

regress-running/regress fails on skink due to timeout

(skink is a Valgrind animal)

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

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

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

Recent 027_streaming_regress.pl hangs \ meson TIMEOUT on skink

035_standby_logical_decoding_standby.pl fails due to missing activeslot invalidation

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

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

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

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

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

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

xversion-upgrade-XXX fails due to pg_ctl timeout

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2024-05-23%2004%3A11%3A03 - REL_16_STABLE

REL9_5_STABLE-ctl4.log
waiting for server to shut down........................................................................................................................... failed
pg_ctl: server does not shut down

Also test runs fail on the stopdb-C-x stage

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=opaleye&dt=2024-06-08%2001%3A41%3A41 - HEAD

The xversion-upgrade test fails to stop server

A partial fix: The xversion-upgrade test fails to stop server \ PGCTLTIMEOUT increased on crake

subscriber tests fail due to an assertion failure in SnapBuildInitialSnapshot()

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2024-05-15%2020%3A55%3A17 - REL_15_STABLE

Bailout called.  Further testing stopped:  pg_ctl stop failed
t/031_column_list.pl ............... ok

---
031_column_list_publisher.log
2024-05-16 00:23:24.522 UTC [1882382][walsender][5/22:0] LOG:  received replication command: CREATE_REPLICATION_SLOT "pg_16588_sync_16582_7369385153852978065" LOGICAL pgoutput (SNAPSHOT 'use')
2024-05-16 00:23:24.522 UTC [1882382][walsender][5/22:0] STATEMENT:  CREATE_REPLICATION_SLOT "pg_16588_sync_16582_7369385153852978065" LOGICAL pgoutput (SNAPSHOT 'use')
2024-05-16 00:23:24.639 UTC [1882382][walsender][5/22:0] LOG:  logical decoding found consistent point at 0/164A088
2024-05-16 00:23:24.639 UTC [1882382][walsender][5/22:0] DETAIL:  There are no running transactions.
2024-05-16 00:23:24.639 UTC [1882382][walsender][5/22:0] STATEMENT:  CREATE_REPLICATION_SLOT "pg_16588_sync_16582_7369385153852978065" LOGICAL pgoutput (SNAPSHOT 'use')
TRAP: FailedAssertion("TransactionIdPrecedesOrEquals(safeXid, snap->xmin)", File: "/home/bf/bf-build/skink/REL_15_STABLE/pgsql.build/../pgsql/src/backend/replication/logical/snapbuild.c", Line: 614, PID: 756819)
2024-05-09 07:11:55.444 UTC [756803][walsender][4/0:0] ERROR:  cannot use different column lists for table "public.test_mix_1" in different publications
2024-05-09 07:11:55.444 UTC [756803][walsender][4/0:0] CONTEXT:  slot "sub1", output plugin "pgoutput", in the change callback, associated LSN 0/163B860
2024-05-09 07:11:55.444 UTC [756803][walsender][4/0:0] STATEMENT:  START_REPLICATION SLOT "sub1" LOGICAL 0/0 (proto_version '3', publication_names '"pub_mix_1","pub_mix_2"')
postgres: publisher: walsender bf [local] CREATE_REPLICATION_SLOT(ExceptionalCondition+0x92)[0x6bc2db]
postgres: publisher: walsender bf [local] CREATE_REPLICATION_SLOT(SnapBuildInitialSnapshot+0x1fd)[0x521e82]
postgres: publisher: walsender bf [local] CREATE_REPLICATION_SLOT(+0x430bb1)[0x538bb1]
postgres: publisher: walsender bf [local] CREATE_REPLICATION_SLOT(exec_replication_command+0x3c9)[0x53ac9a]
postgres: publisher: walsender bf [local] CREATE_REPLICATION_SLOT(PostgresMain+0x748)[0x58f8f1]
postgres: publisher: walsender bf [local] CREATE_REPLICATION_SLOT(+0x3efabb)[0x4f7abb]
postgres: publisher: walsender bf [local] CREATE_REPLICATION_SLOT(+0x3f1bba)[0x4f9bba]
postgres: publisher: walsender bf [local] CREATE_REPLICATION_SLOT(+0x3f1dc8)[0x4f9dc8]
postgres: publisher: walsender bf [local] CREATE_REPLICATION_SLOT(PostmasterMain+0x1133)[0x4fb36b]
postgres: publisher: walsender bf [local] CREATE_REPLICATION_SLOT(main+0x210)[0x448be9]
/lib/x86_64-linux-gnu/libc.so.6(+0x27b8a)[0x4cd0b8a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85)[0x4cd0c45]
postgres: publisher: walsender bf [local] CREATE_REPLICATION_SLOT(_start+0x21)[0x1d2b71]
2024-05-09 07:11:55.588 UTC [747458][postmaster][:0] LOG:  server process (PID 756819) was terminated by signal 6: Aborted
2024-05-09 07:11:55.588 UTC [747458][postmaster][:0] DETAIL:  Failed process was running: CREATE_REPLICATION_SLOT "pg_16586_sync_16580_7366892877332646335" LOGICAL pgoutput (SNAPSHOT 'use')

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sidewinder&dt=2024-02-09%2012%3A46%3A37 - REL_15_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2024-05-09%2003%3A48%3A10 - REL_15_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2024-09-14%2013%3A22%3A59 - REL_15_STABLE

Assertion failure in SnapBuildInitialSnapshot()

Upgrade tests fail on Windows due to pg_upgrade_output.d/ not removed

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


  2/242 postgresql:pg_upgrade / pg_upgrade/004_subscription                             ERROR            98.04s   exit status 1

---
regress_log_004_subscription

Upgrade Complete
----------------
Optimizer statistics are not transferred by pg_upgrade.
Once you start the new server, consider running:
    C:/tools/nmsys64/home/pgrunner/bf/root/HEAD/PGSQL~1.BUI/TMP_IN~1/tools/nmsys64/home/pgrunner/bf/root/HEAD/inst/bin/vacuumdb --all --analyze-in-stages
Running this script will delete the old cluster's data files:
    delete_old_cluster.bat
pg_upgrade: warning: could not remove directory "C:/tools/nmsys64/home/pgrunner/bf/root/HEAD/pgsql.build/testrun/pg_upgrade/004_subscription/data/t_004_subscription_new_sub_data/pgdata/pg_upgrade_output.d/20240613T060900.667/log": Directory not empty
pg_upgrade: warning: could not remove directory "C:/tools/nmsys64/home/pgrunner/bf/root/HEAD/pgsql.build/testrun/pg_upgrade/004_subscription/data/t_004_subscription_new_sub_data/pgdata/pg_upgrade_output.d/20240613T060900.667": Directory not empty
pg_upgrade: warning: could not stat file "C:/tools/nmsys64/home/pgrunner/bf/root/HEAD/pgsql.build/testrun/pg_upgrade/004_subscription/data/t_004_subscription_new_sub_data/pgdata/pg_upgrade_output.d/20240613T060900.667/log/pg_upgrade_internal.log": No such file or directory
pg_upgrade: warning: could not remove directory "C:/tools/nmsys64/home/pgrunner/bf/root/HEAD/pgsql.build/testrun/pg_upgrade/004_subscription/data/t_004_subscription_new_sub_data/pgdata/pg_upgrade_output.d/20240613T060900.667/log": Directory not empty
pg_upgrade: warning: could not remove directory "C:/tools/nmsys64/home/pgrunner/bf/root/HEAD/pgsql.build/testrun/pg_upgrade/004_subscription/data/t_004_subscription_new_sub_data/pgdata/pg_upgrade_output.d/20240613T060900.667": Directory not empty
[06:09:33.510](34.360s) ok 8 - run of pg_upgrade for old instance when the subscription tables are in init/ready state
[06:09:33.510](0.000s) not ok 9 - pg_upgrade_output.d/ removed after successful pg_upgrade
[06:09:33.511](0.001s) #   Failed test 'pg_upgrade_output.d/ removed after successful pg_upgrade'
#   at C:/tools/nmsys64/home/pgrunner/bf/root/HEAD/pgsql/src/bin/pg_upgrade/t/004_subscription.pl line 265.

Also buildfarm's check-pg_upgrade fails on removing data.old

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2024-11-18%2013%3A51%3A55 - REL_12_STABLE

c:\\build-farm-local\\buildroot\\REL_12_STABLE\\pgsql.build\\src\\bin\\pg_upgrade>RMDIR /s/q "c:\\build-farm-local\\buildroot\\REL_12_STABLE\\pgsql.build\\src\\bin\\pg_upgrade\\tmp_check\\data.old" 
\203f\203B\203\214\203N\203g\203\212\202\252\213\363\202\305\202\315\202\240\202\350\202\334\202\271\202\361\201B

--- The last line is a Japanese message:
ディレクトリが空ではありません。
=
Directory not empty
encoded in SJIS.

pg_upgrade test failure \ the output directory remains after successful upgrade

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

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

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

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

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

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

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

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

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

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

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

Miscellaneous test failures in v14- on Windows due to "Permission denied" errors

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-06-24%2014%3A03%3A05 - REL_14_STABLE

============== shutting down postmaster               ==============
pg_ctl: could not open PID file "C:/tools/nmsys64/home/pgrunner/bf/root/REL_14_STABLE/pgsql.build/src/test/regress/./tmp_check/data/postmaster.pid": Permission denied

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2024-07-10%2002%3A27%3A04 - REL_13_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2024-07-10%2002%3A09%3A24 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2024-08-08%2001%3A11%3A00 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamerkop&dt=2024-08-08%2001%3A31%3A42 - REL_13_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-11-06%2011%3A03%3A06 - REL_12_STABLE

stat() vs ERROR_DELETE_PENDING, round N + 1 \ pushing fix e2f0f8ed2 to v15+

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

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

(mereswine is an armv7 machine)

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

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

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

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

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

infinite_recurse hitting OOM condititon on mereswine

Miscellaneous tests fail on Windows due to a connection closed before receiving a final error message

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-07-06%2015%3A16%3A39 - REL_15_STABLE

#   Failed test 'certificate authorization fails with revoked client cert with server-side CRL directory: matches'
#   at t/001_ssltests.pl line 742.
#                   'psql: error: connection to server at "127.0.0.1", port 57497 failed: server closed the connection unexpectedly
# 	This probably means the server terminated abnormally
# 	before or while processing the request.
# server closed the connection unexpectedly
# 	This probably means the server terminated abnormally
# 	before or while processing the request.'
#     doesn't match '(?^:SSL error: ssl[a-z0-9/]* alert certificate revoked)'
# Looks like you failed 1 test of 180.
[16:08:45] t/001_ssltests.pl .. 
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/180 subtests

Why is src/test/modules/committs/t/002_standby.pl flaky? \ A new attempt to fix this mess

031_recovery_conflict.pl test might fail due to late pgstat entries flushing

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

 23/296 postgresql:recovery / recovery/031_recovery_conflict                            ERROR            11.55s   exit status 1

---
regress_log_031_recovery_conflict
[07:58:53.979](0.255s) ok 11 - tablespace conflict: logfile contains terminated connection due to recovery conflict
[07:58:54.058](0.080s) not ok 12 - tablespace conflict: stats show conflict on standby
[07:58:54.059](0.000s) #   Failed test 'tablespace conflict: stats show conflict on standby'
#   at /home/bf/bf-build/rorqual/REL_17_STABLE/pgsql/src/test/recovery/t/031_recovery_conflict.pl line 332.
[07:58:54.059](0.000s) #          got: '0'
#     expected: '1'

The 031_recovery_conflict.pl test might fail due to late pgstat entries flushing

005_opclass_damage.pl fails on Windows animals due to timeout

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

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

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

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

fairywren timeout failures on the pg_amcheck/005_opclass_damage test

culicidae failed to restart server due to incorrect checksum in control file

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2024-07-24%2004%3A08%3A23 - REL_16_STABLE

(culicidae tests EXEC_BACKEND)

001_auth_node.log
2024-07-24 04:19:28.403 UTC [1018014][postmaster][:0] LOG:  starting PostgreSQL 16.3 on x86_64-linux, compiled by gcc-13.3.0, 64-bit
2024-07-24 04:19:28.427 UTC [1018014][postmaster][:0] LOG:  listening on Unix socket "/tmp/U3Osq_FaO8/.s.PGSQL.12427"
2024-07-24 04:19:29.036 UTC [1018564][startup][:0] LOG:  database system was shut down at 2024-07-24 04:19:27 UTC
2024-07-24 04:19:29.038 UTC [1018562][not initialized][:0] FATAL:  incorrect checksum in control file

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2024-11-07%2006%3A21%3A37 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2024-12-15%2020%3A29%3A49 - REL_16_STABLE

Also culicidae failed regression test due to incorrect checksum

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2024-08-17%2001%3A12%3A50 - HEAD

\342\226\266 1/1 + partition_prune                          3736 ms FAIL          

---
inst/logfile
2024-08-17 01:25:31.254 UTC [2841385][client backend][43/184:0] LOG:  connection authorized: user=buildfarm database=regression application_name=pg_regress/partition_prune
...
2024-08-17 01:25:33.676 UTC [2842326][not initialized][:0] FATAL:  incorrect checksum in control file
...
2024-08-17 01:25:33.683 UTC [2841385][client backend][43/553:0] ERROR:  parallel worker failed to initialize
2024-08-17 01:25:33.683 UTC [2841385][client backend][43/553:0] HINT:  More details may be available in the server log.
2024-08-17 01:25:33.683 UTC [2841385][client backend][43/553:0] CONTEXT:  PL/pgSQL function explain_parallel_append(text) line 5 at FOR over EXECUTE statement
2024-08-17 01:25:33.683 UTC [2841385][client backend][43/553:0] STATEMENT:  select explain_parallel_append('select avg(ab.a) from ab inner join lprt_a a on ab.a = a.a where a.a in(1, 0, 0)');

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2025-01-24%2018%3A22%3A01 - master

race condition when writing pg_control \ the issue in question apparently happened in the wild

stats.sql is failing sporadically in v14- on POWER/aarch64 animals

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sungazer&dt=2024-07-30%2003%3A49%3A35 - REL_14_STABLE

test stats                        ... FAILED   469155 ms
...
--- /home/nm/farm/gcc64/REL_14_STABLE/pgsql.build/src/test/regress/expected/stats.out 2022-03-30 01:18:17.000000000 +0000
+++ /home/nm/farm/gcc64/REL_14_STABLE/pgsql.build/src/test/regress/results/stats.out 2024-07-30 09:49:39.000000000 +0000
@@ -165,11 +165,11 @@
    WHERE relname like 'trunc_stats_test%' order by relname;
         relname      | n_tup_ins | n_tup_upd | n_tup_del | n_live_tup | n_dead_tup
-------------------+-----------+-----------+-----------+------------+------------
-  trunc_stats_test  |         3 |         0 |         0 | 0 |          0
-  trunc_stats_test1 |         4 |         2 |         1 | 1 |          0
-  trunc_stats_test2 |         1 |         0 |         0 | 1 |          0
-  trunc_stats_test3 |         4 |         0 |         0 | 2 |          2
-  trunc_stats_test4 |         2 |         0 |         0 | 0 |          2
+  trunc_stats_test  |         0 |         0 |         0 | 0 |          0
+  trunc_stats_test1 |         0 |         0 |         0 | 0 |          0
+  trunc_stats_test2 |         0 |         0 |         0 | 0 |          0
+  trunc_stats_test3 |         0 |         0 |         0 | 0 |          0
+  trunc_stats_test4 |         0 |         0 |         0 | 0 |          0
...


---
inst/logfile
2024-07-30 09:25:11.225 UTC [63307946:1] LOG:  using stale statistics instead of current ones because stats collector is 
not responding
2024-07-30 09:25:11.345 UTC [11206724:559] pg_regress/create_index LOG:  using stale statistics instead of current ones 
because stats collector is not responding
...

The stats.sql test is failing sporadically in v14- on POWER7/AIX 7.1 buildfarm animals

pg_ctl stop/start fails on Windows due to inconsistent check for postmaster.pid existence

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-08-19%2017%3A32%3A54 - HEAD

...
pg_createsubscriber: stopping the subscriber
2024-08-19 18:02:47.608 UTC [6988:4] LOG:  received fast shutdown request
2024-08-19 18:02:47.608 UTC [6988:5] LOG:  aborting any active transactions
2024-08-19 18:02:47.612 UTC [5884:2] FATAL:  terminating walreceiver process due to administrator command
2024-08-19 18:02:47.705 UTC [7036:1] LOG:  shutting down
pg_createsubscriber: server was stopped
...
[18:02:47.900](2.828s) ok 29 - run pg_createsubscriber without --databases
...
pg_createsubscriber: starting the standby with command-line options
pg_createsubscriber: pg_ctl command is: ...
2024-08-19 18:02:48.163 UTC [5284:1] FATAL:  could not create lock file "postmaster.pid": File exists
pg_createsubscriber: server was started
pg_createsubscriber: checking settings on subscriber
2024-08-19 18:02:48.484 UTC [6988:6] LOG:  database system is shut down

DELETE PENDING strikes back, via pg_ctl stop/start

pg_ctl stop fails on Cygwin due to DELETE PENDING state of postmaster.pid

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=lorikeet&dt=2024-08-22%2009%3A52%3A46 - HEAD

waiting for server to shut down........pg_ctl: could not open PID file "data-C/postmaster.pid": Permission denied

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=lorikeet&dt=2024-11-11%2011%3A26%3A06 - master

DELETE PENDING strikes back, via pg_ctl stop/start \ a lorikeet failure

dblink.sql (and postgres_fdw.sql) fail on Windows due to the cancel packet not sent

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-08-26%2021%3A35%3A04 - REL_17_STABLE

40/67 postgresql:dblink-running / dblink-running/regress                           ERROR            32.97s   exit status 1

---
pgsql.build/testrun/dblink-running/regress/regression.diffs
 SELECT dblink_cancel_query('dtest1');
- dblink_cancel_query 
----------------------
- OK
+   dblink_cancel_query    
+--------------------------
+ cancel request timed out
 (1 row)

Add non-blocking version of PQcancel \ the dblink test failed on drongo

timeouts.spec failed because of statement cancelled due to unexpected reason

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mylodon&dt=2024-08-30%2023%3A03%3A31 - REL_16_STABLE

257/260 postgresql:isolation / isolation/isolation                                ERROR            79.90s   exit status 1

---
pgsql.build/testrun/isolation/isolation/regression.diffs
--- /home/bf/bf-build/mylodon/REL_16_STABLE/pgsql/src/test/isolation/expected/timeouts.out	2023-06-30 00:57:49.207140401 +0000
+++ /home/bf/bf-build/mylodon/REL_16_STABLE/pgsql.build/testrun/isolation/isolation/results/timeouts.out	2024-08-30 23:06:07.610042527 +0000
@@ -78,4 +78,4 @@
 step slto: SET lock_timeout = '10s'; SET statement_timeout = '10ms';
 step update: DELETE FROM accounts WHERE accountid = 'checking'; <waiting ...>
 step update: <... completed>
-ERROR:  canceling statement due to statement timeout
+ERROR:  canceling statement due to user request

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=flaviventris&dt=2025-02-11%2021%3A54%3A52 - master

Add non-blocking version of PQcancel \ mylodon failed due to reason discussed upthread

002_archiving.pl fails due to promote request not received timely on Windows

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-09-29%2015%3A30%3A27 - REL_17_STABLE

(drongo is a Windows animal)

  6/289 postgresql:recovery / recovery/002_archiving                                    ERROR           626.63s   (exit status 255 or signal 127 SIGinvalid)

---
regress_log_002_archiving
[17:11:11.519](0.001s) ok 3 - recovery_end_command not executed yet
### Promoting node "standby"
# Running: pg_ctl -D C:\\prog\\bf\\root\\REL_17_STABLE\\pgsql.build/testrun/recovery/002_archiving\\data/t_002_archiving_standby_data/pgdata -l C:\\prog\\bf\\root\\REL_17_STABLE\\pgsql.build/testrun/recovery/002_archiving\\log/002_archiving_standby.log promote
waiting for server to promote....................................................................................................................................................................................... stopped waiting
pg_ctl: server did not promote in time
[17:20:06.095](534.576s) Bail out!  command "pg_ctl -D C:\\prog\\bf\\root\\REL_17_STABLE\\pgsql.build/testrun/recovery/002_archiving\\data/t_002_archiving_standby_data/pgdata -l C:\\prog\\bf\\root\\REL_17_STABLE\\pgsql.build/testrun/recovery/002_archiving\\log/002_archiving_standby.log promote" exited with value 1

---
002_archiving_standby.log
2024-09-29 17:11:10.319 UTC [6408:3] LOG:  recovery restart point at 0/3028BF8
2024-09-29 17:11:10.319 UTC [6408:4] DETAIL:  Last completed transaction was at log time 2024-09-29 17:10:57.783965+00.
The system cannot find the file specified.
2024-09-29 17:11:10.719 UTC [7440:5] 002_archiving.pl LOG:  disconnection: session time: 0:00:00.488 user=pgrunner database=postgres host=127.0.0.1 port=62549
The system cannot find the file specified.
The system cannot find the file specified.
...
The system cannot find the file specified.
2024-09-29 17:20:08.237 UTC [6684:4] LOG:  received immediate shutdown request
The system cannot find the file specified.
...

(there is no "received promote request" message)

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-06-28%2001%3A06%3A00 - REL_16_STABLE

promote request not received timely on slow Windows machines

019_replslot_limit.pl fails due to walsender stuck on sending FATAL to frozen walreceiver

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=francolin&dt=2024-10-03%2012%3A51%3A32 - REL_17_STABLE

297/297 postgresql:recovery / recovery/019_replslot_limit                               ERROR           306.28s   exit status 29

---
regress_log_019_replslot_limit
[12:56:34.033](0.228s) ok 19 - walsender termination logged
[13:00:57.133](263.100s) # poll_query_until timed out executing this query:
# SELECT wal_status FROM pg_replication_slots WHERE slot_name = 'rep3'
# expecting this output:
# lost
# last actual query output:
# unreserved
# with stderr:
timed out waiting for slot to be lost at /home/bf/bf-build/francolin/REL_17_STABLE/pgsql/src/test/recovery/t/019_replslot_limit.pl line 388.

---
019_replslot_limit_primary3.log
2024-10-03 12:56:34.041 UTC [673987] standby_3 FATAL:  terminating connection due to administrator command
2024-10-03 12:56:34.041 UTC [673987] standby_3 STATEMENT:  START_REPLICATION SLOT "rep3" 0/800000 TIMELINE 1
2024-10-03 12:56:34.066 UTC [674545] 019_replslot_limit.pl LOG:  statement: SELECT wal_status FROM pg_replication_slots WHERE slot_name = 'rep3'
2024-10-03 12:56:34.238 UTC [674628] 019_replslot_limit.pl LOG:  statement: SELECT wal_status FROM pg_replication_slots WHERE slot_name = 'rep3'
...

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mylodon&dt=2023-04-05%2017%3A47%3A03 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=kestrel&dt=2024-02-04%2001%3A53%3A44 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=piculet&dt=2025-02-19%2021%3A45%3A45 - REL_17_STABLE

failure in 019_replslot_limit

027_stream_regress.pl failed on drongo due to walreceiver not reconnecting after primary restart

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-10-14%2010%3A08%3A17 - master

(drongo is a Windows animal)

166/294 postgresql:recovery / recovery/027_stream_regress                               ERROR           871.81s   exit status 25

---
regress_log_027_stream_regress
Waiting for replication conn standby_1's replay_lsn to pass 0/158C8B98 on primary
[10:41:32.115](661.161s) # poll_query_until timed out executing this query:
# SELECT '0/158C8B98' <= replay_lsn AND state = 'streaming'
#          FROM pg_catalog.pg_stat_replication
#          WHERE application_name IN ('standby_1', 'walreceiver')
# expecting this output:
# t
# last actual query output:
#


---
027_stream_regress_standby_1.log
2024-10-14 10:30:28.483 UTC [4320:12] 027_stream_regress.pl LOG: disconnection: session time: 0:00:03.793 user=pgrunner 
database=postgres host=127.0.0.1 port=61748
2024-10-14 10:30:31.442 UTC [8468:2] LOG:  replication terminated by primary server
2024-10-14 10:30:31.442 UTC [8468:3] DETAIL:  End of WAL reached on timeline 1 at 0/158C8B98.
2024-10-14 10:30:31.442 UTC [8468:4] FATAL:  could not send end-of-streaming message to primary: server closed the 
connection unexpectedly
         This probably means the server terminated abnormally
         before or while processing the request.
     no COPY in progress
2024-10-14 10:30:31.443 UTC [5452:7] LOG:  invalid resource manager ID 101 at 0/158C8B98
2024-10-14 10:35:06.986 UTC [8648:21] LOG:  restartpoint starting: time
2024-10-14 10:35:06.991 UTC [8648:22] LOG:  restartpoint complete: wrote 0 buffers (0.0%), wrote 1 SLRU buffers; 0 WAL 
file(s) added, 0 removed, 1 recycled; write=0.001 s, sync=0.001 s, total=0.005 s; sync files=0, longest=0.000 s, 
average=0.000 s; distance=15336 kB, estimate=69375 kB; lsn=0/158C8B20, redo lsn=0/158C8B20
2024-10-14 10:35:06.991 UTC [8648:23] LOG:  recovery restart point at 0/158C8B20
2024-10-14 10:35:06.991 UTC [8648:24] DETAIL:  Last completed transaction was at log time 2024-10-14 10:30:24.820804+00.
2024-10-14 10:41:32.510 UTC [4220:4] LOG:  received immediate shutdown request

Also 001_rep_changes.pl failed on fairywren due to walreceiver not reconnecting after primary restart

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-11-15%2015%3A23%3A29 - REL_15_STABLE

+++ tap check in src/test/subscription +++
# poll_query_until timed out executing this query:
# SELECT '0/1534000' <= replay_lsn AND state = 'streaming'
#          FROM pg_catalog.pg_stat_replication
#          WHERE application_name IN ('tap_sub', 'walreceiver')
# expecting this output:
# t
# last actual query output:
# 
# with stderr:
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 25 just after 23.
[16:07:39] t/001_rep_changes.pl ............... 
Dubious, test returned 25 (wstat 6400, 0x1900)

---
pgsql.build/src/test/subscription/tmp_check/log/001_rep_changes_publisher.log
2024-11-15 16:00:58.066 UTC [8716:3] 001_rep_changes.pl LOG:  statement: DELETE FROM tab_rep
2024-11-15 16:00:58.068 UTC [8716:4] 001_rep_changes.pl LOG:  disconnection: session time: 0:00:00.010 user=pgrunner database=postgres host=[local]
2024-11-15 16:00:58.109 UTC [3628:4] LOG:  received fast shutdown request
2024-11-15 16:00:58.109 UTC [3628:5] LOG:  aborting any active transactions
2024-11-15 16:00:58.121 UTC [3628:6] LOG:  background worker "logical replication launcher" (PID 8756) exited with exit code 1
2024-11-15 16:00:58.121 UTC [6480:1] LOG:  shutting down
2024-11-15 16:00:58.392 UTC [7740:14] tap_sub LOG:  disconnection: session time: 0:00:00.682 user=pgrunner database=postgres host=[local]
2024-11-15 16:00:58.421 UTC [6480:2] LOG:  checkpoint starting: shutdown immediate
2024-11-15 16:00:58.477 UTC [6480:3] LOG:  checkpoint complete: wrote 9 buffers (7.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.057 s; sync files=0, longest=0.000 s, average=0.000 s; distance=617 kB, estimate=617 kB
2024-11-15 16:00:58.486 UTC [3628:7] LOG:  database system is shut down
2024-11-15 16:00:58.741 UTC [8864:1] LOG:  starting PostgreSQL 15.9 on x86_64-w64-mingw32, compiled by gcc.exe (Rev3, Built by MSYS2 project) 14.1.0, 64-bit

---
pgsql.build/src/test/subscription/tmp_check/log/001_rep_changes_subscriber.log
2024-11-15 16:00:57.692 UTC [5512:1] LOG:  logical replication apply worker for subscription "tap_sub" has started
2024-11-15 16:00:58.394 UTC [5512:2] LOG:  data stream from publisher has ended
2024-11-15 16:00:58.394 UTC [5512:3] ERROR:  could not send end-of-streaming message to primary: server closed the connection unexpectedly
		This probably means the server terminated abnormally
		before or while processing the request.
	no COPY in progress
2024-11-15 16:00:58.405 UTC [4848:9] LOG:  background worker "logical replication worker" (PID 5512) exited with exit code 1
2024-11-15 16:00:58.483 UTC [2204:1] LOG:  logical replication apply worker for subscription "tap_sub" has started
2024-11-15 16:05:33.567 UTC [5260:1] LOG:  checkpoint starting: time

Also 021_twophase.pl failed on fairywren due to walreceiver not reconnecting after primary restart

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2024-12-25%2014%3A03%3A06 - master

[14:23:23.860](1.196s) ok 9 - Rows inserted via 2PC are visible on the subscriber
### Stopping node "publisher" using mode immediate
# Running: pg_ctl -D C:\\tools\\xmsys64\\home\\pgrunner\\bf\\root\\HEAD\\pgsql.build/testrun/subscription/021_twophase/data/t_021_twophase_publisher_data/pgdata -m immediate stop
waiting for server to shut down.... done
server stopped
# No postmaster PID for node "publisher"
### Starting node "publisher"
# Running: pg_ctl -w -D C:\\tools\\xmsys64\\home\\pgrunner\\bf\\root\\HEAD\\pgsql.build/testrun/subscription/021_twophase/data/t_021_twophase_publisher_data/pgdata -l C:\\tools\\xmsys64\\home\\pgrunner\\bf\\root\\HEAD\\pgsql.build/testrun/subscription/021_twophase/log/021_twophase_publisher.log -o --cluster-name=publisher start
waiting for server to start.... done
server started
# Postmaster PID for node "publisher" is 8896
Waiting for replication conn tap_sub's replay_lsn to pass 0/178D688 on publisher
[14:31:05.104](461.244s) # poll_query_until timed out executing this query:
# SELECT '0/178D688' <= replay_lsn AND state = 'streaming'
#          FROM pg_catalog.pg_stat_replication
#          WHERE application_name IN ('tap_sub', 'walreceiver')
# expecting this output:
# t
# last actual query output:
# 
# with stderr:
[14:31:05.241](0.137s) # Last pg_stat_replication contents:
timed out waiting for catchup at C:/tools/xmsys64/home/pgrunner/bf/root/HEAD/pgsql/src/test/subscription/t/021_twophase.pl line 242.


---
pgsql.build/testrun/subscription/021_twophase/log/021_twophase_subscriber.log
2024-12-25 14:23:24.064 UTC [4168:2] 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.
2024-12-25 14:23:24.115 UTC [6164:1] LOG:  logical replication apply worker for subscription "tap_sub" has started
2024-12-25 14:23:24.120 UTC [5256:4] LOG:  background worker "logical replication apply worker" (PID 4168) exited with exit code 1
2024-12-25 14:28:23.097 UTC [276:4] LOG:  checkpoint starting: time
2024-12-25 14:28:23.430 UTC [276:5] LOG:  1 two-phase state file was written for a long-running prepared transaction
2024-12-25 14:28:23.431 UTC [276:6] LOG:  checkpoint complete: wrote 3 buffers (0.0%), wrote 1 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.326 s, sync=0.001 s, total=0.334 s; sync files=0, longest=0.000 s, average=0.000 s; distance=8 kB, estimate=8 kB; lsn=0/178C418, redo lsn=0/178C3F8
2024-12-25 14:31:05.415 UTC [5256:5] LOG:  received immediate shutdown request

WaitEventSetWaitBlock() can still hang on Windows due to connection reset

pageinspect/page.sql fails in v14- due to freeze requested not happening

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-11-09%2004%3A18%3A56 - REL_14_STABLE

============== creating database "contrib_regression" ==============
...
test page                         ... FAILED      401 ms
...
---
pgsql.build/contrib/pageinspect/regression.diffs

--- C:/prog/bf/root/REL_14_STABLE/pgsql.build/contrib/pageinspect/expected/page.out	2024-09-14 14:59:50.899122300 +0000
+++ C:/prog/bf/root/REL_14_STABLE/pgsql.build/contrib/pageinspect/results/page.out	2024-11-09 05:16:52.027703100 +0000
@@ -93,8 +93,8 @@
 FROM heap_page_items(get_raw_page('test1', 0)),
      LATERAL heap_tuple_infomask_flags(t_infomask, t_infomask2);
  t_infomask | t_infomask2 |                         raw_flags                         |   combined_flags   
-------------+-------------+-----------------------------------------------------------+--------------------
-       2816 |           2 | {HEAP_XMIN_COMMITTED,HEAP_XMIN_INVALID,HEAP_XMAX_INVALID} | {HEAP_XMIN_FROZEN}
+------------+-------------+-----------------------------------------+----------------
+       2304 |           2 | {HEAP_XMIN_COMMITTED,HEAP_XMAX_INVALID} | {}
 (1 row)

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hornet&dt=2025-02-01%2004%3A57%3A21 - REL_13_STABLE

Revert "Prevent instability in contrib/pageinspect's regression test."

deadlock-soft.sql is failing on newest Fedora

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

not ok 24    - deadlock-soft                          741086 ms

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

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

deadlock-soft isolation test is failing on newest Fedora

ssl tests still have opportunity to fail due to TCP port conflict

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2024-11-21%2020%3A44%3A43 - master

296/305 postgresql:subscription / subscription/100_bugs                                 OK               26.74s   14 subtests passed
\342\226\266 297/305 pg_ctl restart failed                                                         ERROR         
297/305 postgresql:ssl / ssl/002_scram                                                  ERROR             5.96s   (exit status 255 or signal 127 SIGinvalid)
...

---
regress_log_002_scram
### Restarting node "primary"
# Running: pg_ctl -w -D /home/bf/bf-build/culicidae/HEAD/pgsql.build/testrun/ssl/002_scram/data/t_002_scram_primary_data/pgdata -l /home/bf/bf-build/culicidae/HEAD/pgsql.build/testrun/ssl/002_scram/log/002_scram_primary.log restart
waiting for server to shut down..... done
server stopped
waiting for server to start.... stopped waiting
pg_ctl: could not start server
Examine the log output.
# pg_ctl restart failed; see logfile for details: /home/bf/bf-build/culicidae/HEAD/pgsql.build/testrun/ssl/002_scram/log/002_scram_primary.log
# No postmaster PID for node "primary"
[20:57:30.208](5.688s) Bail out!  pg_ctl restart failed

---
002_scram_primary.log
2024-11-21 20:57:28.783 UTC [4067616][postmaster][:0] LOG:  received fast shutdown request
2024-11-21 20:57:28.803 UTC [4067616][postmaster][:0] LOG:  aborting any active transactions
2024-11-21 20:57:28.818 UTC [4067616][postmaster][:0] LOG:  background worker "logical replication launcher" (PID 4067783) exited with exit code 1
2024-11-21 20:57:28.825 UTC [4067730][checkpointer][:0] LOG:  shutting down
2024-11-21 20:57:28.835 UTC [4067730][checkpointer][:0] LOG:  checkpoint starting: shutdown immediate
2024-11-21 20:57:30.050 UTC [4067730][checkpointer][:0] LOG:  checkpoint complete: wrote 5713 buffers (34.9%), wrote 3 SLRU buffers; 0 WAL file(s) added, 0 removed, 3 recycled; write=0.964 s, sync=0.103 s, total=1.220 s; sync files=1797, longest=0.030 s, average=0.001 s; distance=46011 kB, estimate=46011 kB; lsn=0/4474998, redo lsn=0/4474998
2024-11-21 20:57:30.094 UTC [4067616][postmaster][:0] LOG:  database system is shut down
2024-11-21 20:57:30.175 UTC [4070346][postmaster][:0] LOG:  starting PostgreSQL 18devel on x86_64-linux, compiled by gcc-14.2.0, 64-bit
2024-11-21 20:57:30.175 UTC [4070346][postmaster][:0] LOG:  could not bind IPv4 address "127.0.0.1": Address already in use
2024-11-21 20:57:30.175 UTC [4070346][postmaster][:0] HINT:  Is another postmaster already running on port 32301? If not, wait a few seconds and retry.
2024-11-21 20:57:30.175 UTC [4070346][postmaster][:0] WARNING:  could not create listen socket for "127.0.0.1"
2024-11-21 20:57:30.175 UTC [4070346][postmaster][:0] FATAL:  could not create any TCP/IP sockets

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=olingo&dt=2025-02-19%2004%3A57%3A22 - master

ssl tests fail due to TCP port conflict \ substantially reduce buildfarm failures

Parallel tests publication and subscription might fail due to concurrent tuple update

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=desman&dt=2024-12-09%2018%3A33%3A49 - REL_16_STABLE

# parallel group (2 tests):  subscription publication
not ok 157   + publication                              2251 ms
ok 158       + subscription                              415 ms


--- /home/fedora/17-desman/buildroot/REL_16_STABLE/pgsql.build/src/test/regress/expected/publication.out 2024-12-09 
18:34:02.939762233 +0000
+++ /home/fedora/17-desman/buildroot/REL_16_STABLE/pgsql.build/src/test/regress/results/publication.out 2024-12-09 
18:44:48.582958859 +0000
@@ -1193,23 +1193,29 @@
  ERROR:  permission denied for database regression
  SET ROLE regress_publication_user;
  GRANT CREATE ON DATABASE regression TO regress_publication_user2;
+ERROR:  tuple concurrently updated
  SET ROLE regress_publication_user2;
  SET client_min_messages = 'ERROR';
  CREATE PUBLICATION testpub2;  -- ok
+ERROR:  permission denied for database regression

---
pgsql.build/src/test/regress/log/postmaster.log
2024-12-09 18:44:46.753 UTC [1345157:903] pg_regress/publication STATEMENT:  CREATE PUBLICATION testpub2;
2024-12-09 18:44:46.753 UTC [1345158:287] pg_regress/subscription LOG:  statement: REVOKE CREATE ON DATABASE REGRESSION 
FROM regress_subscription_user3;
2024-12-09 18:44:46.754 UTC [1345157:904] pg_regress/publication LOG:  statement: SET ROLE regress_publication_user;
2024-12-09 18:44:46.754 UTC [1345157:905] pg_regress/publication LOG:  statement: GRANT CREATE ON DATABASE regression TO 
regress_publication_user2;
2024-12-09 18:44:46.754 UTC [1345157:906] pg_regress/publication ERROR:  tuple concurrently updated
2024-12-09 18:44:46.754 UTC [1345157:907] pg_regress/publication STATEMENT:  GRANT CREATE ON DATABASE regression TO 
regress_publication_user2;

Parallel tests publication and subscription might fail due to concurrent tuple update

019_replslot_limit.pl might fail due to checkpoint skipped

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=alligator&dt=2024-12-13%2001%3A24%3A58 - REL_17_STABLE

[12:27:41.437](0.024s) ok 18 - have walreceiver pid 637143
[12:30:42.564](181.127s) not ok 19 - walsender termination logged
[12:30:42.564](0.000s)
[12:30:42.564](0.000s) #   Failed test 'walsender termination logged'
#   at t/019_replslot_limit.pl line 382.


---
019_replslot_limit_primary3.log:
2024-12-13 12:27:40.912 ACDT [637093:7] LOG:  checkpoint starting: wal
...
2024-12-13 12:27:41.461 ACDT [637182:4] 019_replslot_limit.pl LOG: statement: SELECT pg_logical_emit_message(false, '', 
'foo');
2024-12-13 12:27:41.462 ACDT [637182:5] 019_replslot_limit.pl LOG: statement: SELECT pg_switch_wal();
2024-12-13 12:27:41.463 ACDT [637182:6] 019_replslot_limit.pl LOG: disconnection: session time: 0:00:00.003 
user=postgres database=postgres host=[local]
2024-12-13 12:27:41.668 ACDT [637093:8] LOG:  checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 1 
removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.756 s; sync files=0, longest=0.000 s, average=0.000 s; 
distance=1024 kB, estimate=1024 kB; lsn=0/900060, redo lsn=0/700028
2024-12-13 12:27:41.668 ACDT [637093:9] LOG:  checkpoints are occurring too frequently (1 second apart)
2024-12-13 12:27:41.668 ACDT [637093:10] HINT:  Consider increasing the configuration parameter "max_wal_size".
2024-12-13 12:30:42.565 ACDT [637144:10] standby_3 LOG:  terminating walsender process due to replication timeout
2024-12-13 12:30:42.565 ACDT [637144:11] standby_3 STATEMENT: START_REPLICATION SLOT "rep3" 0/700000 TIMELINE 1

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=alligator&dt=2025-01-30%2021%3A03%3A27 - REL_16_STABLE

019_replslot_limit.pl might fail due to checkpoint skipped

tablespace.sql is unstable due to lack of ORDER BY (in v15-)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mandrill&dt=2024-12-25%2011%3A01%3A58 - REL_15_STABLE

#   Failed test 'regression tests pass'
#   at t/027_stream_regress.pl line 81.
#          got: '256'
#     expected: '0'
# Looks like you failed 1 test of 8.
[17:36:30] t/027_stream_regress.pl .............. 

---
pgsql.build/src/test/recovery/tmp_check/log/regress_log_027_stream_regress
test tablespace                   ... FAILED    47555 ms

diff -U3 /home/nm/farm/xlc32/REL_15_STABLE/pgsql.build/src/test/regress/expected/tablespace.out /home/nm/farm/xlc32/REL_15_STABLE/pgsql.build/src/test/recovery/tmp_check/results/tablespace.out
--- /home/nm/farm/xlc32/REL_15_STABLE/pgsql.build/src/test/regress/expected/tablespace.out	2024-11-26 05:26:30.000000000 +0000
+++ /home/nm/farm/xlc32/REL_15_STABLE/pgsql.build/src/test/recovery/tmp_check/results/tablespace.out	2024-12-25 17:13:47.000000000 +0000
@@ -334,9 +334,9 @@
      where c.reltablespace = t.oid AND c.relname LIKE 'part%_idx';
     relname   |     spcname      
  -------------+------------------
+  part_a_idx  | regress_tblspace
   part1_a_idx | regress_tblspace
   part2_a_idx | regress_tblspace
-  part_a_idx  | regress_tblspace
  (3 rows)

Unstable regression test "tablespace" / Add ORDER BY to stabilize tablespace test for partitioned index

stats.sql might fail due to shared buffers also used by parallel tests

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2024-12-17%2008%3A59%3A44 - master

--- C:/prog/bf/root/HEAD/pgsql/src/test/regress/expected/stats.out	2024-09-18 19:31:14.665516500 +0000
+++ C:/prog/bf/root/HEAD/pgsql.build/testrun/recovery/027_stream_regress/data/results/stats.out	2024-12-17 09:57:08.944588500 +0000
@@ -1291,7 +1291,7 @@
 SELECT :io_sum_shared_after_writes > :io_sum_shared_before_writes;
  ?column? 
 ----------
- t
+ f
 (1 row)

---
pgsql.build/testrun/recovery/027_stream_regress/log/027_stream_regress_primary.log
2024-12-17 09:57:06.782 UTC [8568:115] pg_regress/stats LOG:  statement: CHECKPOINT;
2024-12-17 09:57:06.794 UTC [3664:40] LOG:  checkpoint starting: immediate force wait
2024-12-17 09:57:06.856 UTC [3664:41] LOG:  checkpoint complete: wrote 0 buffers (0.0%), wrote 1 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.062 s; sync files=0, longest=0.000 s, average=0.000 s; distance=1875 kB, estimate=52682 kB; lsn=0/14A2F410, redo lsn=0/14A2F3B8
2024-12-17 09:57:06.857 UTC [8568:116] pg_regress/stats LOG:  statement: CHECKPOINT;
2024-12-17 09:57:06.857 UTC [3664:42] LOG:  checkpoint starting: immediate force wait
2024-12-17 09:57:06.859 UTC [3664:43] LOG:  checkpoint complete: wrote 0 buffers (0.0%), wrote 0 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.002 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=47414 kB; lsn=0/14A2F4E0, redo lsn=0/14A2F488
2024-12-17 09:57:06.859 UTC [8568:117] pg_regress/stats LOG:  statement: SELECT sum(writes) AS writes, sum(fsyncs) AS fsyncs
	  FROM pg_stat_io
	  WHERE object = 'relation' 
2024-12-17 09:57:06.860 UTC [8568:118] pg_regress/stats LOG:  statement: SELECT 77693 > 77693;

stats.sql might fail due to shared buffers also used by parallel tests

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

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

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

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

test_decoding/slot_creation_error.spec fails due to timing issue

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-02-06%2001%3A19%3A14 - master

--- C:/prog/bf/root/HEAD/pgsql/contrib/test_decoding/expected/slot_creation_error.out	2023-01-23 04:39:00.502404900 +0000
+++ C:/prog/bf/root/HEAD/pgsql.build/testrun/test_decoding/isolation/results/slot_creation_error.out	2025-02-06 02:43:51.979727000 +0000
@@ -92,23 +92,7 @@
     FROM pg_stat_activity
     WHERE application_name = 'isolation/slot_creation_error/s2';
  <waiting ...>
-step s2_init: <... completed>
-FATAL:  terminating connection due to administrator command
-server closed the connection unexpectedly
+PQconsumeInput failed: server closed the connection unexpectedly
 	This probably means the server terminated abnormally
 	before or while processing the request.
 
-step s1_terminate_s2: <... completed>
-pg_terminate_backend
---------------------
-t                   
-(1 row)
-
-step s1_c: COMMIT;
-step s1_view_slot: 
-    SELECT slot_name, slot_type, active FROM pg_replication_slots WHERE slot_name = 'slot_creation_error'
-
-slot_name|slot_type|active
----------+---------+------
-(0 rows)
-

Other occurrences:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2025-02-13%2015%3A24%3A51 - REL_16_STABLE

Improving tracking/processing of buildfarm test failures \ failure of slot_creation_error

014_binary.pl might fail when apply worker starts only after timeout of 180 seconds

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=snakefly&dt=2025-02-09%2011%3A45%3A05 - master


[12:04:20.537](1.318s) ok 7 - check synced data on subscriber with custom type
timed out waiting for match: (?^:ERROR: ( [A-Z0-9]+:)? incorrect binary data format) at t/014_binary.pl line 269.
# Postmaster PID for node "publisher" is 28332
### Stopping node "publisher" using mode immediate
...
[12:07:20.933](180.395s) # Tests were run but no plan was declared and done_testing() was not seen.

---
pgsql.build/src/test/subscription/tmp_check/log/014_binary_subscriber.log
2025-02-09 12:04:20.554 UTC [28531:4] 014_binary.pl LOG:  statement: CREATE TABLE public.test_mismatching_types (
	        a int PRIMARY KEY
	    );
2025-02-09 12:04:20.556 UTC [28531:5] 014_binary.pl LOG:  statement: ALTER SUBSCRIPTION tsub REFRESH PUBLICATION;
2025-02-09 12:04:20.568 UTC [28531:6] 014_binary.pl LOG:  disconnection: session time: 0:00:00.015 user=postgres database=postgres host=[local]
2025-02-09 12:07:20.629 UTC [28561:1] LOG:  logical replication apply worker for subscription "tsub" has started
2025-02-09 12:07:20.636 UTC [28563:1] LOG:  logical replication table synchronization worker for subscription "tsub", table "test_mismatching_types" has started
2025-02-09 12:07:20.659 UTC [28563:2] ERROR:  incorrect binary data format
2025-02-09 12:07:20.659 UTC [28563:3] CONTEXT:  COPY test_mismatching_types, line 1, column a
2025-02-09 12:07:20.660 UTC [28344:7] LOG:  background worker "logical replication tablesync worker" (PID 28563) exited with exit code 1

Improving the latch handling between logical replication launcher and worker processes. \ race condition between DEFAULT_NAPTIME_PER_CYCLE and $timeout_default

Fixed Test Failures

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

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

(indri is a macOS animal)

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

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

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

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

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

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

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

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

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

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

Lower default value of autovacuum_worker_slots in initdb as needed.

XversionUpgrade fails with pg_dump error after e65dbc992

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

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

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

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

Fix buildfarm failure introduced by commit e65dbc9927.

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

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

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

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

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

Fix instability in recently added regression tests

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

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

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

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

Fix check_install_is_complete

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

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

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

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

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

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

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

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

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

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

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

Also new test t_001_test_escape fails on ARM animals

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

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

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

(no link to the public discussion)

Fix type in test_escape test

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

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

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

(no link to the public discussion)

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

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

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

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

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

(no link to the public discussion)

adjust to upstream API change

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

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

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

New buildfarm animals with FIPS mode enabled

New buildfarm animals with FIPS mode enabled \ these animals stopped

initdb fails on Valgrind-enabled animal (after 925682260)

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

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

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

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

Fix explicit valgrind interaction in read_stream.c.

Testing timed out on check stage (after 6a2275b89)

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

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

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

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

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

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

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

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

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

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

Get rid of WALBufMappingLock \ BF failure spotted

Revert: Get rid of WALBufMappingLock

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

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

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

...

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

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

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

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

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


not ok 3     - cached-plan-inval                      536538 ms

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

Remove unstable test suite added by 525392d57

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

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

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

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

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

Trial fix for old cross-version upgrades.

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

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

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

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

Improve robustness of Cross Version Upgrade tests

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

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

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

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

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

Fix cross-version upgrades with XMLSERIALIZE(NO INDENT)

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

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

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

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

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

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

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

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

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

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

Use attnum to identify index columns in pg_restore_attribute_stats()

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

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

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

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

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

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

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

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


Summary of Failures:

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

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

Statistics Import and Export \ pg_dump broken due to pg_strtof specifics

Fix pg_strtof() to not crash on NULL endptr

Unsorted/Unhelpful Test Failures

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2025-01-16%2002%3A17%3A31 - REL_15_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2025-02-02%2002%3A38%3A12 - REL_13_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2025-02-11%2002%3A25%3A29 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2025-02-19%2002%3A38%3A59 - REL_15_STABLE

2025-01-16 03:59:09.546 CET [26119:1] FATAL:  shmat(id=1006632988, addr=0, flags=0x4000) failed: Not enough space

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=kingsnake&dt=2024-08-19%2019%3A17%3A59 - REL_17_STABLE

(kingsnake is an ppc64le (POWER9) animal)

not ok 1     - basic_archive                          122486 ms

---
pgsql.build/contrib/basic_archive/regression.diffs
--- /home/fedora/17-kingsnake/buildroot/REL_17_STABLE/pgsql.build/contrib/basic_archive/expected/basic_archive.out	2024-08-19 19:18:02.127953655 +0000
+++ /home/fedora/17-kingsnake/buildroot/REL_17_STABLE/pgsql.build/contrib/basic_archive/results/basic_archive.out	2024-08-19 20:08:27.248588589 +0000
@@ -23,7 +23,7 @@
 	WHERE a ~ '^[0-9A-F]{24}$';
  ?column? 
 ----------
- t
+ f
 (1 row)

---
pgsql.build/contrib/basic_archive/log/postmaster.log
2024-08-19 20:06:25.585 UTC [381940:6] pg_regress/basic_archive LOG:  statement: DO $$
	DECLARE
		archived bool;
		loops int := 0;
	BEGIN
		LOOP
			archived := count(*) > 0 FROM pg_ls_dir('.', false, false) a
				WHERE a ~ '^[0-9A-F]{24}$';
			IF archived OR loops > 120 * 10 THEN EXIT; END IF;
			PERFORM pg_sleep(0.1);
			loops := loops + 1;
		END LOOP;
	END
	$$;
2024-08-19 20:08:27.252 UTC [381940:7] pg_regress/basic_archive LOG:  statement: SELECT count(*) > 0 FROM pg_ls_dir('.', false, false) a
		WHERE a ~ '^[0-9A-F]{24}$';

the expected archive file (000000010000000000000001?) didn't appear in the data directory within 120 seconds?

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=iguana&dt=2024-08-29%2013%3A57%3A57 - REL_15_STABLE

+++ isolation install-check in src/test/modules/delay_execution +++
============== running regression test queries        ==============
test partition-addition           ... FAILED   312375 ms

---
inst/logfile
...
2024-08-29 14:31:13.852 UTC [4029501:5] isolation/partition-addition/control connection LOG:  statement: 
	  CREATE TABLE foo (a int, b text) PARTITION BY LIST(a);
	  CREATE TABLE foo1 PARTITION OF foo FOR VALUES IN (1);
	  CREATE TABLE foo3 PARTITION OF foo FOR VALUES IN (3);
	  CREATE TABLE foo4 PARTITION OF foo FOR VALUES IN (4);
	  INSERT INTO foo VALUES (1, 'ABC');
	  INSERT INTO foo VALUES (3, 'DEF');
	  INSERT INTO foo VALUES (4, 'GHI');
	
2024-08-29 14:31:13.859 UTC [4029503:5] isolation/partition-addition/s2 LOG:  statement: SELECT pg_advisory_lock(12345);
2024-08-29 14:31:13.859 UTC [4029502:5] isolation/partition-addition/s1 LOG:  statement: LOAD 'delay_execution';
			  SET delay_execution.post_planning_lock_id = 12345;
			  SELECT * FROM foo WHERE a <> 1 AND a <> (SELECT 3);
2024-08-29 14:31:13.870 UTC [4029501:6] isolation/partition-addition/control connection LOG:  execute isolationtester_waiting: SELECT pg_catalog.pg_isolation_test_session_is_blocked($1, '{4029502,4029503}')
2024-08-29 14:31:13.870 UTC [4029501:7] isolation/partition-addition/control connection DETAIL:  parameters: $1 = '4029502'
...
2024-08-29 14:36:26.052 UTC [4029501:60550] isolation/partition-addition/control connection LOG:  execute isolationtester_waiting: SELECT pg_catalog.pg_isolation_test_session_is_blocked($1, '{4029502,4029503}')
2024-08-29 14:36:26.052 UTC [4029501:60551] isolation/partition-addition/control connection DETAIL:  parameters: $1 = '4029502'
2024-08-29 14:36:26.055 UTC [4029502:6] isolation/partition-addition/s1 ERROR:  canceling statement due to user request
2024-08-29 14:36:26.055 UTC [4029502:7] isolation/partition-addition/s1 STATEMENT:  LOAD 'delay_execution';
			  SET delay_execution.post_planning_lock_id = 12345;
			  SELECT * FROM foo WHERE a <> 1 AND a <> (SELECT 3);

(iguana is a ppc64le (POWER9) animal)

Session "s1" was blocked but pg_isolation_test_session_is_blocked() could not determine that, either because pg_blocking_pids() somehow omitted PID 4029503 (can be emulated with "PG_RETURN_BOOL(false);" inserted at the start of pg_isolation_test_session_is_blocked()), or because "s1" was blocked somehow before reaching planner_hook (= delay_execution_planner) (can be emulated with "SELECT pg_sleep(330);" added before "SET delay_execution.post_planning_lock_id = 12345;" in the session "s1" declaration).

Not reproduced. Moreover, this is the only failure of this kind among all TestModulesCheck-C failures recorded (50+).

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2024-09-02%2021%3A32%3A19 - REL_16_STABLE

make (01:25:46)
...
scripts-check (01:38:17)
...
[04:33:31] t/020_createdb.pl ......... ok  1326343 ms ( 0.03 usr  0.00 sys +  7.41 cusr  9.33 csys = 16.77 CPU)
[04:40:17] t/040_createuser.pl ....... ok   406303 ms ( 0.02 usr  0.00 sys +  3.07 cusr  2.79 csys =  5.88 CPU)
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 29 just after 13.
[04:47:09] t/050_dropdb.pl ........... 
Dubious, test returned 29 (wstat 7424, 0x1d00)
All 13 subtests passed 
...

---
pgsql.build/src/bin/scripts/tmp_check/log/regress_log_050_dropdb
[04:47:00.052](0.069s) ok 13 - fails with nonexistent database
error running SQL: 'psql:<stdin>:2: ERROR:  source database "template1" is being accessed by other users
DETAIL:  There is 1 other session using the database.'
while running 'psql -XAtq -d port=13455 host=/home/nm/farm/tmp/gsuqPCSa4L dbname='postgres' -f - -v ON_ERROR_STOP=1' with sql '
	CREATE DATABASE regression_invalid;
	UPDATE pg_database SET datconnlimit = -2 WHERE datname = 'regression_invalid';

---
pgsql.build/src/bin/scripts/tmp_check/log/050_dropdb_main.log
2024-09-03 04:47:00.116 CEST [4558:3] 050_dropdb.pl LOG:  statement: CREATE DATABASE regression_invalid;
2024-09-03 04:47:05.118 CEST [4558:4] 050_dropdb.pl ERROR:  source database "template1" is being accessed by other users
2024-09-03 04:47:05.118 CEST [4558:5] 050_dropdb.pl DETAIL:  There is 1 other session using the database.
2024-09-03 04:47:05.118 CEST [4558:6] 050_dropdb.pl STATEMENT:  CREATE DATABASE regression_invalid;

compare duration with the next (successful) run:

make (00:02:09)
...
scripts-check (00:01:31)
...
[20:01:56] t/020_createdb.pl ......... ok    12996 ms ( 0.02 usr  0.00 sys +  5.46 cusr  6.11 csys = 11.59 CPU)
[20:02:01] t/040_createuser.pl ....... ok     4888 ms ( 0.01 usr  0.00 sys +  2.47 cusr  2.16 csys =  4.64 CPU)
[20:02:06] t/050_dropdb.pl ........... ok     5093 ms ( 0.00 usr  0.00 sys +  2.62 cusr  2.19 csys =  4.81 CPU)

(Perhaps, wrasse was extremely slow at the time of the failed test run and autovacuum worker started in template1 could not stop during 5 seconds.)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2024-12-16%2023%3A43%3A03 - REL_15_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2024-12-21%2022%3A18%3A04 - REL_16_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2025-01-02%2009%3A21%3A04 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2025-01-09%2023%3A15%3A04 - REL_17_STABLE

--- /home/bf/proj/bf/build-farm-17/REL_16_STABLE/pgsql.build/src/test/regress/expected/select_parallel.out	2024-12-21 22:18:03.844773742 +0000
+++ /home/bf/proj/bf/build-farm-17/REL_16_STABLE/pgsql.build/src/test/recovery/tmp_check/results/select_parallel.out	2024-12-21 22:23:28.264849796 +0000
@@ -551,7 +551,7 @@
    ->  Nested Loop (actual rows=98000 loops=1)
          ->  Seq Scan on tenk2 (actual rows=10 loops=1)
                Filter: (thousand = 0)
-               Rows Removed by Filter: 9990
+               Rows Removed by Filter: 9395

#   Failed test 'regression tests pass'
#   at t/027_stream_regress.pl line 95.
#          got: '256'
#     expected: '0'
# Looks like you failed 1 test of 9.
[23:42:59] t/027_stream_regress.pl ............... 
...
diff -U3 /home/bf/proj/bf/build-farm-17/HEAD/pgsql.build/src/test/regress/expected/memoize.out /home/bf/proj/bf/build-farm-17/HEAD/pgsql.build/src/test/recovery/tmp_check/results/memoize.out
--- /home/bf/proj/bf/build-farm-17/HEAD/pgsql.build/src/test/regress/expected/memoize.out	2024-12-18 23:35:04.318987642 +0000
+++ /home/bf/proj/bf/build-farm-17/HEAD/pgsql.build/src/test/recovery/tmp_check/results/memoize.out	2024-12-18 23:42:24.806028990 +0000
@@ -179,7 +179,7 @@
                Hits: 980  Misses: 20  Evictions: Zero  Overflows: 0  Memory Usage: NkB
                ->  Seq Scan on tenk1 t2 (actual rows=1 loops=N)
                      Filter: ((t1.twenty = unique1) AND (t1.two = two))
-                     Rows Removed by Filter: 9999
+                     Rows Removed by Filter: 9775
 (12 rows)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sungazer&dt=2024-12-14%2005%3A54%3A52 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hornet&dt=2025-01-24%2004%3A08%3A24 - REL_14_STABLE

# poll_query_until timed out executing this query:
# 
# 	SELECT vacuum_count > 0
# 	FROM pg_stat_all_tables WHERE relname = 'vac_horizon_floor_table';

2024-12-14 10:43:37.277 UTC [11534840:9] 043_vacuum_horizon_floor.pl LOG:  statement: VACUUM (VERBOSE, FREEZE) vac_horizon_floor_table;
...
2024-12-14 10:43:47.361 UTC [11534840:10] 043_vacuum_horizon_floor.pl LOG:  using stale statistics instead of current ones because stats collector is not responding
2024-12-14 10:43:47.361 UTC [11534840:11] 043_vacuum_horizon_floor.pl STATEMENT:  VACUUM (VERBOSE, FREEZE) vac_horizon_floor_table;
2024-12-14 10:43:47.362 UTC [11534840:12] 043_vacuum_horizon_floor.pl INFO:  aggressively vacuuming "public.vac_horizon_floor_table"
...
2024-12-14 10:43:49.296 UTC [11534840:25] 043_vacuum_horizon_floor.pl INFO:  index "vac_horizon_floor_table_col1_idx" now contains 3 row versions in 551 pages
2024-12-14 10:43:49.296 UTC [11534840:26] 043_vacuum_horizon_floor.pl DETAIL:  200000 index row versions were removed.
	544 index pages were newly deleted.
	544 index pages are currently deleted, of which 0 are currently reusable.
	CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s.
2024-12-14 10:43:49.296 UTC [11534840:27] 043_vacuum_horizon_floor.pl CONTEXT:  while cleaning up index "vac_horizon_floor_table_col1_idx" of relation "public.vac_horizon_floor_table"
2024-12-14 10:43:49.296 UTC [11534840:28] 043_vacuum_horizon_floor.pl INFO:  table "vac_horizon_floor_table": found 199559 removable, 3 nonremovable row versions in 885 out of 885 pages
2024-12-14 10:43:49.296 UTC [11534840:29] 043_vacuum_horizon_floor.pl DETAIL:  0 dead row versions cannot be removed yet, oldest xmin: 741
	Skipped 0 pages due to buffer pins, 0 frozen pages.
	CPU: user: 0.09 s, system: 0.03 s, elapsed: 1.93 s.
2024-12-14 10:43:49.296 UTC [11534840:30] 043_vacuum_horizon_floor.pl CONTEXT:  while scanning relation "public.vac_horizon_floor_table"
...

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=francolin&dt=2025-01-06%2010%3A02%3A36 - REL_17_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mylodon&dt=2025-02-24%2022%3A05%3A28 - REL_16_STABLE

--- /home/bf/bf-build/francolin/REL_17_STABLE/pgsql/src/pl/plpgsql/src/expected/plpgsql_cache.out	2024-09-25 13:23:23.310891515 +0000
+++ /home/bf/bf-build/francolin/REL_17_STABLE/pgsql.build/testrun/plpgsql-running/regress/results/plpgsql_cache.out	2025-01-06 10:17:15.939118906 +0000
@@ -23,8 +23,11 @@
 -- currently, this fails due to cached plan for "r.f1 + 1" expression
 -- (but if debug_discard_caches is on, it will succeed)
 select c_sillyaddone(42);
-ERROR:  type of parameter 4 (double precision) does not match that when preparing the plan (integer)
-CONTEXT:  PL/pgSQL function c_sillyaddone(integer) line 1 at RETURN
+ c_sillyaddone 
+---------------
+            43
+(1 row)
+

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2025-01-07%2022%3A00%3A04 - REL_16_STABLE

--- /home/bf/proj/bf/build-farm-17/REL_16_STABLE/pgsql.build/src/test/regress/expected/partition_prune.out	2025-01-07 22:00:03.731034208 +0000
+++ /home/bf/proj/bf/build-farm-17/REL_16_STABLE/pgsql.build/src/test/regress/results/partition_prune.out	2025-01-07 22:00:50.219782536 +0000
@@ -2438,8 +2438,8 @@
                                  Index Cond: (a = a.a)
                            ->  Index Scan using ab_a2_b3_a_idx on ab_a2_b3 ab_6 (never executed)
                                  Index Cond: (a = a.a)
-                           ->  Index Scan using ab_a3_b1_a_idx on ab_a3_b1 ab_7 (never executed)
-                                 Index Cond: (a = a.a)
+                           ->  Seq Scan on ab_a3_b1 ab_7 (never executed)
+                                 Filter: (a = a.a)
...
                            ->  Index Scan using ab_a3_b3_a_idx on ab_a3_b3 ab_9 (never executed)
@@ -2629,11 +2629,8 @@
          Filter: (b = $1)
          ->  Bitmap Index Scan on ab_a2_b3_a_idx (never executed)
                Index Cond: (a = $0)
-   ->  Bitmap Heap Scan on ab_a3_b1 ab_7 (never executed)
-         Recheck Cond: (a = $0)
-         Filter: (b = $1)
-         ->  Bitmap Index Scan on ab_a3_b1_a_idx (never executed)
-               Index Cond: (a = $0)
+   ->  Seq Scan on ab_a3_b1 ab_7 (never executed)
+         Filter: ((a = $0) AND (b = $1))
    ->  Bitmap Heap Scan on ab_a3_b2 ab_8 (actual rows=0 loops=1)
          Recheck Cond: (a = $0)
          Filter: (b = $1)
@@ -2644,7 +2641,7 @@
          Filter: (b = $1)
          ->  Bitmap Index Scan on ab_a3_b3_a_idx (never executed)
                Index Cond: (a = $0)
-(52 rows)
+(49 rows)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2025-01-11%2016%3A49%3A04 - REL_15_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2025-01-14%2013%3A16%3A03 - REL_16_STABLE

=== dumping /home/bf/proj/bf/build-farm-17/REL_15_STABLE/pgsql.build/src/bin/pg_upgrade/tmp_check/regression.diffs ===
diff -U3 /home/bf/proj/bf/build-farm-17/REL_15_STABLE/pgsql.build/src/test/regress/expected/partition_prune.out /home/bf/proj/bf/build-farm-17/REL_15_STABLE/pgsql.build/src/bin/pg_upgrade/tmp_check/results/partition_prune.out
--- /home/bf/proj/bf/build-farm-17/REL_15_STABLE/pgsql.build/src/test/regress/expected/partition_prune.out	2025-01-11 16:49:03.976529417 +0000
+++ /home/bf/proj/bf/build-farm-17/REL_15_STABLE/pgsql.build/src/bin/pg_upgrade/tmp_check/results/partition_prune.out	2025-01-11 16:51:52.701998985 +0000
@@ -2440,8 +2440,8 @@
                                  Index Cond: (a = a.a)
                            ->  Index Scan using ab_a3_b1_a_idx on ab_a3_b1 ab_7 (never executed)
                                  Index Cond: (a = a.a)
-                           ->  Index Scan using ab_a3_b2_a_idx on ab_a3_b2 ab_8 (never executed)
-                                 Index Cond: (a = a.a)
+                           ->  Seq Scan on ab_a3_b2 ab_8 (never executed)
+                                 Filter: (a.a = a)
                            ->  Index Scan using ab_a3_b3_a_idx on ab_a3_b3 ab_9 (never executed)
                                  Index Cond: (a = a.a)
 (27 rows)
...

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mereswine&dt=2025-01-17%2004%3A09%3A28 - REL_17_STABLE

2025-01-16 22:09:57.095 PST [22738:1] FATAL:  could not map anonymous shared memory: Cannot allocate memory

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

2025-01-16 07:47:32.998 UTC [821755:97] LOG:  client backend (PID 823960) was terminated by signal 6: Aborted
2025-01-16 07:47:32.998 UTC [821755:98] DETAIL:  Failed process was running: SELECT t1.oid, t1.typname, p1.oid, p1.proname
	FROM pg_type AS t1, pg_proc AS p1
	WHERE t1.typinput = p1.oid AND p1.provolatile NOT IN ('i', 's');

--- https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=leafhopper&dt=2025-01-19%2014%3A21%3A04 - master

2025-01-19 14:27:39.420 UTC [886769:94] LOG:  client backend (PID 889096) was terminated by signal 6: Aborted
2025-01-19 14:27:39.420 UTC [886769:95] DETAIL:  Failed process was running: SELECT *
	FROM pg_stats
	WHERE schemaname = 'stats_import'
	AND tablename = 'test'
	AND inherited = false
	AND attname = 'tags';

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-02-05%2015%3A26%3A51 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2025-02-05%2017%3A52%3A03 - master

--- /home/andrew/bf/root/HEAD/redis_fdw.build/test/expected/redis_fdw.out	2021-06-29 13:33:37.761589602 -0400
+++ /home/andrew/bf/root/HEAD/redis_fdw.build/test/results/redis_fdw.out	2025-02-05 10:36:42.440034768 -0500
@@ -42,1359 +42,10 @@
     end if;
   end;
 $$;
-\\unset ON_ERROR_STOP
--- ok, empty, so now run the setup script
-\\! redis-cli < test/sql/redis_setup
...
+ERROR:  invalid tabletype (hash) - must be hash, list, set or zset
+CONTEXT:  SQL statement "select                   (select count(*) from db15) +
+        (select count(*) from db15_hash) +
+        (select count(*) from db15_set) +
+        (select count(*) from db15_list) +
+        (select count(*) from db15_zset)"
+PL/pgSQL function inline_code_block line 5 at SQL statement

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=alligator&dt=2025-02-08%2019%3A36%3A39 - master
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=alligator&dt=2025-02-08%2019%3A35%3A46 - master

2025-02-09 06:25:59.733 ACDT [388413] LOG:  invalid value for parameter "lc_monetary": "en_AU.UTF-8"
2025-02-09 06:25:59.733 ACDT [388413] LOG:  invalid value for parameter "lc_numeric": "en_AU.UTF-8"
2025-02-09 06:25:59.733 ACDT [388413] LOG:  invalid value for parameter "lc_time": "en_AU.UTF-8"
2025-02-09 06:25:59.733 ACDT [388413:4] FATAL:  configuration file "/home/postgres/proj/bfgit/buildroot/HEAD/pgsql.build/src/test/recovery/tmp_check/t_001_stream_rep_primary_data/pgdata/postgresql.conf" contains errors

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-02-08%2015%3A09%3A04 - REL_14_STABLE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2025-02-15%2003%3A15%3A23 - REL_14_STABLEE

Stage install-check-English_United-States.1252

test tablespace                   ... FAILED     3740 ms

--- C:/prog/bf/root/REL_14_STABLE/pgsql.build/src/test/regress/expected/tablespace.out	2025-02-08 15:57:43.889887000 +0000
+++ C:/prog/bf/root/REL_14_STABLE/pgsql.build/src/test/regress/results/tablespace.out	2025-02-08 15:57:49.333051100 +0000
@@ -929,6 +929,7 @@
 NOTICE:  no matching relations in tablespace "regress_tblspace_renamed" found
 -- Should succeed
 DROP TABLESPACE regress_tblspace_renamed;
+ERROR:  tablespace "regress_tblspace_renamed" is not empty

(Not reproduced locally under seemingly the same conditions.)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=dikkop&dt=2025-02-16%2000%3A26%3A01 - REL_16_STABLE

--- /mnt/data/buildfarm/buildroot/REL_16_STABLE/pgsql.build/src/test/regress/expected/numeric.out	2025-02-16 02:18:52.820119000 +0000
+++ /mnt/data/buildfarm/buildroot/REL_16_STABLE/pgsql.build/src/test/regress/results/numeric.out	2025-02-16 02:19:57.772058000 +0000
@@ -3583,9 +3583,9 @@
 SET LOCAL parallel_setup_cost = 0;
 SET LOCAL max_parallel_workers_per_gather = 4;
 SELECT variance(a) FROM num_variance;
-      variance      
---------------------
- 2.5000000000000000
+ variance 
+----------
+        0
 (1 row)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sevengill&dt=2025-02-19%2002%3A47%3A40 - master

running bootstrap script ... 2025-02-18 22:51:51.476 CST [18221] FATAL:  could not create shared memory segment: No space left on device

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=caiman&dt=2025-02-23%2006%3A54%3A54 - master

--- /repos/client-code-REL_18/HEAD/pgsql.build/src/test/isolation/expected/stats_1.out	2025-02-23 03:55:35.961552179 -0300
+++ /repos/client-code-REL_18/HEAD/pgsql.build/src/test/isolation/output_iso/results/stats.out	2025-02-23 04:21:35.039876561 -0300
@@ -1688,7 +1688,7 @@
 
 name           |pg_stat_get_function_calls|total_above_zero|self_above_zero
 ---------------+--------------------------+----------------+---------------
-test_stat_func2|                         1|t               |t              
+test_stat_func2|                         1|f               |f              
 (1 row)

(Not reproduced locally on Fedora 43 VM,)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=tayra&dt=2025-02-24%2011%3A35%3A14 - master

2025-02-24 08:45:03.621 -03 [227213] ERROR:  invalid value for parameter "TimeZone": "America/Los_Angeles"

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=tern&dt=2025-02-27%2005%3A07%3A23 - REL_14_STABLE

#   Failed test 'check replication statistics are updated'
#   at t/001_repl_stats.pl line 81.
#          got: 'regression_slot1|f|f
# regression_slot2|f|f
# regression_slot3|f|f'
#     expected: 'regression_slot1|t|t
# regression_slot2|t|t
# regression_slot3|t|t'
# Looks like you failed 1 test of 2.
[10:41:59] t/001_repl_stats.pl .. 
Dubious, test returned 1 (wstat 256, 0x100)

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2025-02-28%2010%3A45%3A58 - REL_17_STABLE

pg_restore: error: could not execute query: ERROR:  could not extend file "base/16384/2606": No space left on device
HINT:  Check free disk space.

Known Buildfarm Test Failures

Investigated Test failures

027_stream_regress.pl fails to wait for standby because of incorrect CRC in WAL

020_archive_status.pl failed to wait for updated statistics due to send() returned EAGAIN

031_recovery_conflict.pl fails to detect an expected lock acquisition

031_recovery_conflict.pl fails when a conflict counted twice

001_rep_changes.pl fails due to publisher stuck on shutdown

Also 035_standby_logical_decoding.pl fails on restart of standby (which is a publisher in the test):

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

027_stream_regress.pl fails on crake with timeout when waiting for catchup

027_stream_regress.pl fails due to some IOS plans of queries in create_index.sql changed

Also 002_pg_upgrade.pl fails due to some IOS plans of queries in create_index.sql changed

regress-running/regress fails on skink due to timeout

035_standby_logical_decoding_standby.pl fails due to missing activeslot invalidation

xversion-upgrade-XXX fails due to pg_ctl timeout

Also test runs fail on the stopdb-C-x stage

subscriber tests fail due to an assertion failure in SnapBuildInitialSnapshot()

Upgrade tests fail on Windows due to pg_upgrade_output.d/ not removed

Also buildfarm's check-pg_upgrade fails on removing data.old

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

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

Miscellaneous test failures in v14- on Windows due to "Permission denied" errors

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

Miscellaneous tests fail on Windows due to a connection closed before receiving a final error message

031_recovery_conflict.pl test might fail due to late pgstat entries flushing

005_opclass_damage.pl fails on Windows animals due to timeout

culicidae failed to restart server due to incorrect checksum in control file

Also culicidae failed regression test due to incorrect checksum

stats.sql is failing sporadically in v14- on POWER/aarch64 animals

pg_ctl stop/start fails on Windows due to inconsistent check for postmaster.pid existence

pg_ctl stop fails on Cygwin due to DELETE PENDING state of postmaster.pid

dblink.sql (and postgres_fdw.sql) fail on Windows due to the cancel packet not sent

timeouts.spec failed because of statement cancelled due to unexpected reason

002_archiving.pl fails due to promote request not received timely on Windows

019_replslot_limit.pl fails due to walsender stuck on sending FATAL to frozen walreceiver

027_stream_regress.pl failed on drongo due to walreceiver not reconnecting after primary restart

Also 001_rep_changes.pl failed on fairywren due to walreceiver not reconnecting after primary restart

Also 021_twophase.pl failed on fairywren due to walreceiver not reconnecting after primary restart

pageinspect/page.sql fails in v14- due to freeze requested not happening

deadlock-soft.sql is failing on newest Fedora

ssl tests still have opportunity to fail due to TCP port conflict

Parallel tests publication and subscription might fail due to concurrent tuple update

019_replslot_limit.pl might fail due to checkpoint skipped

tablespace.sql is unstable due to lack of ORDER BY (in v15-)

stats.sql might fail due to shared buffers also used by parallel tests

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

test_decoding/slot_creation_error.spec fails due to timing issue

014_binary.pl might fail when apply worker starts only after timeout of 180 seconds

Fixed Test Failures

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

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

XversionUpgrade fails with pg_dump error after e65dbc992

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

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

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

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

Also new test t_001_test_escape fails on ARM animals

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

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

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

initdb fails on Valgrind-enabled animal (after 925682260)

Testing timed out on check stage (after 6a2275b89)

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

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

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

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

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

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

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

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

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

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

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

Unsorted/Unhelpful Test Failures

Known Buildfarm Test Failures - Archive

Navigation menu

Search