| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PANIC: wrong buffer passed to visibilitymap_clear |
| Date: | 2021-04-11 15:47:16 |
| Message-ID: | CAH2-WzmWOLaWhQgEC1BJN0JZpOCOwxCAhjmd2Nd4yh4wrqju8Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Apr 10, 2021 at 10:04 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Acquire-super-exclusive-lock-in-lazy_vacuum_heap_rel.patch | application/octet-stream | 1.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-04-11 15:57:50 | Re: PANIC: wrong buffer passed to visibilitymap_clear |
| Previous Message | Tom Lane | 2021-04-11 15:34:02 | Re: PL/R regression on windows, but not linux with master. |