forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commite0271d5
committed
Remove useless range checks on INT8 sequences
There's no point in checking if an INT8 sequence has a seqmin and seqmaxvalue is outside the range of the minimum and maximum values for an int64type. These both use the same underlying types so an INT8 certainlycannot be outside the minimum and maximum values supported by int64.This code is fairly harmless and it seems likely that most compilerswould optimize it out anyway, never-the-less, let's remove it replacingit with a small comment to mention why the check is not needed.Author: Greg Nancarrow, with the comment revised by David RowleyDiscussion:https://postgr.es/m/CAJcOf-c9KBUZ8ow_6e%3DWSfbbEyTKfqV%3DVwoFuODQVYMySHtusw%40mail.gmail.com1 parent5bd38d2 commite0271d5
1 file changed
+4
-4
lines changedLines changed: 4 additions & 4 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
1460 | 1460 |
| |
1461 | 1461 |
| |
1462 | 1462 |
| |
| 1463 | + | |
1463 | 1464 |
| |
1464 |
| - | |
1465 |
| - | |
| 1465 | + | |
1466 | 1466 |
| |
1467 | 1467 |
| |
1468 | 1468 |
| |
| |||
1497 | 1497 |
| |
1498 | 1498 |
| |
1499 | 1499 |
| |
| 1500 | + | |
1500 | 1501 |
| |
1501 |
| - | |
1502 |
| - | |
| 1502 | + | |
1503 | 1503 |
| |
1504 | 1504 |
| |
1505 | 1505 |
| |
|
0 commit comments
Comments
(0)