Re: Memory ordering issue in LWLockRelease, WakeupWaiters, WALInsertSlotRelease

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: MauMau <maumau307(at)gmail(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 00:17:10
Message-ID: CAM3SWZQzQVfiX3i+uh2igXztgHecWueSVYr=5Vap76ejFmBdtQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 12, 2014 at 3:55 AM, MauMau <maumau307(at)gmail(dot)com> wrote:
> FYI, the following stack traces are the ones obtained during two instances
> of hang.

You mentioned a hang during a B-Tree insert operation - do you happen
to have a backtrace that relates to that?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2014-02-18 01:15:26 Re: Auto-tuning work_mem and maintenance_work_mem
Previous Message Michael Paquier 2014-02-17 23:35:35 Re: CREATE FOREIGN TABLE ( ... LIKE ... )