From: | Егор Будюкин <zhora(dot)budyukin111(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Confusion on Assert() definition |
Date: | 2025-03-26 11:33:56 |
Message-ID: | CAAv0m28UaDUMLiaHMuSrhQDQAo-6gmBraaHBARi4XOuk4nOPQg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-03-26 14:39:56 | Re: Confusion on Assert() definition |
Previous Message | Alexander Farber | 2025-03-26 10:31:39 | Re: How to pass a list of locations (longitude, latitude) to a PostgreSQL/PostGIS stored function? |