Re: [PERFORM] Select in subselect vs select = any array

2011-03-20 Thread Pavel Stehule
2011/3/21 Adam Tistler : > Pavel, thanks for the help. > > I increased work_mem from 16MB to 64MB, no difference.  The queries are > really just a test case.  My actual queries are actual just large number of > primary keys that I am selecting from the db: > > For example: >   select * from nodes

Re: [PERFORM] Select in subselect vs select = any array

2011-03-20 Thread Adam Tistler
Pavel, thanks for the help. I increased work_mem from 16MB to 64MB, no difference. The queries are really just a test case. My actual queries are actual just large number of primary keys that I am selecting from the db: For example: select * from nodes where node_id in ( 1, 2, 3 . ) I

Re: [PERFORM] Select in subselect vs select = any array

2011-03-20 Thread Pavel Stehule
Hello I think so HashAggregate goes out of memory - you can try to increase a work_mem. There are better queries for counting duplicit then cross join Regards Pavel Stehule 2011/3/21 Adam Tistler : > logicops2=# explain analyze select count(*) from nodes where node_id = any(   > Array(select n

Re: [PERFORM] Select in subselect vs select = any array

2011-03-20 Thread Adam Tistler
logicops2=# explain analyze select count(*) from nodes where node_id = any( Array(select node_id from nodes limit 10) ); QUERY PLAN -

Re: [PERFORM] REINDEX takes half a day (and still not complete!)

2011-03-20 Thread Phoenix Kiula
Thanks Scott. > What is the output of running vacuum verbose as a superuser (you can > run it on the postgres database so it returns fast.) Here's the output for postgres DB: INFO: free space map contains 110614 pages in 33 relations DETAIL: A total of 110464 page slots are in use (in