Re: Temp table + inde + FDW table on Redshift: MOVE BACKWARD ALL IN not supported

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Wells Oliver <wells(dot)oliver(at)gmail(dot)com>
Cc: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Temp table + inde + FDW table on Redshift: MOVE BACKWARD ALL IN not supported
Date: 2024-02-11 00:20:54
Message-ID: 1912061.1707610854@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Wells Oliver <wells(dot)oliver(at)gmail(dot)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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Антон Глушаков 2024-02-12 15:36:20 pg_dump --binary-upgrade out of memory
Previous Message Wells Oliver 2024-02-10 23:35:53 Temp table + inde + FDW table on Redshift: MOVE BACKWARD ALL IN not supported