| From: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Smolkin Grigory <smallkeen(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: race condition in pg_class |
| Date: | 2023-10-25 12:57:11 |
| Message-ID: | 2B34E318-9FC7-40B4-B156-FC2EC7F9262A@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 25 Oct 2023, at 13:39, Smolkin Grigory <smallkeen(at)gmail(dot)com> wrote:
>
> We are running PG13.10 and recently we have encountered what appears to be a bug due to some race condition between ALTER TABLE ... ADD CONSTRAINT and some other catalog-writer, possibly ANALYZ
> I've tried to reproduce this scenario with CREATE INDEX and various concurrent statements, but no luck.
Maybe it would be possible to reproduce with modifying tests for concurrent index creation. For example add “ANALYZE” here [0].
Keep in mind that for easier reproduction it would make sense to increase transaction count radically.
Best regards, Andrey Borodin.
[0] https://github.com/postgres/postgres/blob/master/contrib/amcheck/t/002_cic.pl#L34
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Zubkov | 2023-10-25 13:00:23 | Re: [PATCH] Tracking statements entry timestamp in pg_stat_statements |
| Previous Message | Aleksander Alekseev | 2023-10-25 12:43:54 | Re: RFC: Pluggable TOAST |