Re: pg_verifybackup: TAR format backup verification
От | Tom Lane |
---|---|
Тема | Re: pg_verifybackup: TAR format backup verification |
Дата | |
Msg-id | 1636465.1727733671@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: pg_verifybackup: TAR format backup verification (Robert Haas <robertmhaas@gmail.com>) |
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: > On Mon, Sep 30, 2024 at 11:24 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Um, wait ... we do have strtou64(), so you should use that. > The thing we should be worried about is not how large a JSON blob > might be, but rather how large any file that appears in the data > directory might be. So uint32 is out; and I think I hear you voting > for uint64 over size_t. Yes. size_t might only be 32 bits. > But then how do you think we should print > that? Cast to unsigned long long and use %llu? Our two standard solutions are to do that or to use UINT64_FORMAT. But UINT64_FORMAT is problematic in translatable strings because then the .po files would become platform-specific, so long long is what to use in that case. For a non-translated format string you can do either. > I don't understand what you think the widely-used, better solution is > here. What we just said above. regards, tom lane
В списке pgsql-hackers по дате отправления: