Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15)
| От | Alexander Korotkov |
|---|---|
| Тема | Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15) |
| Дата | |
| Msg-id | CAPpHfduUf0UpG9LWXZHBwNhx7iZ1y_YO_u9paAjBi71fVgq3_A@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15) (Peter Eisentraut <peter.eisentraut@enterprisedb.com>) |
| Ответы |
Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15)
|
| Список | pgsql-hackers |
On Thu, Mar 17, 2022 at 4:23 PM Peter Eisentraut
<peter.eisentraut@enterprisedb.com> wrote:
> On 17.03.22 14:12, Aleksander Alekseev wrote:
> > v19-0001 changes the format string for XIDs from %u to XID_FMT. This
> > refactoring allows us to switch to UINT64_FORMAT by changing one
> > #define in the future patches.
> >
> > Kyotaro suggested using `errmsg("blah blah %lld ..", (long long)
> > xid)` instead in order to simplify localization of the error messages.
> > Personally I don't have a strong opinion here. Either approach will
> > work and will affect the error messages eventually. Please let us know
> > what you think.
>
> This is not a question of simplification. Translatable messages with
> embedded macros won't work. This patch isn't going to be acceptable.
I've suspected this, but wasn't sure. Thank you for clarification.
------
Regards,
Alexander Korotkov
В списке pgsql-hackers по дате отправления: