Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1nuf5i-0003u4-O7
	for pgsql-bugs@arkaria.postgresql.org; Fri, 27 May 2022 18:53:42 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1nuf5g-0000xQ-Vl
	for pgsql-bugs@arkaria.postgresql.org; Fri, 27 May 2022 18:53:40 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1nuf5g-0000xH-Ni
	for pgsql-bugs@lists.postgresql.org; Fri, 27 May 2022 18:53:40 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1nuf5e-0006iK-FN
	for pgsql-bugs@lists.postgresql.org; Fri, 27 May 2022 18:53:40 +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 24RIrZtF2703830;
	Fri, 27 May 2022 14:53:35 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
cc: Noah Misch <noah@leadboat.com>,
        =?UTF-8?B?RsOkcmJlciwgRnJhbnotSm9zZWYgKFN0TVVLKQ==?=
 <Franz-Josef.Faerber@stmuk.bayern.de>,
        PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: Extension pg_trgm, permissions and pg_dump order
In-reply-to: 
 <CA+TgmobJ31pKFAKJwq2p=4gKo_HYvYnnwJE7fz+T1auJfN+jEQ@mail.gmail.com>
References: <f8a4105f076544c180a87ef0c4822352@stmuk.bayern.de>
 <1961551.1653498155@sss.pgh.pa.us>
 <20220526055047.GA3153526@rfd.leadboat.com>
 <CA+TgmobJ31pKFAKJwq2p=4gKo_HYvYnnwJE7fz+T1auJfN+jEQ@mail.gmail.com>
Comments: In-reply-to Robert Haas <robertmhaas@gmail.com>
	message dated "Fri, 27 May 2022 14:46:41 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2703828.1653677615.1@sss.pgh.pa.us>
Date: Fri, 27 May 2022 14:53:35 -0400
Message-ID: <2703829.1653677615@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/2703829.1653677615%40sss.pgh.pa.us>
Precedence: bulk

Robert Haas <robertmhaas@gmail.com> writes:
> Why isn't the current behavior - i.e. failing with a permissions error
> - correct? I mean I realize it's wrong in the sense that you can't
> restore a dump you just took, but what about from a security
> perspective?