Re: Wrong aggregate result when sorting by a NULL value

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, obouda(at)email(dot)cz, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Wrong aggregate result when sorting by a NULL value
Date: 2018-11-04 23:49:40
Message-ID: 24674.1541375380@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2018-11-05 00:09:00 Re: Wrong aggregate result when sorting by a NULL value
Previous Message Andres Freund 2018-11-04 23:44:10 Re: Wrong aggregate result when sorting by a NULL value