aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/json.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-07-22 13:30:01 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2014-07-22 13:30:14 -0400
commit6306d07122d8b6678f47c273165540de02a0d242 (patch)
tree1598a69d5b07d7faa498b995752569dffb9e3c68 /src/backend/utils/adt/json.c
parentf59c8eff7dd3dea4116a34e1890ee219f6d7f8d5 (diff)
downloadpostgresql-6306d07122d8b6678f47c273165540de02a0d242.tar.gz
postgresql-6306d07122d8b6678f47c273165540de02a0d242.zip
Re-enable error for "SELECT ... OFFSET -1".
The executor has thrown errors for negative OFFSET values since 8.4 (see commit bfce56eea45b1369b7bb2150a150d1ac109f5073), but in a moment of brain fade I taught the planner that OFFSET with a constant negative value was a no-op (commit 1a1832eb085e5bca198735e5d0e766a3cb61b8fc). Reinstate the former behavior by only discarding OFFSET with a value of exactly 0. In passing, adjust a planner comment that referenced the ancient behavior. Back-patch to 9.3 where the mistake was introduced.
Diffstat (limited to 'src/backend/utils/adt/json.c')
0 files changed, 0 insertions, 0 deletions