Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data
Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
From: Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
To: Noah Misch <noah@leadboat.com>
Cc: CM Team <cm@enterprisedb.com>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>,
Michael Paquier <michael@paquier.xyz>, Tom Lane <tgl@sss.pgh.pa.us>, Peter Geoghegan <pg@bowt.ie>,
Andres Freund <andres@anarazel.de>, Andrey Borodin <x4mmm@yandex-team.ru>
Date: 2021-10-30T06:09:18Z
Lists: pgsql-bugs
Hi Noah, On Thu, Oct 28, 2021 at 7:35 PM Noah Misch <noah@leadboat.com> wrote: > On Sun, Oct 24, 2021 at 04:35:02PM -0700, Noah Misch wrote: > > On Sat, Oct 23, 2021 at 10:00:28PM -0700, Noah Misch wrote: > > > Pushed. > > > > cm@enterprisedb.com, could you post a stack trace from buildfarm member > > gharial failing in "make check"? I'm looking for a trace from a SIGSEGV > like > > those seen today: > > > > > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gharial&dt=2021-10-24%2016%3A19%3A05 > > > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gharial&dt=2021-10-24%2020%3A38%3A39 > > > > Those SIGSEGV are all in ALTER TABLE. My commits from this thread > probably > > broke something, but I've run out of ideas, and my hpux boxes died. > > cm@enterprisedb.com, is this still in your queue, or not? I am somewhat > concerned that the 2021-11-11 releases will contain a regression if the > gharial failures remain undiagnosed. I don't know how to diagnose them > without your help. (I currently can't justify reverting the suspect bug > fix > on the basis of two master-branch-only failures in one buildfarm member.) > > Sorry for responding late as this email was missed somehow :-( I checked the reports on the dashboard and there was a failure then but the reports after 25th Oct looks fine. The back branches all look fine as well. https://buildfarm.postgresql.org/cgi-bin/show_history.pl?nm=gharial&br=HEAD Please let me know if I missed something -- Sandeep Thakkar
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Improve contrib/amcheck's tests for CREATE INDEX CONCURRENTLY.
- b1f943d2aa7e 14.1 landed
- 7f580aa5d88a 15.0 landed
- 5a4b8a8a720c 13.5 landed
- 141cd0ef0b0b 12.9 landed
-
Fix minor memory leaks in pg_dump.
- 70bef494000e 15.0 cited
-
Avoid race in RelationBuildDesc() affecting CREATE INDEX CONCURRENTLY.
- e428699cb3be 9.6.24 landed
- db86746fd11e 10.19 landed
- 5141e471b36a 11.14 landed
- dde966efb286 14.1 landed
- 2e33b43599ad 13.5 landed
- 0869e53d3a07 12.9 landed
- fdd965d074d4 15.0 landed
-
Fix CREATE INDEX CONCURRENTLY for the newest prepared transactions.
- df6158139f64 11.14 landed
- 560124a37c2f 10.19 landed
- 5184932432b4 9.6.24 landed
- fe5d44a1d38f 12.9 landed
- a9d0a5409415 13.5 landed
- a5b9a0000e14 14.1 landed
- 3cd9c3b92197 15.0 landed
-
Add -w back to the flags for pg_ctl (re)start in PostgresNode
- b33259e261ae 15.0 cited
-
Fix CREATE INDEX CONCURRENTLY for simultaneous prepared transactions.
- 77a0e14f0b21 9.5.25 landed
- d683d6528dba 9.6.21 landed
- 179775135b41 10.16 landed
- d1ab4bf6ed2d 11.11 landed
- be843ce29737 12.6 landed
- 86a5b309c933 13.2 landed
- 8a54e12a38d1 14.0 landed