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 <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1uFE3m-001oZF-Tg
	for pgsql-bugs@arkaria.postgresql.org; Wed, 14 May 2025 15:30:19 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1uFE3l-00A8XB-Ce
	for pgsql-bugs@arkaria.postgresql.org; Wed, 14 May 2025 15:30:17 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1uFE3l-00A8X3-4C
	for pgsql-bugs@lists.postgresql.org; Wed, 14 May 2025 15:30:17 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1uFE3i-001m2T-0z
	for pgsql-bugs@lists.postgresql.org;
	Wed, 14 May 2025 15:30:15 +0000
Received: from pro.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 54EFUCMf1624474;
	Wed, 14 May 2025 11:30:12 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Matheus Alcantara <matheusssilv97@gmail.com>
cc: jackie.space@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18928: postgres_fdw search_path not reset causing pgbouncer
 pool_mode=transaction using the wrong schema
In-reply-to: 
 <CAFY6G8deU8mh=THZXVCDzan_9D6b8K9YUw4bBPBrYS4z37BZ9Q@mail.gmail.com>
References: <18928-b85f8c68121fd98b@postgresql.org>
 <CAFY6G8deU8mh=THZXVCDzan_9D6b8K9YUw4bBPBrYS4z37BZ9Q@mail.gmail.com>
Comments: In-reply-to Matheus Alcantara <matheusssilv97@gmail.com>
	message dated "Wed, 14 May 2025 12:06:35 -0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7624.1747236612.1@sss.pgh.pa.us>
Date: Wed, 14 May 2025 11:30:12 -0400
Message-ID: <7625.1747236612@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/7625.1747236612%40sss.pgh.pa.us>
Precedence: bulk

ISTM the problem described here is a failure on PgBouncer's part: it is
failing to maintain the illusion of a separate connection per user.
I don't know that much about PgBouncer, but perhaps you just have
it configured wrong?

			regards, tom lane