Re: Routing of FDW Queries to Secondary databases

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: adam(dot)blomeke(at)gmail(dot)com
Cc: pgpool-general(at)lists(dot)postgresql(dot)org
Subject: Re: Routing of FDW Queries to Secondary databases
Date: 2026-04-22 05:36:06
Message-ID: 20260422.143606.1097654739437506696.ishii@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgpool-general

> Hi,
>
> I understand that FDW queries don't get routed to the secondary databases
> since they occur within FETCH blocks.

Yes, currently Pgpool-II does not load balance DECLARE CURSOR/FETCH
(it's documented). The difficulty is, once DECLARE CURSOR is routed
to particular server, subsequent FETCH must be routed to the server
too. Pgpool-II has to track this.

> Is there any planned work to change
> this.

As far as I know I haven't noticed a request to implement load
balancing for DECLARE CURSOR/FETCH up to now.

> I have one database I'm about to work on clusterizing, but this
> limitation makes pgpool impractical as the read side is only accessed via
> FDWs in all but a very small set of circumstances.
>
> Again, I realize the existing limitation; I'm just curious if there's any
> work on the horizon to add that capability. If not, I will likely need to
> explore other alternatives for one of the clusters I'm working on.

If there's a strong demand, developers will discuss on implementing
the feature for the next major release of Pgpool-II (planned to be
released by the end of this year).

Regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp

In response to

Responses

Browse pgpool-general by date

  From Date Subject
Next Message Zdenek.Koktan 2026-04-23 08:22:41 Problems with SSL communication
Previous Message Adam Blomeke 2026-04-17 19:11:08 Routing of FDW Queries to Secondary databases