Check for fseeko() failure in pg_dump's _tarAddFile(). Coverity pointed out, not unreasonably, that we checked fseeko's result at every other call site but these. Failure to seek in the temp file (note this is NOT pg_dump's output file) seems quite unlikely, and even if it did happen the file length cross-check further down would probably detect the problem. Still, that's a poor excuse for not checking the result of a system call.
Branch ------ REL_10_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/3ed76bd3592f9d476edc0616b527c6fdce71ce85 Modified Files -------------- src/bin/pg_dump/pg_backup_tar.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
