Re: Remove INT64_FORMAT in translatable strings - Mailing list pgsql-hackers

From Justin Pryzby
Subject Re: Remove INT64_FORMAT in translatable strings
Date
Msg-id 20220318173225.GR28503@telsasoft.com
Whole thread Raw
In response to Re: Remove INT64_FORMAT in translatable strings  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Mar 18, 2022 at 01:12:40PM -0400, Tom Lane wrote:
> Japin Li <japinli@hotmail.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.GA9712@telsasoft.com
0002-Fix-broken-error-message-on-unseekable-input.patch

-- 
Justin



pgsql-hackers by date:

Previous
From: Zheng Li
Date:
Subject: Re: Support logical replication of DDLs
Next
From: "Imseih (AWS), Sami"
Date:
Subject: Re: [PATCH] pgbench: add multiconnect option