aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/network_gist.c
diff options
context:
space:
mode:
authorDavid Rowley <drowley@postgresql.org>2023-01-24 13:49:39 +1300
committerDavid Rowley <drowley@postgresql.org>2023-01-24 13:49:39 +1300
commit5dc582da6b9a281321e687ae2b52f96b929d8d0e (patch)
treec7200e03590230453cc9372b99c6698a5c440469 /src/backend/utils/adt/network_gist.c
parent73f77ab508d1514ca604c47b6f56c5dee4dd9025 (diff)
downloadpostgresql-5dc582da6b9a281321e687ae2b52f96b929d8d0e.tar.gz
postgresql-5dc582da6b9a281321e687ae2b52f96b929d8d0e.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/utils/adt/network_gist.c')
0 files changed, 0 insertions, 0 deletions