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

From: Huansong Fu <huansong(dot)fu(dot)info(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Quan Zongliang <quanzongliang(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: bugfix: invalid bit/varbit input causes the log file to be unreadable
Date: 2021-12-13 19:42:11
Message-ID: 3886A146-1632-49F4-B02E-5BECB3BA3D9E@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Quan Zongliang <quanzongliang(at)gmail(dot)com> writes:
>> I tested it, and it looks fine.
>
> Pushed, thanks for reporting the issue!
>
> regards, tom lane
>
>
>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2021-12-13 19:52:53 Re: extended stats on partitioned tables
Previous Message Andres Freund 2021-12-13 19:33:24 Re: port conflicts when running tests concurrently on windows.