Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
Date
Msg-id arR6vutn730-lQ84@paquier.xyz
Whole thread
In response to Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks  (Ayush Tiwari <ayushtiwari.slg01@gmail.com>)
Responses Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
List pgsql-bugs
On Thu, Sep 24, 2026 at 01:09:12AM +0530, Ayush Tiwari wrote:
> I don't have much background on the lock levels needed here, but taking
> AccessExclusiveLock upfront seems reasonable given the storage replacement.
> I'm less sure whether it's too strong for cases like OWNED BY.
> [I've sent a diff upthread, can add a patch if that's the right way to go]
>
> Cc'ing Andres, Michael and Peter, who were involved in the original
> sequence locking and transactional changes. Does this approach make
> sense, or am I missing something here?

Where do you mean to add this extra level of locking?
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: shihao zhong
Date:
Subject: Re: BUG #19708: Hash Join becomes about 300x slower with higher work_mem
Next
From: shihao zhong
Date:
Subject: Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows