From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: printf %s with NULL pointer (was Re: BUG #17098: Assert failed on composing an error message when adding a type to an extension being dropped) |
Date: | 2021-07-14 05:52:39 |
Message-ID: | 802d1a9448570ed6b14d0c8d57746c3a3cd55695.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Tue, 2021-07-13 at 14:26 -0400, Tom Lane wrote:
> Did you see my followup? The vast majority of live systems do not do
> that, so we are accomplishing nothing of value by insisting it's a
> crash-worthy bug.
>
> I flat out don't agree that "crash on debug builds but it's okay on
> production" is a useful way to define this. I spend way too much
> time already on bug reports that only manifest with asserts enabled.
You convinced my that printing "(null)" is better than crashing.
Having a "(null)" show up in a weird place is certainly a minor inconvenience.
But I don't buy your second point: if it is like that, why do we have
Asserts at all?
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2021-07-14 06:05:54 | Re: printf %s with NULL pointer (was Re: BUG #17098: Assert failed on composing an error message when adding a type to an extension being dropped) |
Previous Message | David G. Johnston | 2021-07-14 04:06:28 | Re: Statistics updates is delayed when using `commit and chain` |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2021-07-14 06:05:54 | Re: printf %s with NULL pointer (was Re: BUG #17098: Assert failed on composing an error message when adding a type to an extension being dropped) |
Previous Message | Amit Kapila | 2021-07-14 05:46:46 | Re: row filtering for logical replication |