| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vitalii Tymchyshyn | 2010-10-13 10:54:19 | Re: Slow count(*) again... |
| Previous Message | Peter Eisentraut | 2010-10-13 10:48:17 | Re: wip: functions median and percentile |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2010-10-13 10:56:06 | Re: wip: functions median and percentile |
| Previous Message | Peter Eisentraut | 2010-10-13 10:48:17 | Re: wip: functions median and percentile |