Skip site navigation (1) Skip section navigation (2)

Re: wip: functions median and percentile

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: wip: functions median and percentile
Date: 2010-10-13 10:51:51
Message-ID: AANLkTikvkmOsY3oAm9cuzVNJxr0VYhaf2dP4Lg38u545@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-rrreviewers
2010/10/13 Peter Eisentraut <peter_e(at)gmx(dot)net>:
> On mån, 2010-10-11 at 20:46 +0200, Pavel Stehule wrote:
>> The problem is in interface. The original patch did it, but I removed
>> it. We cannot to unsure immutability of some parameters now.
>
> How about you store the "immutable" parameter in the transition state
> and error out if it changes between calls?
>

yes, it's possibility. Now I looking there and I see the as more
important problem the conformance with ANSI SQL. see my last post.
There can be a kind of aggregate functions based on tuplesort.

Regards

Pavel


>

In response to

Responses

pgsql-hackers by date

Next:From: Vitalii TymchyshynDate: 2010-10-13 10:54:19
Subject: Re: Slow count(*) again...
Previous:From: Peter EisentrautDate: 2010-10-13 10:48:17
Subject: Re: wip: functions median and percentile

pgsql-rrreviewers by date

Next:From: Pavel StehuleDate: 2010-10-13 10:56:06
Subject: Re: wip: functions median and percentile
Previous:From: Peter EisentrautDate: 2010-10-13 10:48:17
Subject: Re: wip: functions median and percentile

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group