Re: Re: [COMMITTERS] pgsql: pg_rewind: Fix some problems when copying files >2GB.
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael.paquier@gmail.com>,
Robert Haas <robertmhaas@gmail.com>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-09-07T01:11:51Z
Lists: pgsql-hackers
On 9/4/17 06:03, Alvaro Herrera wrote: > Tom Lane wrote: >> Michael Paquier <michael.paquier@gmail.com> writes: >>> I don't like breaking the abstraction of pg_log() with the existing >>> flags with some kind of pg_debug() layer. The set of APIs present now >>> in pg_rewind for logging is nice to have, and I think that those debug >>> messages should be translated. So what about the attached? >> >> Your point about INT64_FORMAT not necessarily working with fprintf >> is an outstanding reason not to keep it like it is. I've not reviewed >> this patch in detail but I think this is basically the way to fix it. > > Actually this code goes throgh vsnprintf, not fprintf, which should be > safe, so I removed that part of the comment, and pushed. Is there a reason this was not backpatched to 9.5? -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Fix translatable string
- 8d5ec8ee3809 9.5.10 landed
- a1af1e7cfaef 10.0 landed
- bd75335a83bf 9.6.6 landed
- 863d75439e87 11.0 landed
-
pg_rewind: Fix some problems when copying files >2GB.
- 73fbf3d3d0a5 9.6.4 cited