Postgres Pro
Downloads
Home   >   mailing lists

Re: cache lookup failed when \d t concurrent with DML change column data type - Mailing list pgsql-hackers

From Kirill Reshke
Subject Re: cache lookup failed when \d t concurrent with DML change column data type
Date
Msg-id CALdSSPicAw2+HJe6PE-nQ+0Sk3e+nsHf8c-hO+uCLLPSo8Dfbw@mail.gmail.com
Whole thread Raw
In response to Re: cache lookup failed when \d t concurrent with DML change column data type  (Andrei Lepikhov <lepihov@gmail.com>)
Responses Re: cache lookup failed when \d t concurrent with DML change column data type
List pgsql-hackers
Tree view 
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?


-- 
Best regards,
Kirill Reshke

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Pgoutput not capturing the generated columns
Next
From: Kirill Reshke
Date:
Subject: Re: Useless field ispartitioned in CreateStmtContext