Re: Error while copying a large file in pg_rewind
Michael Paquier <michael.paquier@gmail.com>
From: Michael Paquier <michael.paquier@gmail.com>
To: Kuntal Ghosh <kuntalghosh.2007@gmail.com>
Cc: Dilip Kumar <dilipbalaut@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>,
Heikki Linnakangas <hlinnaka@iki.fi>
Date: 2017-07-20T06:17:38Z
Lists: pgsql-hackers
On Fri, Jul 7, 2017 at 9:33 AM, Michael Paquier <michael.paquier@gmail.com> wrote: > On Fri, Jul 7, 2017 at 4:31 PM, Kuntal Ghosh <kuntalghosh.2007@gmail.com> wrote: >> On Fri, Jul 7, 2017 at 7:49 AM, Michael Paquier >> <michael.paquier@gmail.com> wrote: >> I don't have any more inputs on this patch and it looks good to me. >> So, I'm moving the status to ready for committer. > > Thanks! > >>> At some point it would really make sense to group all things under the >>> same banner (64-b LO, pg_basebackup, and now pg_rewind). >>> >> +1. Implementation-wise, I prefer pg_recvint64 to fe_recvint64. > > So do I. That's a matter of taste I guess. Heikki, this bug is rather bad for anybody using pg_rewind with relation file sizes larger than 2GB as this corrupts data of instances. I think that you would be the best fit as a committer to look at this patch as you implemented the tool first, and it would be a bad idea to let that sit for a too long time. Could it be possible to spare a bit of your time at some point to look at it? -- Michael
Commits
-
pg_rewind: Fix some problems when copying files >2GB.
- ed367be64b11 9.5.8 landed
- 73fbf3d3d0a5 9.6.4 landed
- a46fe6e8be02 10.0 landed
-
pg_rewind: Fix busted sanity check.
- c54e4a55f468 9.5.8 landed
- 0fe21602e27f 9.6.4 landed
- 063ff9210c54 10.0 landed
-
Code review for 64-bit-large-object patch.
- 26fe56481c0f 9.3.0 cited