| From: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
|---|---|
| To: | Kirill Reshke <reshkekirill(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com> |
| Cc: | 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 08:07:19 |
| Message-ID: | e70561d3-e78f-445e-a80b-c52808e3a569@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/25/24 14:15, Kirill Reshke wrote:
> 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?
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2024-10-25 08:14:03 | Re: Docs Build in CI failing with "failed to load external entity" |
| Previous Message | Daniil Davydov | 2024-10-25 08:02:37 | Forbid to DROP temp tables of other sessions |