Re: Re: [COMMITTERS] pgsql: pg_rewind: Fix some problems when copying files >2GB.
Michael Paquier <michael.paquier@gmail.com>
From: Michael Paquier <michael.paquier@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-08-29T02:22:12Z
Lists: pgsql-hackers
Attachments
- rewind-int64-log.patch (application/octet-stream) patch
On Mon, Aug 28, 2017 at 11:24 PM, Robert Haas <robertmhaas@gmail.com> wrote: > On Mon, Aug 28, 2017 at 10:16 AM, Alvaro Herrera > <alvherre@2ndquadrant.com> wrote: >>> I am fine with however you want to handle it, but it seems odd to me >>> that we don't have a way of embedding INT64_FORMAT in a translatable >>> string. Surely that's going to be a problem in some case, sometime, >>> isn't it? >> >> The way we do that elsewhere is to print out the value to a string >> variable and then use %s in the translatable message. > > Hmm. OK. That doesn't sound great, but if there's no better option... 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? -- Michael
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