From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tobias Wendorff <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 17:48:25 -0400
Message-ID: <2450337.1624484905@sss.pgh.pa.us> (raw)
In-Reply-To: <6574e1c6-fcb6-62fb-9de4-c9005feac87d@tu-dortmund.de>
References: <17071-24dc13fbfa29672d@postgresql.org>
<2350897.1624476008@sss.pgh.pa.us>
<6574e1c6-fcb6-62fb-9de4-c9005feac87d@tu-dortmund.de>
Tobias Wendorff <tobias.wendorff@tu-dortmund.de> writes:
> To keep a long discussion short: you classify it as a wontfix.
> Since I've already supplied a workaround (using a subquery or CTE),
> let's close it.
[ shrug... ] If you intend to take such a totally uncooperative
approach, then I can't help you.
I did *not* say this is a "wontfix". I said it's not easy to fix.
There is a large difference. What I was wondering about was whether
we could find an easier change that would help your actual use-case.
But, since you're not seeing fit to provide further detail, you'll
just have to wait till we can create a fix for the case as presented.
That's likely to be a year or two down the pike.
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: <2450337.1624484905@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