Re: pgsql: Refer to replication origin roident as "ID" in user facing messa - Mailing list pgsql-committers

From John Naylor
Subject Re: pgsql: Refer to replication origin roident as "ID" in user facing messa
Date
Msg-id CAFBsxsHTYN2ZduDS1usP6_R0aN=TrW=zt7ZcZLS-iUKD8XOqpQ@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Refer to replication origin roident as "ID" in user facing messa  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-committers
On Mon, Aug 22, 2022 at 9:35 PM Peter Eisentraut
<peter.eisentraut@enterprisedb.com> wrote:
>
> On 19.08.22 03:06, John Naylor wrote:
> > On Thu, Aug 18, 2022 at 4:49 PM Peter Eisentraut
> > <peter.eisentraut@enterprisedb.com> wrote:
> >>
> >> On 18.08.22 04:10, John Naylor wrote:
> >>> While at it, most format strings already use %u, so for consintency
> >>> change the remaining stragglers using %d.
> >>
> >> This is incorrect.  Replication origin IDs are of type uint16, which
> >> gets promoted to int in a variable arguments list, so %d is the correct
> >> placeholder.
> >
> > I would think that for uint16, either %d or %u would have the same
> > result. Is there some other consideration I'm not aware of?
>
> Every once in a while, I build PostgreSQL with -Wformat-signedness,
> which often finds issues with OIDs and timeline IDs printed with the
> wrong placeholder.  There is a lot of noise to skip past when doing
> that, but in the long run it would be nice if we didn't add more of it.

Thanks for the info; I've pushed a patch.

-- 
John Naylor
EDB: http://www.enterprisedb.com



pgsql-committers by date:

Previous
From: John Naylor
Date:
Subject: pgsql: Switch format specifier for replication origins to %d
Next
From: Andres Freund
Date:
Subject: pgsql: pgstat: Acquire lock when reading variable-numbered stats