From: Tom Lane <tgl@sss.pgh.pa.us>
To: basha@maxcontact.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
Date: Fri, 06 Sep 2024 14:49:07 -0400
Message-ID: <2358981.1725648547@sss.pgh.pa.us> (raw)
In-Reply-To: <18604-04d64b68e981ced6@postgresql.org>
References: <18604-04d64b68e981ced6@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> Steps to Reproduce:
> Enable allow_system_table_mods = true.
> Modify system tables (e.g., pg_database) to restrict visibility in a
> multi-tenant setup.
> Attempt to run pg_dump for backup purposes.
> pg_dump fails due to the recent security restriction.
Without any details about what you did to the system catalogs,
this complaint is quite un-actionable.
I will note that we do not consider random manual changes to
system catalogs to be a supported feature.
regards, tom lane
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: tgl@sss.pgh.pa.us, 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: <2358981.1725648547@sss.pgh.pa.us>
* 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