Message-ID: <0dba883ce1ae2faa2ef061605d2147d148b7f52c.camel@cybertec.at>
Subject: Re: pgBadger and postgres_fdw
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Colin 't Hart <colinthart@gmail.com>, Adrian Klaver
	 <adrian.klaver@aklaver.com>
Cc: PostgreSQL General <pgsql-general@lists.postgresql.org>
Date: Wed, 21 Jan 2026 19:57:26 +0100
In-Reply-To: <CAMon-aT92+JQVTD54iwEmPpkFRDHDnhOzZGHMG6GoH_8Qh_EDg@mail.gmail.com>
References: 
	<CAMon-aR8f3zi1Wytg-TCrbLa=sAooi4kTzbjukcvdt8G4mycbw@mail.gmail.com>
	 <31af308b-1689-44e8-ab88-f6a72722b38b@aklaver.com>
	 <CAMon-aT92+JQVTD54iwEmPpkFRDHDnhOzZGHMG6GoH_8Qh_EDg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.58.2 (3.58.2-1.fc43) 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/0dba883ce1ae2faa2ef061605d2147d148b7f52c.camel%40cybertec.at>
Precedence: bulk

On Wed, 2026-01-21 at 17:12 +0100, Colin 't Hart wrote:
> My question is how to identify which connections / queries from postgres_=
fdw are
> generating the `fetch 100 from c2` queries, which, in turn, may quite pos=
sibly
> lead to a feature request for having these named uniquely.

I would inverstigate that on the remote database.

If the user that postgres_fdw uses to connect is remote_user, you could

  ALTER ROLE remote_user SET log_min_duretion_statement =3D 0;

Then any statements executed through postgres_fdw would be logged.

If you have %x in log_line_prefix, you can find the DECLARE statement that =
declared
the cursor that takes so long to fetch.  Not very comfortale, but it should=
 work.

Yours,
Laurenz Albe