MIME-Version: 1.0
From: "Colin 't Hart" <colinthart@gmail.com>
Date: Wed, 21 Jan 2026 09:18:52 +0100
Message-ID: <CAMon-aR8f3zi1Wytg-TCrbLa=sAooi4kTzbjukcvdt8G4mycbw@mail.gmail.com>
Subject: pgBadger and postgres_fdw
To: PostgreSQL General <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000bbfd9b0648e193ab"
Archived-At: <https://www.postgresql.org/message-id/CAMon-aR8f3zi1Wytg-TCrbLa%3DsAooi4kTzbjukcvdt8G4mycbw%40mail.gmail.com>
Precedence: bulk

--000000000000bbfd9b0648e193ab
Content-Type: text/plain; charset="UTF-8"

Hi,

One of my clients makes extensive use of postgres_fdw. After a migration
performance isn't great. pgBadger reports show the slowest queries all
being `fetch 100 from c2`.

Anyone have any tricks for being able to associate those fetches with the
queries that were used when declaring the server-side cursor?

Thanks,

Colin

--000000000000bbfd9b0648e193ab
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi,</div><div><br></div><div>One of my clients makes =
extensive use of postgres_fdw. After a migration performance isn&#39;t grea=
t. pgBadger reports show the slowest queries all being `fetch 100 from c2`.=
</div><div><br></div><div>Anyone have any tricks for being able to associat=
e=C2=A0those fetches with the queries that were used when declaring the ser=
ver-side cursor?</div><div><br></div><div>Thanks,</div><div><br></div><div>=
Colin</div></div>

--000000000000bbfd9b0648e193ab--