From: | Sebastian P(dot) Luque <spluque(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: custom average window function failure |
Date: | 2016-10-09 19:34:48 |
Message-ID: | 87eg3puxif.fsf@otaria.sebmel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, 09 Oct 2016 12:40:09 -0400,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
>> On 10/09/2016 08:46 AM, Tom Lane wrote:
>>> Clearly a bug --- the wrong type OIDs are being passed down to
>>> array_append. It should be told that it's getting called as
>> For my edification, why does this work?:
> On closer inspection, the error is only in the
> aggregate-used-as-window-function case, not plain aggregation.
Yes, I see the same phenomenon. Could someone suggest a workaround
until this is fixed? I'm under the gun to submit output tables and the
only thing I can think of is a crawling slow loop to step through each
window twice: once using the plain aggregation and another without just
get all rows. I highly doubt it will be worthwhile, given it's going to
be about 1000 iterations, and each one would take about 30-45 min...
--
Seb
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-10-09 20:00:21 | Re: custom average window function failure |
Previous Message | Tom Lane | 2016-10-09 16:40:09 | Re: custom average window function failure |