| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: REINDEX INDEX results in a crash for an index of pg_class since 9.6 |
| Date: | 2019-05-04 15:04:07 |
| Message-ID: | 4622.1556982247@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> sidewinder is still pissed of as of HEAD, pointing visibly to f912d7d
> as the root cause:
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sidewinder&dt=2019-05-03%2021%3A45%3A00
Right, the deadlocks are expected when some previous session is slow about
cleaning out its temp schema. The plan is to leave that in place till
tomorrow to see if any *other* failure modes turn up. But it has to come
out before we wrap the releases.
I don't think we discussed exactly what "come out" means. My thought is
to leave the test scripts in place (so they can be invoked manually with
EXTRA_TESTS) but remove them from the schedule files.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-05-04 15:15:24 | Re: First-draft release notes for back branches are up |
| Previous Message | Tom Lane | 2019-05-04 15:00:11 | Re: Inconsistent error message wording for REINDEX CONCURRENTLY |