pgsql: Don't call OwnLatch while holding a spinlock.

From: heikki(at)postgresql(dot)org (Heikki Linnakangas)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Don't call OwnLatch while holding a spinlock.
Date: 2010-09-15 06:51:19
Message-ID: 20100915065119.F29727541E2@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Don't call OwnLatch while holding a spinlock. OwnLatch can elog() under
some "can't happen" scenarios, and spinlocks should only be held for
a few instructions anyway. As pointed out by Fujii Masao.

Modified Files:
--------------
pgsql/src/backend/replication:
walsender.c (r1.31 -> r1.32)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/replication/walsender.c?r1=1.31&r2=1.32)

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2010-09-15 10:06:21 pgsql: Simplify Windows implementation of latches.
Previous Message Tom Lane 2010-09-14 23:15:37 pgsql: Fix join-removal logic for pseudoconstant and outerjoin-delayed