Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications

Поиск
Список
Период
Сортировка
От Christophe Pettus
Тема Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
Дата
Msg-id 3B462E2E-88B6-43B9-943F-90E883D33357@thebuild.com
обсуждение исходный текст
Ответ на BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications  (PG Bug reporting form <noreply@postgresql.org>)
Ответы RE: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
Список pgsql-bugs

> On Sep 6, 2024, at 09:28, PG Bug reporting form <noreply@postgresql.org> wrote:
> In PostgreSQL 16.4, the recent security enhancement introduced by the commit
> "Prevent unauthorized code execution during pg_dump (Masahiko Sawada)" has
> introduced unintended side effects that severely impact multi-tenant
> database environments. Specifically, this change blocks modifications to
> system tables, even when allow_system_table_mods is explicitly enabled.

As Tom noted, you should describe what system catalog modifications you are making.

It should be noted that this admonition appears as the first sentence in the documentation on the page that includes
`allow_system_table_mods`:

    The following parameters are intended for developer testing, and should never be used on a production database.

"We adjusted a developer-only parameter on a production database, having been warned by the documentation not to, and
nowsomething that previously worked no longer does" is not really going to be considered a bug.  It's better that a way
isfound to support your requirements without modifying system catalogs. 


В списке pgsql-bugs по дате отправления: