Re: fix typos - Mailing list pgsql-hackers

From Tom Lane
Subject Re: fix typos
Date
Msg-id 3437166.1659620465@sss.pgh.pa.us
Whole thread Raw
In response to Re: fix typos  (John Naylor <john.naylor@enterprisedb.com>)
Responses Re: fix typos
List pgsql-hackers
John Naylor <john.naylor@enterprisedb.com> writes:
> On Tue, Aug 2, 2022 at 1:11 AM Justin Pryzby <pryzby@telsasoft.com> wrote:
>   ereport(ERROR,
>   (errcode(ERRCODE_OBJECT_IN_USE),
> - errmsg("could not drop replication origin with OID %d, in use by PID %d",
> + errmsg("could not drop replication origin with OID %u, in use by PID %d",

> RepOriginId is a typedef for uint16, so this can't print the wrong answer,
> but it is inconsistent with other uses. So it seems we don't need to
> backpatch this one?

Um ... if it's int16, then it can't be an OID, so I'd say this message has
far worse problems than %d vs %u.  It should not use that terminology.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: ERREUR: cache lookup failed for function 0 with PostgreSQL 15 beta 2, no error with PostgreSQL 14.4
Next
From: Tom Lane
Date:
Subject: Re: Introduce wait_for_subscription_sync for TAP tests