| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Jeremy Finzel <finzelj(at)gmail(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Deadlock between concurrent index builds on different tables |
| Date: | 2017-12-26 16:28:34 |
| Message-ID: | 20171226162834.dknphdfc56owiai5@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Jeremy Finzel wrote:
> >
> >
> >> Each index build needs to wait for all other transactions
> >> (Including the ones used by the other index build) to finish.
> >> So I don't think a deadlock here is unexpected.
> Does that mean I should never build more than one concurrent index at
> a time within the entire cluster? If so, that is not clear from the
> documentation.
No, there is no such expectation. Jeff analyzed your scenario,
discovered a bug and sent a patch to fix it -- care to test it and
report back? You can get it from here:
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Finzel | 2017-12-26 17:00:55 | Re: Deadlock between concurrent index builds on different tables |
| Previous Message | Pavel Stehule | 2017-12-26 15:57:43 | Re: Does PostgreSQL check database integrity at startup? |