Re: [HACKERS] Re: [COMMITTERS] pgsql: pg_rewind: Fix some problemswhen copying files >2GB.
От | Alvaro Herrera |
---|---|
Тема | Re: [HACKERS] Re: [COMMITTERS] pgsql: pg_rewind: Fix some problemswhen copying files >2GB. |
Дата | |
Msg-id | 20170830233918.4f6oakae5xrk2h5a@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: [HACKERS] Re: [COMMITTERS] pgsql: pg_rewind: Fix some problemswhen copying files >2GB. (Michael Paquier <michael.paquier@gmail.com>) |
Ответы |
Re: [HACKERS] Re: [COMMITTERS] pgsql: pg_rewind: Fix some problemswhen copying files >2GB.
|
Список | pgsql-hackers |
Michael Paquier wrote: > On Tue, Aug 29, 2017 at 11:26 AM, Tom Lane <tgl@sss.pgh.pa.us> 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. > > So, perhaps it would be better to fix that before the next point release? Sure, I'll get it done on Friday, or tomorrow if I can manage it. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: