Beautiful! That fixed my problem. One thing that might be
useful is to update the Index method-extension documentation
on the web site to reflect this problem a bit...if somebody
just wants to get a working index, it can be a bit misleading.
I'll probably go and see if I can construct a few words on
it after my current workload subsides a bit.
-David
Tom Lane writes:
> David McWherter <[EMAIL PROTECTED]> writes:
> > But I still get the issue that my queries don't seem to trigger the
> > GiST indexes to be used. Perhaps the problem is that the system
> > just thinks that the query doesn't need an index to increase
> > performance, i've only got about a dozen elements in the database
> > right now for testing purposes.
>
> Ah, so. You're right, you need more data.
>
> You could try
> SET ENABLE_SEQSCAN TO OFF
> if you just want to force use of the index for testing purposes.
>
> regards, tom lane
----------------------[=========]------------------------
David T. McWherter [EMAIL PROTECTED]
Never pay a compliment as if expecting a receipt.
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
