| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se> |
| Subject: | Re: v12.0: segfault in reindex CONCURRENTLY |
| Date: | 2019-10-13 09:06:43 |
| Message-ID: | 20191013090643.GA1434@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 11, 2019 at 07:44:46PM -0500, Justin Pryzby wrote:
> That's an index on a table partition, but not itself a child of a relkind=I
> index.
Interesting. Testing with a partition tree, and indexes on leaves
which do not have dependencies with a parent I cannot reproduce
anything. Perhaps you have some concurrent operations going on?
> Unfortunately, there was no core file, and I'm still trying to reproduce it.
Forgot to set ulimit -c? Having a backtrace would surely help.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-10-13 09:21:31 | Re: v12.0: reindex CONCURRENTLY: lock ShareUpdateExclusiveLock on object 14185/39327/0 is already held |
| Previous Message | Michael Paquier | 2019-10-13 08:56:02 | Re: dropping column prevented due to inherited index |