Skip site navigation (1) Skip section navigation (2)

pgsql: Improve LockAcquire API per my recent proposal.

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Improve LockAcquire API per my recent proposal.
Date: 2005-05-29 22:45:02
Message-ID: 20050529224502.AB6D752824@svr1.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Improve LockAcquire API per my recent proposal.  All error conditions
are now reported via elog, eliminating the need to test the result code
at most call sites.  Make it possible for the caller to distinguish a
freshly acquired lock from one already held in the current transaction.
Use that capability to avoid redundant AcceptInvalidationMessages() calls
in LockRelation().

Modified Files:
--------------
    pgsql/contrib/userlock:
        user_locks.c (r1.17 -> r1.18)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/userlock/user_locks.c.diff?r1=1.17&r2=1.18)
    pgsql/src/backend/storage/lmgr:
        lmgr.c (r1.74 -> r1.75)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/lmgr/lmgr.c.diff?r1=1.74&r2=1.75)
        lock.c (r1.153 -> r1.154)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/lmgr/lock.c.diff?r1=1.153&r2=1.154)
    pgsql/src/include/storage:
        lock.h (r1.86 -> r1.87)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/storage/lock.h.diff?r1=1.86&r2=1.87)

pgsql-committers by date

Next:From: User DpavlinDate: 2005-05-29 23:00:40
Subject: pgswish - pgswish: make it less chatty at INFO logging level
Previous:From: User DpavlinDate: 2005-05-29 22:41:44
Subject: pgswish - pgswish: subversion revision 22 commited to CVS

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group