Re: log message in proto.c - Mailing list pgsql-hackers

From Robert Haas
Subject Re: log message in proto.c
Date
Msg-id CA+Tgmob1vsEr+kPrWjqdr7QK7Gx8R3mX4G+Ha9pwrQys66Hupw@mail.gmail.com
Whole thread Raw
In response to log message in proto.c  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Tue, Sep 24, 2019 at 5:41 AM Fujii Masao <masao.fujii@gmail.com> wrote:
> src/backend/replication/logical/proto.c
> action = pq_getmsgbyte(in);
> if (action != 'N')
>     elog(ERROR, "expected new tuple but got %d",
>     action);
>
> "%d" in the above message should be "%c" because the type of
> the variable "action" is char? There are other log messages that
> "%c" is used for such variable, in proto.c. Seems the above is
> only message that "%d" is used for such variable.

The potential problem with using %c to print characters is that the
character might be a null byte or something else that ends up making
the log file invalid under the relevant encoding.

However, if the goal of using %d is to protect against such problems,
it has to be done consistently.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PostgreSQL12 and older versions of OpenSSL
Next
From: Robert Haas
Date:
Subject: Re: WIP/PoC for parallel backup