Re: PANIC: wrong buffer passed to visibilitymap_clear

From: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
To: 王伟(学弈) <rogers(dot)ww(at)alibaba-inc(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PANIC: wrong buffer passed to visibilitymap_clear
Date: 2022-07-22 10:06:21
Message-ID: b88768d2-a568-a81b-71c5-c7009168bab3@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7/22/22 10:22, 王伟(学弈) wrote:
> Hi,
> I recently find this problem while testing PG14 with sysbench.
> Then I look through the emails from pgsql-hackers and find a previous
> similary bug which
> is https://www.postgresql.org/message-id/flat/2247102.1618008027%40sss.pgh.pa.us
> <https://www.postgresql.org/message-id/flat/2247102.1618008027%40sss.pgh.pa.us>.
> But the bugfix commit(34f581c39e97e2ea237255cf75cccebccc02d477) is
> already patched to PG14.
>

Which PG14 version / commit is this, exactly? What sysbench parameters
did you use, how likely is hitting the issue?

regards

--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2022-07-22 10:15:52 Re: [PATCH v1] eliminate duplicate code in table.c
Previous Message Aleksander Alekseev 2022-07-22 09:42:20 Re: Add connection active, idle time to pg_stat_activity