From: Tom Lane <tgl@sss.pgh.pa.us>
To: =?UTF-8?B?0JXQs9C+0YAg0JHRg9C00Y7QutC40L0=?= <zhora.budyukin111@gmail.com>
cc: pgsql-general@lists.postgresql.org
Subject: Re: Confusion on Assert() definition
In-reply-to: <CAAv0m28UaDUMLiaHMuSrhQDQAo-6gmBraaHBARi4XOuk4nOPQg@mail.gmail.com>
References: <CAAv0m28UaDUMLiaHMuSrhQDQAo-6gmBraaHBARi4XOuk4nOPQg@mail.gmail.com>
Comments: In-reply-to =?UTF-8?B?0JXQs9C+0YAg0JHRg9C00Y7QutC40L0=?= <zhora.budyukin111@gmail.com>
	message dated "Wed, 26 Mar 2025 14:33:56 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1449616.1742999996.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 26 Mar 2025 10:39:56 -0400
Message-ID: <1449617.1742999996@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/1449617.1742999996%40sss.pgh.pa.us>
Precedence: bulk

=3D?UTF-8?B?0JXQs9C+0YAg0JHRg9C00Y7QutC40L0=3D?=3D <zhora.budyukin111@gmai=
l.com> writes:
> There's something about the definition of Assert() in postgres that I
> don't really understand.

Asserts are meant to be used for "can't happen" cases that would
represent programming bugs.  As such, they are made to do something
in debug builds but be no-ops in production builds.  If you think
there's actually a realistic chance of the case happening in a
production context, you should use a regular if-test-and-ereport
instead of an Assert.

			regards, tom lane