From: | pasman pasmański <pasman(dot)p(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: New feature: accumulative functions. |
Date: | 2011-09-25 18:21:00 |
Message-ID: | CAOWY8=Z0y_83ziMeNv6XnXhajN5P1nxAO2sQNJRr4m0k3fK_dw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
My english is not perfect, by accumulative i think about monotonically
increasing function.
It works that for clause WHERE f(x)=const:
1. Read root page of index_on_x and get x1 ... Xn
2. Calculate f(x1) ... f(xn) for this page
3. When f(x1)<=const<= f(xn) then x1 <= searched x <= xn and we can
test smaller range (xlower, xgreater).
4. Otherwise no rows satisfy condition.
Step 3 we repeat for current index's page and subpages until xlower =
searched x = xgreater
2011/9/25, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> =?ISO-8859-2?Q?pasman_pasma=F1ski?= <pasman(dot)p(at)gmail(dot)com> writes:
>> I propose to add "accumulative" flag to a function definition. This
>> flag would be set for function f(x) which is accumulative and
>> immutable.
>
> Maybe you'd better define what you mean by "accumulative" ...
>
>> This flag allows to use an index on x for clauses containing f(x):
>> where f(x) = const
>> where f(x) > const
>
> ... because it's sure not clear how you would get that to work.
>
> regards, tom lane
>
--
------------
pasman
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2011-09-25 18:36:25 | Re: Mac OS X shared_buffers not same as postgresql.conf file |
Previous Message | Radosław Smogura | 2011-09-25 18:09:05 | Re: New feature: accumulative functions. |