From: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
---|---|
To: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: d844cd75a and postgres_fdw |
Date: | 2024-07-05 12:56:28 |
Message-ID: | CAPmGK14-od7ikHVX2d7Pg--MFFzTPAA5w1zNPb_td9R4xWnHOg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Oct 24, 2023 at 8:48 PM Devrim Gündüz <devrim(at)gunduz(dot)org> wrote:
> I'm seeing an issue after upgrading from 12.13 to 15.4. This happens
> when we run a query against a foreign table (fdw on the same instance to
> a different database) -- but does not appear when we get rid of
> postgres_fdw:
>
> ERROR: cursor can only scan forward
> HINT: Declare it with SCROLL option to enable backward scan.
> CONTEXT: remote SQL command: MOVE BACKWARD ALL IN c1
>
> SQL state: 55000
>
> I attached the query. The name of the foreign table is
> "foobar.sys_user".
>
> Looks like the bug #17889, and this is the last email in that thread:
> https://www.postgresql.org/message-id/1852635.1682808624%40sss.pgh.pa.us
>
> OTOH, same query works (against the FDW) when we remove the following
> WHERE clause:
>
> WHERE
> tbl.table_status = 'A'
> AND tbl.table_id <> 1
> AND tbl.table_id <> - 2
>
> Any hints?
The error occurs when rescanning a postgres_fdw foreign relation, so I
think the reason why the query works would be that the planner chose a
join plan other than a nestloop join plan.
I proposed a fix for this in [1].
Best regards,
Etsuro Fujita
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2024-07-05 13:08:07 | Re: Improving the latch handling between logical replication launcher and worker processes. |
Previous Message | Andrew Dunstan | 2024-07-05 12:53:40 | Re: Problem while installing PostgreSQL using make |