Confusion on Assert() definition - Mailing list pgsql-general

From Егор Будюкин
Subject Confusion on Assert() definition
Date
Msg-id CAAv0m28UaDUMLiaHMuSrhQDQAo-6gmBraaHBARi4XOuk4nOPQg@mail.gmail.com
Whole thread Raw
Responses Re: Confusion on Assert() definition
List pgsql-general
Hi all!

There's something about the definition of Assert() in postgres that I
don't really understand. Refering to src/include/c.h, if
USE_ASSERT_CHECKING is not defined, Assert() is defined to be always
true regardless of FRONTEND? Additionally, I lack understanding of why
Assert() is meant to only be used for debugging when it has a lot of
potential at error intercepting. PipelineDB, for example, has a risk
of few null dereferences because of disabled Assert().

It bugs me that I can't get over something seemingly obvious, so I'd
be very grateful for clarification!

Best regards,
Egor Budyukin,
confused static analysis specialist.



pgsql-general by date:

Previous
From: Alexander Farber
Date:
Subject: Re: How to pass a list of locations (longitude, latitude) to a PostgreSQL/PostGIS stored function?
Next
From: Tom Lane
Date:
Subject: Re: Confusion on Assert() definition