Re: pgsql: Refer to replication origin roident as "ID" in user facing messa

From: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: John Naylor <john(dot)naylor(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Refer to replication origin roident as "ID" in user facing messa
Date: 2022-08-23 02:58:49
Message-ID: CAFBsxsHTYN2ZduDS1usP6_R0aN=TrW=zt7ZcZLS-iUKD8XOqpQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Mon, Aug 22, 2022 at 9:35 PM Peter Eisentraut
<peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>
> On 19.08.22 03:06, John Naylor wrote:
> > On Thu, Aug 18, 2022 at 4:49 PM Peter Eisentraut
> > <peter(dot)eisentraut(at)enterprisedb(dot)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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2022-08-23 03:20:16 pgsql: pgstat: Acquire lock when reading variable-numbered stats
Previous Message John Naylor 2022-08-23 02:57:51 pgsql: Switch format specifier for replication origins to %d