When using Redshift - PostgresSyntaxError: syntax error at or near "ORDER" - in query with no "ORDER"

connection.fetch エントリポイントと再現されたクエリ select 'all' = any($1::text[]) から始め、Redshift での動作を報告された PostgreSQL Docker イメージでの動作と比較します。構文エラーが asyncpg と Redshift のどちらに起因するのかを特定し、確認済みの回避策または互換性の制限を文書化します。

• asyncpg version: asyncpg==0.27.0.
• PostgreSQL version: PostgreSQL 8.0.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2-6.fc3), Redshift 1.0.46987.
• Do you use a PostgreSQL SaaS? If so, which? Can you reproduce
  the issue with a local PostgreSQL install?: I am using Amazon Redshift. I could not reproduce the issue with potgres:9.0 Docker image.
• Python version: Python 3.9.12.
• Platform: Windows 10 Pro, 22H2, 19045.2604.
• Do you use pgbouncer?: No.
• Did you install asyncpg with pip?: Yes.
• If you built asyncpg locally, which version of Cython did you use?: -
• Can the issue be reproduced under both asyncio and
  uvloop?: Have not tried uvloop.

Running this snippet:

options = ConnectionOptions()

sslctx = ssl.create_default_context(ssl.Purpose.SERVER_AUTH)
sslctx.check_hostname = False
sslctx.verify_mode = ssl.CERT_NONE

connection = await asyncpg.connect(options.dsn, ssl=sslctx)

try:
    query = "select 'all' = any($1::text[])"
    await connection.fetch(query, ["all"])

finally:
    await connection.close()

I get this exception:

asyncpg.exceptions.PostgresSyntaxError: syntax error at or near "ORDER"

I am wondering, where the "syntax error at or near "ORDER" comes from, as there is no "ORDER" in the original query.

If asyncpg does not rewrite queries in any way, and the query passed to fetch is forwarded to the database without modification (https://github.com/MagicStack/asyncpg/issues/434#issuecomment-910474719, https://github.com/MagicStack/asyncpg/discussions/859#discussioncomment-1742492) - where does the "ORDER" come from?

Can this issue be worked around, or I should abandon asyncpg as a Redshift client? I do understand that Redshift is not officially supported, but this client is very good otherwise.

I was not able to reproduce the error with the postgres:9.0 instance (the oldest I was able to find quickly). The same (except ssl=False) snippet works without errors.