Re: Explicit NULL dereference (src/backend/commands/tablecmds.c)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Explicit NULL dereference (src/backend/commands/tablecmds.c)
Date: 2021-05-13 14:10:48
Message-ID: 1512089.1620915048@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> writes:
> It is agreed that asserts should be used for error conditions that can
> never occur in the release.
> But with errors that can occur, using assert does not make sense.

On what grounds do you claim that those asserts are wrong?

Coverity's opinion counts for just about nothing these days.
A test case causing a crash would count, of course.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2021-05-13 14:13:00 Re: alter subscription drop publication fixes
Previous Message Ranier Vilela 2021-05-13 14:04:12 Explicit NULL dereference (src/backend/commands/tablecmds.c)