pgsql: Assert that strong-lock count is >0 everywhere it's decremented.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Assert that strong-lock count is >0 everywhere it's decremented.
Date: 2014-04-07 15:19:06
Message-ID: E1WXBKE-0001BS-KX@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Assert that strong-lock count is >0 everywhere it's decremented.

The one existing assertion of this type has tripped a few times in the
buildfarm lately, but it's not clear whether the problem is really
originating there or whether it's leftovers from a trip through one
of the other two paths that lack a matching assertion. So add one.

Since the same bug(s) most likely exist(s) in the back-branches also,
back-patch to 9.2, where the fast-path lock mechanism was added.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/315772e4ecf2e91f17a8e375afe8dff2c2174406

Modified Files
--------------
src/backend/storage/lmgr/lock.c | 2 ++
1 file changed, 2 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2014-04-07 15:47:02 pgsql: Remove 'make clean' support for ipc_test.
Previous Message Tom Lane 2014-04-07 15:07:13 Re: pgsql: Remove ipc_test.