diff options
| author | Etsuro Fujita <efujita@postgresql.org> | 2024-06-07 17:45:06 +0900 |
|---|---|---|
| committer | Etsuro Fujita <efujita@postgresql.org> | 2024-06-07 17:45:06 +0900 |
| commit | 269e2c39162811a170d7e8f87a1a0bde3b9e2fab (patch) | |
| tree | b3830b8974fbca66a04620c67bb3f72b2bd9fe61 /src/backend/executor/nodeModifyTable.c | |
| parent | 788c23003f4c42d9114fa8e9881ccea870187da5 (diff) | |
| download | postgresql-269e2c39162811a170d7e8f87a1a0bde3b9e2fab.tar.gz postgresql-269e2c39162811a170d7e8f87a1a0bde3b9e2fab.zip | |
postgres_fdw: Refuse to send FETCH FIRST WITH TIES to remote servers.
Previously, when considering LIMIT pushdown, postgres_fdw failed to
check whether the query has this clause, which led to pushing false
LIMIT clauses, causing incorrect results.
This clause has been supported since v13, so we need to do a
remote-version check before deciding that it will be safe to push such a
clause, but we do not currently have a way to do the check (without
accessing the remote server); disable pushing such a clause for now.
Oversight in commit 357889eb1. Back-patch to v13, where that commit
added the support.
Per bug #18467 from Onder Kalaci.
Patch by Japin Li, per a suggestion from Tom Lane, with some changes to
the comments by me. Review by Onder Kalaci, Alvaro Herrera, and me.
Discussion: https://postgr.es/m/18467-7bb89084ff03a08d%40postgresql.org
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions