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 1sqZ2Y-00AnXc-CA for pgsql-bugs@arkaria.postgresql.org; Tue, 17 Sep 2024 14:18:51 +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 1sqZ2X-00Bg4R-S3 for pgsql-bugs@arkaria.postgresql.org; Tue, 17 Sep 2024 14:18:49 +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 1sqZ2X-00Bg4J-JW for pgsql-bugs@lists.postgresql.org; Tue, 17 Sep 2024 14:18:49 +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 1sqZ2T-001f30-KG for pgsql-bugs@lists.postgresql.org; Tue, 17 Sep 2024 14:18:49 +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 48HEIje91462964; Tue, 17 Sep 2024 10:18:45 -0400 From: Tom Lane To: rekgrpth@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18621: postgres_fdw cannot work with tables that use schemaless functions in triggers In-reply-to: <18621-34e3fc574aa9fbc1@postgresql.org> References: <18621-34e3fc574aa9fbc1@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Tue, 17 Sep 2024 05:28:53 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1462962.1726582725.1@sss.pgh.pa.us> Date: Tue, 17 Sep 2024 10:18:45 -0400 Message-ID: <1462963.1726582725@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > Let's create a trigger on a remote server that uses different functions for > different users. postgres_fdw cannot perform an insert in this case. And the > remote server may be a production server, where there is no access to change > the trigger code so that it uses an explicit schema specification! This is a bug in the trigger function, not in postgres_fdw. regards, tom lane