[PERFORM] Query plan changing when queried data does not

2006-12-18 Thread Harry Hehl
I have a database that has 3 tables with a relatively small number of records in each. (see schema/counts below). These 3 tables are loaded when the db is created and there are never any updates or deletes on the 3 tables. This database does have many other tables. ds_tables 132 rows, ds_types

Re: [PERFORM] Sequencial scan instead of using index

2006-04-12 Thread Harry Hehl
Thanks Mark, >Hmm - that first query needs to do a sort, so you might want to experiment with the sort_mem parameter. Could you show us output from explain analyze for >both the above queries? Not too concerned about the sort, more about the query performance with seq scan as the tables size inc

Re: [PERFORM] Sequencial scan instead of using index

2006-04-11 Thread Harry Hehl
Index Cond: (objectid = '65ef0be3-bf02-46b6-bae9-5bd015ffdb79'::capsa_sys.uuid) (14 rows) Time: 5.164 -Original Message- From: Mark Kirkwood [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 07, 2006 12:04 AM To: Harry Hehl Cc: pgsql-performance@postgresql.

[PERFORM] Sequencial scan instead of using index

2006-03-06 Thread Harry Hehl
There seems to be many posts on this issue but I not yet found an answer to the seq scan issue. I am having an issue with a joins. I am using 8.0.3 on FC4 Query: select * from ommemberrelation where srcobj='somevalue' and dstobj in (select objectid from omfilesysentry where name='dir15_file80'