public inbox for [email protected]
help / color / mirror / Atom feedFrom: Adrian Klaver <[email protected]>
To: Colin 't Hart <[email protected]>
To: PostgreSQL General <[email protected]>
Subject: Re: pgBadger and postgres_fdw
Date: Wed, 21 Jan 2026 07:43:12 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAMon-aR8f3zi1Wytg-TCrbLa=sAooi4kTzbjukcvdt8G4mycbw@mail.gmail.com>
References: <CAMon-aR8f3zi1Wytg-TCrbLa=sAooi4kTzbjukcvdt8G4mycbw@mail.gmail.com>
On 1/21/26 00:18, Colin 't Hart wrote:
> 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?
This is going to need a lot more information. To start:
1) Migration of what and from what version to what version?
2) Where are the Postgres databases relative to each other on the network?
3) What versions of Postgres if not covered in 1.
4) If Postgres was what was being updated was an analyze done on the
instances?
5) Show a complete query using EXPLAIN ANALYZE.
6) Define slow.
>
> Thanks,
>
> Colin
--
Adrian Klaver
[email protected]
view thread (2+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: pgBadger and postgres_fdw
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox