Life with Open Source

commit   : 12f866cd5f72d65ed4435b8203540efde45ba01d    
  
author   : Michael Paquier <michael@paquier.xyz>    
date     : Wed, 7 Oct 2026 08:45:37 +0900    
  
committer: Michael Paquier <michael@paquier.xyz>    
date     : Wed, 7 Oct 2026 08:45:37 +0900    

A smart or fast shutdown during an early crash restart can wait forever  
on the checkpointer and I/O workers.  FatalError is still set, so  
PM_STOP_BACKENDS adds them as processes to wait for, but these are  
relaunched by the restart and ignore the SIGTERM that a shutdown sends.  
AbortStartTime has been reset at that point, meaning that SIGKILL would  
also not fire.  
  
SIGQUIT is now sent instead of SIGTERM when FatalError is set, via  
HandleFatalError(), arming AbortStartTime.  Going through that routine  
rather than signaling the children directly matters for the startup  
process: TerminateChildren() marks the startup process as signaled, so  
its exit is not later reported as a failure.  Note that after sending  
the SIGTERM, we check for any running processes, assuming that auxiliary  
processes have been already SIGQUIT'd for an immediate shutdown or for a  
FatalError.  
  
A test case is added, able to stress the scenario of a shutdown  
triggered during the early phases of crash recovery with a custom  
restore command waiting for a shutdown by scanning the server logs.  The  
CI is stable with this test (several runs done); the buildfarm will be  
the final judge regarding its stability.  
  
No backpatch is done for now, to be on the conservative side.  This  
feels also a slightly risky change for v19, which is close to release,  
and letting this change bake on HEAD a bit would not hurt.  
  
This problem has been originally reported by Justin Pryzby back in 2023,  
without being fixed, and still existed on HEAD.  
  
Reported-by: Justin Pryzby <pryzby@telsasoft.com>  
Author: Ayush Tiwari <ayushtiwari.slg01@gmail.com>  
Co-authored-by: Michael Paquier <michael@paquier.xyz>  
Discussion: https://postgr.es/m/CAJTYsWXCLi00cJ6-_OkMJB4UjyV6EZjc86QwmgE9=iH_C0R-Aw@mail.gmail.com  
Discussion: https://postgr.es/m/ZWlrdQarrZvLsgIk@pryzbyj2023  

commit   : 18740523a4a044a969f71a7322fb2d19ca69d00d    
  
author   : Peter Geoghegan <pg@bowt.ie>    
date     : Tue, 6 Oct 2026 18:21:37 -0400    
  
committer: Peter Geoghegan <pg@bowt.ie>    
date     : Tue, 6 Oct 2026 18:21:37 -0400    

bpchar equality ignores trailing spaces, so equal values in a column  
with no length specifier can have different images.  Similarly,  
oidvector equality intentionally pays no attention to the array lower  
bound field.  We nevertheless allowed nbtree deduplication to be used  
with indexes built with bpchar_ops, bpchar_pattern_ops, or  
oidvector_ops.  A posting list split could therefore place a TID in an  
index tuple whose key was equal to, but not bytewise identical to, the  
corresponding table value.  This allowed index-only scans to return  
subtly wrong results.  
  
To fix, drop support function 4 from the affected opclasses (we can't  
change catalog contents on branches 14 through 18, so we just disable  
deduplication by adding hard-coding to the relevant support functions).  
Deliberately leave the oidvector opclass alone on branches 14 through  
18, though.  Disallowing oidvector deduplication on these branches would  
make pg_amcheck report that pg_proc_proname_args_nsp_index has a corrupt  
metapage, needlessly alarming users.  
  
System catalog oidvector values always have a lower bound of 0, so the  
issue can't cause harm there; a user can only hit it by indexing an  
oidvector column that stores the output of a function like trim_array().  
It seems very unlikely that any user would ever do that.  
  
Users should REINDEX any B-Tree index on a bpchar column.  
  
Author: Shihao Zhong <zhong950419@gmail.com>  
Co-authored-by: Peter Geoghegan <pg@bowt.ie>  
Reported-by: Ke <kehan5800@gmail.com>  
Reported-by: Tom Lane <tgl@sss.pgh.pa.us>  
Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>  
Bug: #19749  
Discussion: https://postgr.es/m/19749-d46adf7c7d910b07@postgresql.org  
Discussion: https://postgr.es/m/CAGRkXqQQ311Lg=62x5UdZtPuRFgpT6XpPMw4X9E3tgbTu162Mw@mail.gmail.com  
Backpatch-through: 14  

commit   : 46cdca625a73403cad4774d97354a1fac1e91e51    
  
author   : David Steele <david@pgbackrest.org>    
date     : Sun, 4 Oct 2026 09:29:49 +0200    
  
