From: Christophe Pettus <xof@thebuild.com>
To: basha@maxcontact.com
Cc: PostgreSQL Bug List <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
Date: Fri, 6 Sep 2024 12:07:35 -0700
Message-ID: <5129DA7F-C4DF-4B87-A64B-C705DDB2C502@thebuild.com> (raw)
In-Reply-To: <18604-04d64b68e981ced6@postgresql.org>
References: <18604-04d64b68e981ced6@postgresql.org>
> On Sep 6, 2024, at 09:28, PG Bug reporting form <noreply@postgresql.org> wrote:
> However, after the PostgreSQL 16.4 update, pg_dump now fails due to these
> system table modifications, leaving us in a precarious position where
> essential backups cannot be performed.
It should be noted that this change does not prevent PITR backups, so it is still entirely possible to back up your installation.
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: xof@thebuild.com, basha@maxcontact.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
In-Reply-To: <5129DA7F-C4DF-4B87-A64B-C705DDB2C502@thebuild.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox