Horton

Re: bugfix: invalid bit/varbit input causes the log file to be unreadable

Huansong Fu <huansong.fu.info@gmail.com>

View thread View on postgr.es
From: Huansong Fu <huansong.fu.info@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Quan Zongliang <quanzongliang@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2021-12-13T19:42:11Z
Lists: pgsql-hackers 
Hi, 

We recently saw a similar issue in v12 and wondered why the corresponding fix for v14 (https://github.com/postgres/postgres/commit/16e3ad5d143) was not backported to v13 and before. The commit message did mention that this fix might have problem with translatable string messages - would you mind providing a bit more context about what is needed to backport this fix? Thank you.

Regards,
Huansong
https://vmware.com/ <https://vmware.com/>

> On Jun 29, 2020, at 11:42 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
> Quan Zongliang <quanzongliang@gmail.com> writes:
>> I tested it, and it looks fine.
> 
> Pushed, thanks for reporting the issue!
> 
> 			regards, tom lane
> 
> 
> 
>

Commits

  1. Avoid using %c printf format for potentially non-ASCII characters.