committer: David Steele <david@pgbackrest.org>    
date     : Sun, 4 Oct 2026 09:29:49 +0200    

IMPORTANT NOTE: In prior versions it was possible for weak encryption subkeys and salts to be generated if there was an error accessing system random data.  
  
Bug Fixes:  
  
* Fix possible checksum error loading encrypted info and manifest files. (Fixed by j0uinim. Reviewed by David Steele.)  
* Fix possible weak encryption subkeys/salts. (Fixed by j0uinim. Reviewed by David Steele, Stefan Fercot, Douglas J Hunley.)  

commit   : d5138e2e3b92fe806505bc8b9c69f36bd70cea18    
  
author   : David Steele <david@pgbackrest.org>    
date     : Sun, 27 Sep 2026 14:15:45 +0300    
  
committer: David Steele <david@pgbackrest.org>    
date     : Sun, 27 Sep 2026 14:15:45 +0300    

Bug Fixes:  
  
* Fix empty block map when file is truncated to zero during backup. (Reviewed by Douglas J Hunley. Reported by JPCOSTA78.)  
* Disable read retry when filters are passed to the driver. (Reviewed by Douglas J Hunley. Reported by megamaced.)  
* Fix pagination of S3 version listing. (Reviewed by Douglas J Hunley, guruguruguru. Reported by guruguruguru.)  
* Set the Azure version header for SAS authentication. (Reviewed by Douglas J Hunley. Reported by Florian Helmberger.)  
* Fix async archive-push stalling on a zero-size backup history file. (Fixed by Andrew Kroh. Reviewed by David Steele, Douglas J Hunley.)  
* Fix annotate command on a remote encrypted repository. (Fixed by Douglas J Hunley. Reviewed by David Steele.)  
  
Features:  
  
* PostgreSQL 19beta4 support.  

commit   : 8c8f3ee63e310f0b3ea10b55ed3b96b4cc9296da    
  
author   : David Steele <david@pgbackrest.org>    
date     : Mon, 17 Aug 2026 16:08:40 +0700    
  
committer: David Steele <david@pgbackrest.org>    
date     : Mon, 17 Aug 2026 16:08:40 +0700    

Bug Fixes:  
  
* Fix hang when the chunk buffer is smaller than the input buffer. (Reviewed by Andrew Pogrebnoi, Douglas J Hunley. Reported by crajac66.)  
* Compare a new backup label only against its own full backup set. (Reviewed by Douglas J Hunley. Reported by Anton Glushakov.)  
* Fix source archives generated by GitHub missing files required to build. (Reported by aardvarkzed.)  
  
Features:  
  
* PostgreSQL 19beta3 support. (Contributed by Lardière Sébastien. Reviewed by David Steele.)  
  
Documentation Improvements:  
  
* Document exception for dots in S3 bucket names when repo-s3-uri-style=path.  
* Remove explicit hot_standby configuration from user guide.  

commit   : 724edf9bde9d356724ad384a2e196edc3c9f80f7    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Tue, 11 Aug 2026 14:38:31 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Tue, 11 Aug 2026 14:38:31 -0400    

commit   : 841d0cb0f9b8b1b25e7b299ac0eb134074b45a08    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Tue, 11 Aug 2026 14:37:01 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Tue, 11 Aug 2026 14:37:01 -0400    

commit   : 6b3806732b7c5df06bdd0ed150e8a07b4ad62315    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 10 Aug 2026 16:59:18 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 10 Aug 2026 16:59:18 -0400    

commit   : 18ec528b8c3804f4c101e3a8d091ada7c5a40bb4    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 10 Aug 2026 12:35:49 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 10 Aug 2026 12:35:49 -0400    

commit   : 2ff1375b5dd8bf09d8cb0e795974528180fd75ca    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 10 Aug 2026 16:57:41 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 10 Aug 2026 16:57:41 -0400    

commit   : 492b517f362a4325bbcd6c1aa6f1204b7696d7ed    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 10 Aug 2026 12:35:48 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 10 Aug 2026 12:35:48 -0400    

commit   : 7d3e000c5961a544302072058a1184e9a588837b    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 10 Aug 2026 16:56:00 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 10 Aug 2026 16:56:00 -0400    

commit   : a5c8e521cf9e2d2334cf3c94ed64edb397b00e01    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 10 Aug 2026 12:35:48 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 10 Aug 2026 12:35:48 -0400    

commit   : 083ac033419f690758508e08c1736089384bbee8    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 10 Aug 2026 16:54:09 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 10 Aug 2026 16:54:09 -0400    

commit   : 83bb18b714e7b98c243083d2480828331601de23    
  
author   : Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 10 Aug 2026 12:35:48 -0400    
  
committer: Tom Lane <tgl@sss.pgh.pa.us>    
date     : Mon, 10 Aug 2026 12:35:48 -0400