Skip to content

Commit 6306d07

Browse files
committed
Re-enable error for "SELECT ... OFFSET -1".
The executor has thrown errors for negative OFFSET values since 8.4 (see commit bfce56e), but in a moment of brain fade I taught the planner that OFFSET with a constant negative value was a no-op (commit 1a1832e). 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.
1 parent f59c8ef commit 6306d07

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

src/backend/optimizer/plan/planner.c

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2127,7 +2127,7 @@ preprocess_limit(PlannerInfo *root, double tuple_fraction,
21272127
{
21282128
*offset_est = DatumGetInt64(((Const *) est)->constvalue);
21292129
if (*offset_est < 0)
2130-
*offset_est = 0; /* less than 0 is same as 0 */
2130+
*offset_est = 0; /* treat as not present */
21312131
}
21322132
}
21332133
else
@@ -2288,9 +2288,8 @@ limit_needed(Query *parse)
22882288
{
22892289
int64 offset = DatumGetInt64(((Const *) node)->constvalue);
22902290

2291-
/* Executor would treat less-than-zero same as zero */
2292-
if (offset > 0)
2293-
return true; /* OFFSET with a positive value */
2291+
if (offset != 0)
2292+
return true; /* OFFSET with a nonzero value */
22942293
}
22952294
}
22962295
else

0 commit comments

Comments
 (0)