Re: Remove INT64_FORMAT in translatable strings

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Japin Li <japinli(at)hotmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Remove INT64_FORMAT in translatable strings
Date: 2022-03-18 17:32:25
Message-ID: 20220318173225.GR28503@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 18, 2022 at 01:12:40PM -0400, Tom Lane wrote:
> Japin Li <japinli(at)hotmail(dot)com> writes:
> > we can rely on %lld/%llu and we decided to use them in translatable strings.
>
> Seems like good cleanup, so pushed. I think though that project style
> is to use "long long" or "unsigned long long", without the unnecessary
> "int" --- it certainly makes little sense to do it both ways in the
> same patch.

This seemed familiar - it's about the same thing I sent here, while fixing
ftello().

https://www.postgresql.org/message-id/flat/20210104025321(dot)GA9712(at)telsasoft(dot)com
0002-Fix-broken-error-message-on-unseekable-input.patch

--
Justin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Imseih (AWS), Sami 2022-03-18 17:32:45 Re: [PATCH] pgbench: add multiconnect option
Previous Message Tom Lane 2022-03-18 17:29:41 Re: pgsql: Add option to use ICU as global locale provider