Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1smfU7-007ThQ-Si for pgsql-bugs@arkaria.postgresql.org; Fri, 06 Sep 2024 20:23:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1smfU5-003LMd-LR for pgsql-bugs@arkaria.postgresql.org; Fri, 06 Sep 2024 20:23:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1smfU5-003LMV-Cw for pgsql-bugs@lists.postgresql.org; Fri, 06 Sep 2024 20:23:09 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1smfTz-000V7f-4J for pgsql-bugs@lists.postgresql.org; Fri, 06 Sep 2024 20:23:09 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 486KN1ts2370640; Fri, 6 Sep 2024 16:23:01 -0400 From: Tom Lane To: Basha cc: "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: References: <18604-04d64b68e981ced6@postgresql.org> <2358981.1725648547@sss.pgh.pa.us> Comments: In-reply-to Basha message dated "Fri, 06 Sep 2024 19:24:57 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2370638.1725654181.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 06 Sep 2024 16:23:01 -0400 Message-ID: <2370639.1725654181@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Basha writes: > The original option to allow system table is to make changes to the syst= em 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 af= fect 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