aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistget.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2019-09-06 08:22:32 -0400
committerRobert Haas <rhaas@postgresql.org>2019-09-06 08:22:32 -0400
commit286af0ce12117bc673b97df6228d1a666594d247 (patch)
treeb635b99d7101791218a77a6ce9ffac12c691b4ff /src/backend/access/gist/gistget.c
parent5599f40d259a275d3202b10aa6ffb9a36fd8a940 (diff)
downloadpostgresql-286af0ce12117bc673b97df6228d1a666594d247.tar.gz
postgresql-286af0ce12117bc673b97df6228d1a666594d247.zip
When performing a base backup, check for read errors.
The old code didn't differentiate between a read error and a concurrent truncation. fread reports both of these by returning 0; you have to use feof() or ferror() to distinguish between them, which this code did not do. It might be a better idea to use read() rather than fread() here, so that we can display a less-generic error message, but I'm not sure that would qualify as a back-patchable bug fix, so just do this much for now. Jeevan Chalke, reviewed by Jeevan Ladhe and by me. Discussion: http://postgr.es/m/CA+TgmobG4ywMzL5oQq2a8YKp8x2p3p1LOMMcGqpS7aekT9+ETA@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gistget.c')
0 files changed, 0 insertions, 0 deletions