Feedback-ID: i76984098:Fastmail
Message-ID: <31af308b-1689-44e8-ab88-f6a72722b38b@aklaver.com>
Date: Wed, 21 Jan 2026 07:43:12 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: pgBadger and postgres_fdw
To: Colin 't Hart <colinthart@gmail.com>,
 PostgreSQL General <pgsql-general@lists.postgresql.org>
References: <CAMon-aR8f3zi1Wytg-TCrbLa=sAooi4kTzbjukcvdt8G4mycbw@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAMon-aR8f3zi1Wytg-TCrbLa=sAooi4kTzbjukcvdt8G4mycbw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/31af308b-1689-44e8-ab88-f6a72722b38b%40aklaver.com>
Precedence: bulk

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
adrian.klaver@aklaver.com