From: Tom Lane <tgl@sss.pgh.pa.us>
To: Basha <Basha@maxcontact.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
Date: Fri, 06 Sep 2024 16:23:01 -0400
Message-ID: <2370639.1725654181@sss.pgh.pa.us> (raw)
In-Reply-To: <GV1P194MB2356A3AED4F276E1AD0E6162D89E2@GV1P194MB2356.EURP194.PROD.OUTLOOK.COM>
References: <18604-04d64b68e981ced6@postgresql.org>
<2358981.1725648547@sss.pgh.pa.us>
<GV1P194MB2356A3AED4F276E1AD0E6162D89E2@GV1P194MB2356.EURP194.PROD.OUTLOOK.COM>
Basha <Basha@maxcontact.com> writes:
> The original option to allow system table is to make changes to the system tables. This change in 16.4 is removing that feature. When allow system table is set to on, this new feature should still allow and should not affect anything.
[ shrug... ] You're making an incredibly overheated, expansive
claim, many possible interpretations of which are obviously false.
You've provided zero detail that would let anyone figure out what your
actual concrete problem is --- and it sure isn't obvious, because
pg_dump doesn't have any direct connection to allow_system_table_mods,
nor does the security patch you're complaining about.
Perhaps you should read
https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
But with only the information you've provided so far, this bug report
isn't going to go anywhere, because we can't even understand what
you are talking about.
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: [EXT]: Re: BUG #18604: Regression in PostgreSQL 16.4: pg_dump Prevents Essential System Table Modifications
In-Reply-To: <2370639.1725654181@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