diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-07-12 13:24:17 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-07-12 13:24:17 -0400 |
| commit | e439bbe9996f508f584cda9075d0bb3d5fbd7d97 (patch) | |
| tree | 0db0df200b146123cc380c56ef530d958322b6b0 /src/tutorial/funcs.source | |
| parent | a94dd0c25d0132a48c2f95505e0f95bb273f1160 (diff) | |
| download | postgresql-e439bbe9996f508f584cda9075d0bb3d5fbd7d97.tar.gz postgresql-e439bbe9996f508f584cda9075d0bb3d5fbd7d97.zip | |
Avoid integer overflow while sifting-up a heap in tuplesort.c.
If the number of tuples in the heap exceeds approximately INT_MAX/2,
this loop's calculation "2*i+1" could overflow, resulting in a crash.
Fix it by using unsigned int rather than int for the relevant local
variables; that shouldn't cost anything extra on any popular hardware.
Per bug #14722 from Sergey Koposov.
Original patch by Sergey Koposov, modified by me per a suggestion
from Heikki Linnakangas to use unsigned int not int64.
Back-patch to 9.4, where tuplesort.c grew the ability to sort as many
as INT_MAX tuples in-memory (commit 263865a48).
Discussion: https://postgr.es/m/20170629161637.1478.93109@wrigleys.postgresql.org
Diffstat (limited to 'src/tutorial/funcs.source')
0 files changed, 0 insertions, 0 deletions