Re: [PERFORM] Sequential scan being used despite indexes

2006-01-31 Thread James Russell
[Sorry, my last reply didn't go to the list] Reading about this issue further in the FAQ, it seems that I should ensure that Postgres has adequate and accurate information about the tables in question by regularly running VACUUM ANALYZE, something I don't do currently. I disabled SeqScan as per

[PERFORM] Sequential scan being used despite indexes

2006-01-31 Thread James Russell
Hi there, I'm running a simple query with 2 inner joins (say A, B and C). Each of the join columns has indexes. If I run queries that join just A and B, or just B and C, postgres uses indexes. But if I run "A join B join C" then the "B join C" part starts using a sequential scan and I can't figure

[PERFORM] Retaining execution plans between connections?

2006-01-20 Thread James Russell
Hi there, I am running a website where each page connects to the DB to retrieve and write information. Each page load uses a separate connection (rather than just sharing one as is the common case) because I use a lot of transactions. I am looking to speed up performance, and since each page exec