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

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: edwin(dot)polkerman(at)splendiddata(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
Date: 2026-09-02 18:51:46
Message-ID: CAOYmi+=QyQHvH2Ehqb+Je3nvv-+Qg6Xp8fG+cNs-KwAoHvNyBA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Sep 1, 2026 at 6:16 AM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> For PostgreSQL 18.6 and 17.11 the backup completes without any problems.

Do the global/ directories for the 17 and 18 clusters contain a
pgactive.stat file?

Without knowing anything about pgactive in particular (it's a
third-party extension)... It sure looks like that extension, or else
something related to it, has put a random file into the DB internals
in a way that won't pass our checksum verification. It needs to go
somewhere else.

--Jacob

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Edwin Polkerman 2026-09-02 20:43:15 Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
Previous Message Andrey Rachitskiy 2026-09-02 11:44:52 Re: BUG #19441: Backend waits for serializable snapshot indefinitely on removing temp relations