From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)heroku(dot)com> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: hung backends stuck in spinlock heavy endless loop |
Date: | 2015-01-16 14:21:33 |
Message-ID: | CAHyXU0wGVgntDwk2qSn+w6J2iJSJ7WDOjGabYdfZ0G5M9CYanQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jan 16, 2015 at 8:05 AM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> On Thu, Jan 15, 2015 at 5:10 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
>> On Thu, Jan 15, 2015 at 3:00 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
>>> Running this test on another set of hardware to verify -- if this
>>> turns out to be a false alarm which it may very well be, I can only
>>> offer my apologies! I've never had a new drive fail like that, in
>>> that manner. I'll burn the other hardware in overnight and report
>>> back.
>
> huh -- well possibly. not. This is on a virtual machine attached to a
> SAN. It ran clean for several (this is 9.4 vanilla, asserts off,
> checksums on) hours then the starting having issues:
I'm going to bisect this down...FYI. I'll start with the major
releases first. This is not going to be a fast process...I'm out of
pocket for the weekend and have a lot of other stuff going on.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2015-01-16 14:22:27 | Re: hung backends stuck in spinlock heavy endless loop |
Previous Message | Heikki Linnakangas | 2015-01-16 14:21:28 | Re: hung backends stuck in spinlock heavy endless loop |