Postgres Pro
Downloads
Home   >   mailing lists

Re: expressive test macros (was: Report test_atomic_ops() failuresconsistently, via macros) - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: expressive test macros (was: Report test_atomic_ops() failuresconsistently, via macros)
Date
Msg-id eff1a2a2-f2ad-90c1-95eb-62631babacf8@2ndquadrant.com
Whole thread Raw
In response to Re: expressive test macros (was: Report test_atomic_ops() failures consistently, via macros)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: expressive test macros (was: Report test_atomic_ops() failures consistently, via macros)
Re: expressive test macros (was: Report test_atomic_ops() failuresconsistently, via macros)
List pgsql-hackers
Tree view 
On 2019-10-07 19:57, Tom Lane wrote:
> I'd just put them all in c.h.  I see no reason why a new header
> is helpful.

Assert stuff is already in there, but surely stuff that calls elog()
doesn't belong in there?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: expressive test macros (was: Report test_atomic_ops() failuresconsistently, via macros)
Next
From: Bruce Momjian
Date:
Subject: Re: Transparent Data Encryption (TDE) and encrypted files