Re: cache lookup failed when \d t concurrent with DML change column data type

From: Kirill Reshke <reshkekirill(at)gmail(dot)com>
To: Andrei Lepikhov <lepihov(at)gmail(dot)com>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: cache lookup failed when \d t concurrent with DML change column data type
Date: 2024-10-25 07:15:23
Message-ID: CALdSSPicAw2+HJe6PE-nQ+0Sk3e+nsHf8c-hO+uCLLPSo8Dfbw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 25 Oct 2024 at 09:51, Andrei Lepikhov <lepihov(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kirill Reshke 2024-10-25 07:31:45 Re: Useless field ispartitioned in CreateStmtContext
Previous Message Tender Wang 2024-10-25 06:51:28 Re: [BUG] Fix DETACH with FK pointing to a partitioned table fails