Re: Assert while autovacuum was executing - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Assert while autovacuum was executing
Date
Msg-id CAA4eK1+5F3RaeP46p=eQvA1=Ocx9+Ev-9Weo39soWQ2q=2HP0w@mail.gmail.com
Whole thread Raw
In response to Re: Assert while autovacuum was executing  (Andres Freund <andres@anarazel.de>)
Responses Re: Assert while autovacuum was executing
List pgsql-hackers
On Wed, Jun 21, 2023 at 10:57 AM Andres Freund <andres@anarazel.de> wrote:
>
> As far as I can tell 72e78d831a as-is is just bogus. Unfortunately that likely
> also means 3ba59ccc89 is not right.
>

Indeed. I was thinking of a fix but couldn't find one yet. One idea I
am considering is to allow catalog table locks after page lock but I
think apart from hacky that also won't work because we still need to
remove the check added for page locks in the deadlock code path in
commit 3ba59ccc89 and may need to do something for group locking. Feel
free to share any ideas if you have, I can try to evaluate those in
detail. I think in the worst case we need to remove the changes added
by 72e78d831a and 3ba59ccc89 which won't impact any existing feature
but will add a hurdle in parallelizing other write operations or even
improving the parallelism in vacuum (like allowing multiple workers
for an index).

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: allow granting CLUSTER, REFRESH MATERIALIZED VIEW, and REINDEX
Next
From: Nathan Bossart
Date:
Subject: Re: Preventing non-superusers from altering session authorization