Re: operators, operator classes, Btree and index usage
| От | Sergey E. Koposov |
|---|---|
| Тема | Re: operators, operator classes, Btree and index usage |
| Дата | |
| Msg-id | Pine.LNX.4.44.0509030238510.20863-100000@lnfm1.sai.msu.ru обсуждение исходный текст |
| Ответ на | Re: operators, operator classes, Btree and index usage (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-general |
On Fri, 2 Sep 2005, Tom Lane wrote:
> "Sergey E. Koposov" <math@sai.msu.ru> writes:
> > I'm interested in simplifying those queries and introducing the operator
> > doing something like this:
>
> > my_operator(bigint x, bigint[] arr)
> > checking the condition:
> > ((x>arr[1]) AND (x<arr[2])) OR ((x>arr[3]) AND (x<arr[4]))
>
> This could be made to work if you define the above as an inline-able SQL
> function. Hacking operator classes won't do it though.
Thank you, Tom! Great! I didn't know that Postgres can inline the SQL
functions (In fact this is because the only place in the documentation
mentioning about inlining SQL functions is the changelog of the
postgres 7.4 :).
With Best Regards,
Sergey
*****************************************************
Sergey E. Koposov
Max-Planck Institut fuer Astronomie
Web: http://lnfm1.sai.msu.ru/~math
E-mail: math@sai.msu.ru
В списке pgsql-general по дате отправления: