From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: hung backends stuck in spinlock heavy endless loop |
Date: | 2015-01-13 23:17:15 |
Message-ID: | CAM3SWZTfE0vHzYkd9qXwcfq5xTRPwdLDM6s8ShLyfcbH=4=0Sw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jan 13, 2015 at 2:29 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> On my workstation today (running vanilla 9.4.0) I was testing some new
> code that does aggressive parallel loading to a couple of tables.
Could you give more details, please? For example, I'd like to see
representative data, or at least the table definitions involved. Do
you have any idea what index is involved with the _bt_compare() calls
above? I'm curious as to what its definition is.
You might also consider using my B-Tree verification tool on a
preserved data directory:
http://www.postgresql.org/message-id/CAM3SWZRK2YxKegj94_2wKs_vbEMJeHc1yE23ECsS01wRAKzkjg@mail.gmail.com
I'm inclined to think that this is a livelock, and so the problem
isn't evident from the structure of the B-Tree, but it can't hurt to
check. The tool is bleeding edge, so don't use it in production.
Thanks
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2015-01-13 23:21:31 | Re: hung backends stuck in spinlock heavy endless loop |
Previous Message | Merlin Moncure | 2015-01-13 22:40:20 | Re: hung backends stuck in spinlock heavy endless loop |