aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeAgg.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-07-17 12:14:28 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2020-07-17 13:04:05 -0400
commita8d0732ac2b5527ce47cce5b325f8df93f4d19cc (patch)
tree89e2eb746d32200fc5a2a3bf65ee253cc6b22a30 /src/backend/executor/nodeAgg.c
parent5da8bf8bbb5c119d4bd767dbdfaf10efd348c0fd (diff)
downloadpostgresql-a8d0732ac2b5527ce47cce5b325f8df93f4d19cc.tar.gz
postgresql-a8d0732ac2b5527ce47cce5b325f8df93f4d19cc.zip
Remove manual tracking of file position in pg_dump/pg_backup_custom.c.
We do not really need to track the file position by hand. We were already relying on ftello() whenever the archive file is seekable, while if it's not seekable we don't need the file position info anyway because we're not going to be able to re-write the TOC. Moreover, that tracking was buggy since it failed to account for the effects of fseeko(). Somewhat remarkably, that seems not to have made for any live bugs up to now. We could fix the oversights, but it seems better to just get rid of the whole error-prone mess. In itself this is merely code cleanup. However, it's necessary infrastructure for an upcoming bug-fix patch (because that code *does* need valid file position after fseeko). The bug fix needs to go back as far as v12; hence, back-patch that far. Discussion: https://postgr.es/m/CALBH9DDuJ+scZc4MEvw5uO-=vRyR2=QF9+Yh=3hPEnKHWfS81A@mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeAgg.c')
0 files changed, 0 insertions, 0 deletions