From: Tom Lane <tgl@sss.pgh.pa.us>
To: tobias.wendorff@tu-dortmund.de
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17071: ORDER BY gets ignored when result set has only one row, but another one gets added by rollup()
Date: Wed, 23 Jun 2021 15:20:08 -0400
Message-ID: <2350897.1624476008@sss.pgh.pa.us> (raw)
In-Reply-To: <17071-24dc13fbfa29672d@postgresql.org>
References: <17071-24dc13fbfa29672d@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> SELECT
> '2021-01-01'::date AS month
> GROUP BY
> rollup(month)
> ORDER BY
> month NULLS FIRST;
> [ produces unsorted output ]
Hm, that's certainly a bug, but so far as I can tell it's specific to the
case of a constant value being used as the GROUP BY/ORDER BY target.
Which doesn't seem very likely to be interesting in practice. Do you have
a non-toy example where things go wrong?
The issue here is that ORDER BY a constant is normally deemed to be a
no-op. Our parse representation fails to make it clear that in this
situation, the "constant" column isn't so constant after the GROUP BY has
been applied. There's been some discussion of changing that, but it's a
large task and isn't likely to happen overnight (much less be a plausible
candidate for back-patching). So I'm wondering if this was reduced from
a more realistic example that we might be able to fix in some other way.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, tobias.wendorff@tu-dortmund.de, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17071: ORDER BY gets ignored when result set has only one row, but another one gets added by rollup()
In-Reply-To: <2350897.1624476008@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox