| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Subject: | Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data |
| Date: | 2021-08-22 17:42:01 |
| Message-ID: | 5F423E04-BDAE-42AC-9CEF-1E37F6F345DF@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> 22 авг. 2021 г., в 17:30, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> написал(а):
>
> I've observed few times that same Xid was WaitXact()'es twice. Is it possible that taking ShareLock on running xid (taken from PGPGROC of vxid) is not a good way to wait for transaction completition?
> Is it possible that xid is in PGPROC before backend acquires its own lock on xid?
Oh, that's it. We first publish xid in PGPROC and only then take a lock in lock manager on it.
Ok, I know how to fix this.
Currently when testing combination of all fixes I observe things like
'error running SQL: 'psql:<stdin>:1: ERROR: prepared transaction with identifier "a" is busy''
Looks like kind of race condition in tests.
Thanks!
Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2021-08-22 18:38:49 | Re: BUG #17070: Sometimes copy from ingnores transaction |
| Previous Message | Andrey Borodin | 2021-08-22 12:30:47 | Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data |