Search Postgresql Archives

Re: How to get good performance for very large lists/sets?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 






Ohhh..

Um, completely left field, but, if your items are sequential in some
way, maybe there is some gross misuse of ranges you could use?

http://www.postgresql.org/docs/9.2/static/rangetypes.html


-Andy



Another thought, for the case of "find all the items in list A but not list B things can get very slow "

What if you selected everything from list B created yourself a bloom filter, then selected everything out of list A. (Meaning, take it out of PG and do the compare yourself)

Or, maybe write yourself a stored proc that could do bloom filters.

-Andy


--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux