From: Tom Lane <tgl@sss.pgh.pa.us>
To: Wells Oliver <wells.oliver@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Temp table + inde + FDW table on Redshift: MOVE BACKWARD ALL IN not supported
Date: Sat, 10 Feb 2024 19:20:54 -0500
Message-ID: <1912061.1707610854@sss.pgh.pa.us> (raw)
In-Reply-To: <CAOC+FBXDuP3TuztVUB3bxXS6f65wiodFo+3wFrZiUOudzAHTdw@mail.gmail.com>
References: <CAOC+FBXDuP3TuztVUB3bxXS6f65wiodFo+3wFrZiUOudzAHTdw@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, wells.oliver@gmail.com
Subject: Re: Temp table + inde + FDW table on Redshift: MOVE BACKWARD ALL IN not supported
In-Reply-To: <1912061.1707610854@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox