agora inbox for pgsql-bugs@postgresql.org
help / color / mirror / Atom feedFrom: Edwin Polkerman <edwin.polkerman@splendiddata.com>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
Date: Thu, 3 Sep 2026 21:35:44 +0200
Message-ID: <b718d444-3f9a-4e0b-bc82-485fb044c828@splendiddata.com> (raw)
In-Reply-To: <CAOYmi+=prw7DdrMf2-k8E2jhbi6dQ2v03xJJYnC0ZwBe4GLwPg@mail.gmail.com>
References: <19647-d18354ebe2134a6d@postgresql.org>
<CAOYmi+=QyQHvH2Ehqb+Je3nvv-+Qg6Xp8fG+cNs-KwAoHvNyBA@mail.gmail.com>
<b39d0277-de91-4fa1-b912-e3c8ee38ccf1@splendiddata.com>
<CAOYmi+myfnx3eC-jpTxGgtTPL5eMitu_nV9PkyqDS8W4puoNcw@mail.gmail.com>
<cd4f60fe-c8e7-4c15-ae98-6056242d0081@splendiddata.com>
<CAOYmi+=prw7DdrMf2-k8E2jhbi6dQ2v03xJJYnC0ZwBe4GLwPg@mail.gmail.com>
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 <https://www.linkedin.com/company/3327997/admin/>*
view thread (7+ messages)
Message-ID: <b718d444-3f9a-4e0b-bc82-485fb044c828@splendiddata.com>
Permalink: ../b718d444-3f9a-4e0b-bc82-485fb044c828@splendiddata.com/
Also on: postgresql.org/message-id/b718d444-3f9a-4e0b-bc82-485fb044c828@splendiddata.com
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: edwin.polkerman@splendiddata.com, jacob.champion@enterprisedb.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
In-Reply-To: <b718d444-3f9a-4e0b-bc82-485fb044c828@splendiddata.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox