| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | chjischj(at)163(dot)com, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Connections hang indefinitely while taking a gin index's LWLock buffer_content lock |
| Date: | 2018-11-11 01:42:16 |
| Message-ID: | CAH2-WznZ7uDWwap_y9iHJO3LfD3efHRkUy+m2myRHSSoF7q3iw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 7, 2018 at 5:46 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> Teodor: Do you think that the issue is fixable? It looks like there
> are serious issues with the design of 218f51584d5 to me. I don't think
> the general "there can't be any inserters at this subtree" thing works
> given that we have to couple buffer locks when moving right for other
> reasons. We call ginStepRight() within ginFinishSplit(), for reasons
> that date back to bug fix commit ac4ab97e from 2013 -- that detail is
> probably important, because it seems to be what breaks the subtree
> design (we don't delete in two phases or anything in GIN).
Ping?
This is a thorny problem, and I'd like to get your input soon. I
suspect that reverting 218f51584d5 may be the ultimate outcome, even
though it's a v10 feature.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-11-11 04:38:13 | Re: Uninterruptible long planning of a query with too many WHERE clauses |
| Previous Message | Andres Freund | 2018-11-11 00:19:29 | Re: Skylake-S warning |