Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data
От | Noah Misch |
---|---|
Тема | Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data |
Дата | |
Msg-id | 20211024233502.GA3960658@rfd.leadboat.com обсуждение исходный текст |
Ответ на | Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data (Noah Misch <noah@leadboat.com>) |
Ответы |
Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data
|
Список | pgsql-bugs |
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. https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=kittiwake&dt=2021-10-24%2012%3A01%3A10 got an interesting v9.6 failure, unrelated to the gharial SIGSEGV failures: 2021-10-24 14:25:29.263 CEST [34569:175] pgbench ERROR: could not read two-phase state from xlog at 0/158F4E0 2021-10-24 14:25:29.263 CEST [34569:176] pgbench STATEMENT: COMMIT PREPARED 'c1'; I don't see this thread's commits changing code paths relevant to that failure, so I currently think this one is a new test showing an old bug.
В списке pgsql-bugs по дате отправления: