Re: Assertion on create index concurrently
Andrei Lepikhov <a.lepikhov@postgrespro.ru>
From: Andrey Lepikhov <a.lepikhov@postgrespro.ru>
To: Tom Lane <tgl@sss.pgh.pa.us>, Michael Paquier <michael@paquier.xyz>
Cc: pgsql-bugs@lists.postgresql.org
Date: 2021-06-27T19:33:44Z
Lists: pgsql-bugs
Attachments
- 0001-Back-patch-of-83158f7-for-PG9_6.patch (text/plain) patch 0001
On 27/6/21 18:37, Tom Lane wrote: > Michael Paquier <michael@paquier.xyz> writes: >> On Sat, Jun 26, 2021 at 09:48:45PM +0300, Andrey Lepikhov wrote: >>> This problem affects PG 9.6 - 13. The master branch was fixed 9 months ago >>> by commit 83158f7, that made this operation transactional, but still. > >> This looks like a good argument for back-patching 83158f7 all the way >> down, as 813fb03 exists since 9.4. Any thoughts from others? > > +1 ... 83158f7 has survived long enough to have reasonable confidence > in it. Technically, 83158f7 is trivial patch. I think, some efforts is required only for PG9.6. I prepared a patch for this version. -- regards, Andrey Lepikhov Postgres Professional
Commits
-
Add test for CREATE INDEX CONCURRENTLY with not-so-immutable predicate
- 21257a8f6dcb 9.6.23 landed
- 5160d5bb1662 10.18 landed
- 38ca11adeb5a 11.13 landed
- ce8949c4b6e2 12.8 landed
- fd7bc10ab4c6 13.4 landed
- 09a69f6e2336 14.0 landed
-
Make index_set_state_flags() transactional
- d3d0cbeb6232 9.6.23 landed
- 3c465883b8a6 10.18 landed
- 08acba558bba 11.13 landed
- e52f7cbec16c 12.8 landed
- acb60edf0254 13.4 landed
- 83158f74d3ab 14.0 cited