Re: Wrong aggregate result when sorting by a NULL value - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Wrong aggregate result when sorting by a NULL value
Date
Msg-id 24674.1541375380@sss.pgh.pa.us
Whole thread Raw
In response to Re: Wrong aggregate result when sorting by a NULL value  (Andres Freund <andres@anarazel.de>)
Responses Re: Wrong aggregate result when sorting by a NULL value  (Andres Freund <andres@anarazel.de>)
List pgsql-bugs
Andres Freund <andres@anarazel.de> writes:
> On 2018-11-04 11:19:59 -0500, Tom Lane wrote:
>> Used-for-asserts-only problem.  Will fix.

> Thanks.  I wonder if we shouldn't turn Asserts() into something roughly
> akin to if (0) {expr};. That way we'd not deal with errors about unused
> variables anymore - we're not safe against unreachable code warnings
> anyway.

Meh.  I'm unexcited about getting rid of one type of compiler warning by
introducing another one.

            regards, tom lane


pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: Wrong aggregate result when sorting by a NULL value
Next
From: Andres Freund
Date:
Subject: Re: Wrong aggregate result when sorting by a NULL value