| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Chris Hanks <christopher(dot)m(dot)hanks(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Connections hang indefinitely while taking a LWLockTranche buffer_content lock. |
| Date: | 2017-10-23 16:55:30 |
| Message-ID: | CAH2-WzmMqud8=UT55r7Bz2TzzzknzqTSBEBPR-yt1UZ9YbUsxw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Oct 23, 2017 at 9:49 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> This is probably enough info for us to identify the exact cause. But
> I don't have time to look right this minute, and am not the hacker most
> familiar with the GIN infrastructure anyway. Anyone want to look for
> the bug?
I don't know very much about GIN, but this does look interesting. I'll
try to get to it later in the week; I have meetings over the next
couple of days.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Hanks | 2017-10-23 17:39:26 | Re: Connections hang indefinitely while taking a LWLockTranche buffer_content lock. |
| Previous Message | Tom Lane | 2017-10-23 16:49:06 | Re: Connections hang indefinitely while taking a LWLockTranche buffer_content lock. |