From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Peter Geoghegan <pg(at)heroku(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> |
Subject: | Re: Abbreviated keys for Numeric |
Date: | 2015-04-04 03:29:11 |
Message-ID: | 11025.1428118151@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> For those following along at home, the failures are on these queries:
> SELECT 1.1 AS two UNION SELECT 2.2;
> SELECT 1.1 AS two UNION SELECT 2;
> SELECT 1 AS two UNION SELECT 2.2;
> SELECT 1.1 AS three UNION SELECT 2 UNION ALL SELECT 2;
> In each case, the expected result is with the values in ascending
> numerical order. In each case, the 1 or 1.1 value which ought to
> appear before 2 or 2.2 instead appears after it. Strictly speaking,
> this is not the wrong answer to the query, and could be perhaps
> explained by the planner choosing a hash aggregate rather than a sort
> + unique plan. But this patch doesn't change the planner at all, so
> the plan should be the same as it has always been.
Yeah. We could add an EXPLAIN to make certain, perhaps, but since
none of the other critters are failing I doubt this explanation.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2015-04-04 05:19:15 | Re: Providing catalog view to pg_hba.conf file - Patch submission |
Previous Message | Robert Haas | 2015-04-04 03:24:39 | Re: Abbreviated keys for Numeric |