Re: PANIC: wrong buffer passed to visibilitymap_clear

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PANIC: wrong buffer passed to visibilitymap_clear
Date: 2021-04-09 23:27:12
Message-ID: CAH2-WzmUvJDU9MVzXtJc0QWr8mykeWMph9NM2+d8BvBcjja63g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 9, 2021 at 3:40 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Buildfarm members spurfowl[1] and thorntail[2] have each shown $SUBJECT
> once in the past two days. The circumstances are not quite the same;
> spurfowl's failure is in autovacuum while thorntail's is in a manual
> VACUUM command. Still, it seems clear that there's a recently-introduced
> bug here somewhere. I don't see any obvious candidate for the culprit,
> though. Any ideas?

They're both VACUUM ANALYZE. They must be, because the calls to
visibilitymap_clear PANIC (they don't ERROR) -- the failing
visibilitymap_clear() call must occur inside a critical section, and
all such calls are made within heapam.c (only VACUUM ANALYZE uses a
transaction and does writes). It cannot be the two calls to
visibilitymap_clear() inside vacuumlazy.c.

I suspect that you've figured this much already. Just pointing it out.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2021-04-09 23:27:39 Re: PANIC: wrong buffer passed to visibilitymap_clear
Previous Message Alvaro Herrera 2021-04-09 23:02:38 Re: pgsql: Add libpq pipeline mode support to pgbench