Re: Temp table + inde + FDW table on Redshift: MOVE BACKWARD ALL IN not supported - Mailing list pgsql-admin

From Tom Lane
Subject Re: Temp table + inde + FDW table on Redshift: MOVE BACKWARD ALL IN not supported
Date
Msg-id 1912061.1707610854@sss.pgh.pa.us
Whole thread Raw
In response to Temp table + inde + FDW table on Redshift: MOVE BACKWARD ALL IN not supported  (Wells Oliver <wells.oliver@gmail.com>)
List pgsql-admin
Wells Oliver <wells.oliver@gmail.com> writes:
> Hi all. This might be a Redshift-specific issue and if so, I apologize for
> posting here, but there might be something more general with FDW, indexes,
> and temp tables going on too, so I thought I'd post.
> ...
> The query runs for a split second, you can see some results, and then bombs:

> ERROR:  SQL command "MOVE BACKWARD ALL IN c1" not supported.
> CONTEXT:  remote SQL command: MOVE BACKWARD ALL IN c1

You didn't show an EXPLAIN, but it looks like the FDW is expecting
the remote server to support something it doesn't.  I'd guess that
you need a Redshift-specific FDW to make this work reliably.  You
could possibly work around it by forcing the planner to use a
different join method.

            regards, tom lane



pgsql-admin by date:

Previous
From: Wells Oliver
Date:
Subject: Temp table + inde + FDW table on Redshift: MOVE BACKWARD ALL IN not supported
Next
From: Антон Глушаков
Date:
Subject: pg_dump --binary-upgrade out of memory