| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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-05 00:09:00 |
| Message-ID: | 20181105000900.hmhvb5daedmxzm63@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2018-11-04 18:49:40 -0500, Tom Lane wrote:
> 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.
It's impracticable to enable dead code warnings in postgres
anyway. There's way way too many of them (all the returns after
elog(ERROR) etc are enough to make it infeasible to change that).
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-11-05 00:15:47 | Re: Wrong aggregate result when sorting by a NULL value |
| Previous Message | Tom Lane | 2018-11-04 23:49:40 | Re: Wrong aggregate result when sorting by a NULL value |