Re: Memory ordering issue in LWLockRelease, WakeupWaiters, WALInsertSlotRelease

From: "MauMau" <maumau307(at)gmail(dot)com>
To: "Peter Geoghegan" <pg(at)heroku(dot)com>
Cc: "Andres Freund" <andres(at)2ndquadrant(dot)com>, <pgsql-hackers(at)postgresql(dot)org>, "Heikki Linnakangas" <hlinnakangas(at)vmware(dot)com>
Subject: Re: Memory ordering issue in LWLockRelease, WakeupWaiters, WALInsertSlotRelease
Date: 2014-02-18 11:35:02
Message-ID: 8EC58B22649C4BACB322EA9F97C2A989@maumau
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From: "Peter Geoghegan" <pg(at)heroku(dot)com>
> You mentioned a hang during a B-Tree insert operation - do you happen
> to have a backtrace that relates to that?

Sorry, I may have misunderstood. The three stack traces I attached are not
related to btree. I recall that I saw one stack trace containing
bt_insert(), but I'm not sure.

When the hang occurred, INSERT/UPDATE/COMMIT statements stopped for at least
one hour, while SELECT statements ran smoothly.

Regards
MauMau

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message MauMau 2014-02-18 11:49:06 Re: Do you know the reason for increased max latency due to xlog scaling?
Previous Message KONDO Mitsumasa 2014-02-18 11:11:50 Re: Add min and max execute statement time in pg_stat_statement