On 10/25/24 14:15, Kirill Reshke wrote:
> On Fri, 25 Oct 2024 at 09:51, Andrei Lepikhov <lepihov@gmail.com> wrote:
>>
>> It may be have made sense to lock the row of replaced index in pg_class
>> and pg_index until the transaction, altered it will be commmitted. But,
>> because ALTER TABLE is not fully MVCC-safe, it may be expected (or
>> acceptable) behaviour.
>
> I suspect this is the case. If that is, should be reflect it in the doc?
We already have the doc entry on such cases [1]. This is a suitable
place to change if someone wants to detail this 'failed cache lookup' case.
[1] https://www.postgresql.org/docs/16/mvcc-caveats.html
--
regards, Andrei Lepikhov
