pgsql: Make LOCK_PRINT & PROCLOCK_PRINT expand to ((void) 0) when not i

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Make LOCK_PRINT & PROCLOCK_PRINT expand to ((void) 0) when not i
Date: 2013-11-08 00:08:09
Message-ID: E1VeZcP-0003Uk-3k@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Make LOCK_PRINT & PROCLOCK_PRINT expand to ((void) 0) when not in use.

This avoids warnings from more-anal-than-average compilers, and might
prevent hidden syntax problems in the future.

Andres Freund

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/20803d7881c3865edede170579f55261140b5d0d

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

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2013-11-08 14:00:05 pgsql: Fix subtly-wrong volatility checking in BeginCopyFrom().
Previous Message Tom Lane 2013-11-07 22:44:05 Re: pgsql: Silence benign warnings from clang version 3.0-6ubuntu3.