| From: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> |
|---|---|
| To: | Nick Raj <nickrajjain(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andreas Kretschmer <akretschmer(at)spamfence(dot)net>, pgsql-general(at)postgresql(dot)org, Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
| Subject: | Re: disable seqscan |
| Date: | 2011-05-24 09:01:58 |
| Message-ID: | 9062FD1C-C911-40D3-A1A3-843B5CCA5C9E@solfertje.student.utwente.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 24 May 2011, at 8:22, Nick Raj wrote:
> One think i am not able to understand is, if i use ndpoint_overlap method it is going for seq. scan every time but if i use && operator it is using index scan. Why it is so?
> Why these is happening?
Tom already explained that, but in short: Because a function is not an operator.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4ddb741511921606159980!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Trenta sis | 2011-05-24 09:15:22 | Re: Postgres questions |
| Previous Message | Alban Hertroys | 2011-05-24 08:50:44 | Re: strange behaviour in 9.0.2 / ERROR: 22003: value out of range: overflow |