Re: CUBE seems a bit confused about ORDER BY

From: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
To: Teodor Sigaev <teodor(at)sigaev(dot)ru>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CUBE seems a bit confused about ORDER BY
Date: 2018-01-10 15:17:20
Message-ID: CAPpHfdthSHtwkZf1hE909yb1tk-jPMrUbw=5kKaSLYtM8NYvww@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 14, 2017 at 2:39 PM, Teodor Sigaev <teodor(at)sigaev(dot)ru> wrote:

> SQL-query seems too huge for release notes and isn't looking for
> materialized view (fixable) and functional indexes with function which
> contains this operator somewhere inside (not fixable by this query). I
> think, just words is enough.

I found that cube_2.out expected output in regression tests is used on
Windows 2003 in my virtual machine. I've checked that for both cube
patches, regression tests pass correctly on that virtual machine.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-01-10 15:37:07 Re: [HACKERS] Proposal: Local indexes for partitioned table
Previous Message Konstantin Knizhnik 2018-01-10 15:07:38 Re: [HACKERS] Secondary index access optimizations