pgsql: Don't call OwnLatch while holding a spinlock. - Mailing list pgsql-committers

From heikki@postgresql.org (Heikki Linnakangas)
Subject pgsql: Don't call OwnLatch while holding a spinlock.
Date
Msg-id 20100915065119.F29727541E2@cvs.postgresql.org
Whole thread Raw
List 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)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix join-removal logic for pseudoconstant and outerjoin-delayed
Next
From: heikki@postgresql.org (Heikki Linnakangas)
Date:
Subject: pgsql: Simplify Windows implementation of latches.