| 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 16:43:15 |
| Message-ID: | CAH2-WzkCXg6RQJdc_7ZGHcKvyoJAfFu9R2ZVAiE9mCcOfaXJdQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Apr 11, 2021 at 9:10 AM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> I don't have any reason to believe that using a super-exclusive lock
> during heap page vacuuming is necessary. My guess is that returning to
> doing it that way might make the buildfarm green again. That would at
> least confirm my suspicion that this code is relevant. The
> super-exclusive lock might have been masking the problem for a long
> time.
This isn't just any super-exclusive lock, either -- we were calling
ConditionalLockBufferForCleanup() at this point.
I now think that there is a good chance that we are seeing these
symptoms because the "conditional-ness" went away -- we accidentally
relied on that.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2021-04-11 16:51:27 | Re: PL/R regression on windows, but not linux with master. |
| Previous Message | Tom Lane | 2021-04-11 16:42:58 | Re: PL/R regression on windows, but not linux with master. |