pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: chenhj <chjischj@163.com>
To: Peter Geoghegan <pg@bowt.ie>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re:Re: Connections hang indefinitely while taking a gin index's LWLock buffer_content lock
Date: Mon, 12 Nov 2018 01:10:32 +0800 (CST)
Message-ID: <37ed3491.c3.16703c0e722.Coremail.chjischj@163.com> (raw)
In-Reply-To: <CAH2-Wzn2vaVWG8JNPYnzNnRjh3T2SuMdR83uT2v7OKhAvhWX+g@mail.gmail.com>
References: <31a702a.14dd.166c1366ac1.Coremail.chjischj@163.com>
	<CAH2-Wzn2vaVWG8JNPYnzNnRjh3T2SuMdR83uT2v7OKhAvhWX+g@mail.gmail.com>



>
>BTW, I strongly doubt that disabling hugepages has fixed anything,
>though it may have accidentally masked the problem. This is an issue
>around the basic correctness of the locking protocols used by GIN.
>

We had disable hugepages for some days, but the bug still occurs.


The attachment is the gcore files that was collected when the issue occurred on the primary, and I hope to help analyze the problem.






Regard,
Chen Huajun

Attachments:

  primary_hang_20181026_52.tar.gz (application/x-gzip, 4.8M) download

view thread (67+ messages)  latest in thread

Message-ID: <37ed3491.c3.16703c0e722.Coremail.chjischj@163.com>
Permalink:  ../37ed3491.c3.16703c0e722.Coremail.chjischj@163.com/
Also on:    postgresql.org/message-id/37ed3491.c3.16703c0e722.Coremail.chjischj@163.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: chjischj@163.com, pg@bowt.ie, pgsql-hackers@lists.postgresql.org
  Subject: Re:Re: Connections hang indefinitely while taking a gin index's LWLock buffer_content lock
  In-Reply-To: <37ed3491.c3.16703c0e722.Coremail.chjischj@163.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox