pgsql: Define Trap and TrapMacro even in non-cassert builds.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Define Trap and TrapMacro even in non-cassert builds.
Date: 2013-06-28 13:34:36
Message-ID: E1UsYou-0008KJ-Dy@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Define Trap and TrapMacro even in non-cassert builds.

In some cases, the use of these macros may be preferable to Assert()
or AssertMacro(), since this way the caller can set the trap message.

Andres Freund and Robert Haas

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/5ee73525d57380a55b5c87f8df1c30bd32fb98b3

Modified Files
--------------
src/include/c.h | 3 +++
1 file changed, 3 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2013-06-28 15:13:35 pgsql: Make the OVER keyword unreserved.
Previous Message Heikki Linnakangas 2013-06-28 09:46:29 pgsql: Track spinlock delay in microsecond granularity.