Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension - Mailing list pgsql-bugs

From Edwin Polkerman
Subject Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
Date
Msg-id b718d444-3f9a-4e0b-bc82-485fb044c828@splendiddata.com
Whole thread
List pgsql-bugs

Hi Jacob,

We try to avoid big behavior changes in minor version updates.
Ah of course, that 's quite understandable... PG17 was the new major but the others were minor releases  :-)

Thank you very much for opening the enhancement request in -hackers!!

Kind regards,

Edwin

On 9/3/26 18:49, Jacob Champion wrote:
On Thu, Sep 3, 2026 at 4:55 AM Edwin Polkerman
<edwin.polkerman@splendiddata.com> wrote:
Keeps me only wondering why the behaviour change in pg_basebackup is not implemented for PG14 to 16 as well.
We try to avoid big behavior changes in minor version updates.

b) pg_basebackup ignores checksum issues on files not owned/managed by postgresql but pg_checksums will still complain about them in the data location.

Or is that what you mean for 'b)' below, an enhancement request for pg_checksums to treat checksums the way pg_basebackup does (pg >= 17)?
Correct.

I will file a bug report for this issue in github for the third-party extension pgactive. Please let me know if you want me to report an enhancement request or thet you take care about that
I'm happy to shepherd the conversation over to -hackers, and will do
that shortly. (I'm probably not the right person to drive it.)

--Jacob
--

Splendid Data Nederland B.V.
Binnenhof 62A
1412 LC NAARDEN
+31 85 773 19 99
+31 6 5118 8231

Follow us on LinkedIn

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #19652: to_number() silently truncates over-length integers
Next
From: Alexander Korotkov
Date:
Subject: Re: BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL