aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistget.c
diff options
context:
space:
mode:
authorDavid Rowley <drowley@postgresql.org>2023-01-24 13:49:10 +1300
committerDavid Rowley <drowley@postgresql.org>2023-01-24 13:49:10 +1300
commit9567686ec834e50ab10ae872a8394c9a9e590b0d (patch)
tree9b90fa0575db2ad7fe74b41270bbba9297283bf5 /src/backend/access/gist/gistget.c
parentb762fed6481e722a022ac2bea02151e080c31fa6 (diff)
downloadpostgresql-9567686ec834e50ab10ae872a8394c9a9e590b0d.tar.gz
postgresql-9567686ec834e50ab10ae872a8394c9a9e590b0d.zip
Use OFFSET 0 instead of ORDER BY to stop subquery pullup
b762fed64 recently changed this test to prevent subquery pullup to allow us to test Memoize with lateral_vars. As pointed out by Tom Lane, OFFSET 0 is our standard way of preventing subquery pullups, so do it that way instead. Discussion: https://postgr.es/m/2144818.1674517061@sss.pgh.pa.us Backpatch-through: 14, same as b762fed64
Diffstat (limited to 'src/backend/access/gist/gistget.c')
0 files changed, 0 insertions, 0 deletions