aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorNeil Conway <neilc@samurai.com>2005-06-22 02:02:09 +0000
committerNeil Conway <neilc@samurai.com>2005-06-22 02:02:09 +0000
commit5ba26d48fc03eef2083768672548bde0bb6ddbbe (patch)
tree80b057d337869a2867f1409e8690654bd39d6287 /src/backend/access/gist/gist.c
parent5bcb851c92ae273a83dd5e314995941455d226ae (diff)
downloadpostgresql-5ba26d48fc03eef2083768672548bde0bb6ddbbe.tar.gz
postgresql-5ba26d48fc03eef2083768672548bde0bb6ddbbe.zip
Correct some code in pg_restore when reading the header of a tar archive:
(1) The code doesn't initialize `sum', so the initial "does the checksum match?" test is wrong. (2) The loop that is intended to check for a "null block" just checks the first byte of the tar block 512 times, rather than each of the 512 bytes one time (!), which I'm guessing was the intent. It was only through sheer luck that this worked in the first place. Per Coverity static analysis performed by EnterpriseDB.
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions