Re: BUG #18499: Reindexing spgist index concurrently triggers Assert("TransactionIdIsValid(state->myXid)")
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: exclusion@gmail.com, pgsql-bugs@lists.postgresql.org
Date: 2024-06-16T23:30:46Z
Lists: pgsql-bugs
Michael Paquier <michael@paquier.xyz> writes: > On Sun, Jun 16, 2024 at 06:52:52PM -0400, Tom Lane wrote: >> ... not sure there's a nice way for spginsert() to know whether it's >> being invoked in REINDEX CONCURRENTLY or a normal INSERT/UPDATE >> query. Can we trust indexInfo->ii_Concurrent for that? > I am not sure to understand the redirection part for spgist, but > except if I am missing something, we already rely on ii_Concurrent for > other index AMs like BRIN paths to check if we are dealing with a > concurrent build path or not. index_concurrently_build() is used > by both CIC and REINDEX CONCURRENTLY, where the flag is set after a > BuildIndexInfo(). Right. I was thinking that CIC wouldn't reach spginsert(), rather spgbuild(), but it does feel a bit rickety. A separate flag would be better. On the whole I'm inclined to stick with the patch as I have it. Maybe somebody would like to investigate this idea as an improvement for v18 or later. regards, tom lane
Commits
-
Fix insertion of SP-GiST REDIRECT tuples during REINDEX CONCURRENTLY.
- f55083319323 15.8 landed
- e4a55378f726 14.13 landed
- 92c49d1062f7 17.0 landed
- 507a900ad32c 13.16 landed
- 3e3e2ebea79c 12.20 landed
- 06f81fed3cdd 16.4 landed