Re: PANIC: wrong buffer passed to visibilitymap_clear

Peter Geoghegan <pg@bowt.ie>

View thread View on postgr.es

From: Peter Geoghegan <pg@bowt.ie>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Andres Freund <andres@anarazel.de>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2021-04-11T15:47:16Z

Lists: pgsql-hackers

Attachments

0001-Acquire-super-exclusive-lock-in-lazy_vacuum_heap_rel.patch (application/octet-stream) patch 0001

On Sat, Apr 10, 2021 at 10:04 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Just eyeing the evidence on hand, I'm wondering if something has decided
> it can start setting the page-all-visible bit without adequate lock,
> perhaps only in system catalogs.  heap_update is clearly assuming that
> that flag won't change underneath it, and if it did, it's clear how this
> symptom would ensue.

Does this patch seem to fix the problem?

-- 
Peter Geoghegan

Commits

Avoid improbable PANIC during heap_update.
- 5f12bc94dcc6 12.7 landed
- 37e76546a2ba 13.3 landed
- 34f581c39e97 14.0 landed
Refactor lazy_scan_heap() loop.
- 7ab96cf6b312 14.0 cited