"Just Someone" <[EMAIL PROTECTED]> writes:
> Here is the result of explain analyze (though this one took 1500ms and
> not 169000):
Well, it's hard to be sure what the problem is when you're not showing
us a problem case ... but I notice that this indexscan is estimated
awfully high:
> -> Index Scan using
> pg_depend_reference_index on pg_depend dep (cost=0.00..64942.17
> rows=247 width=12) (actual time=396.542..1547.172 rows=22 loops=1)
> Index Cond: (refobjid = 30375069::oid)
The reason is not far to seek: the scan is checking only the second
index key, meaning that it has to scan the entire index. (I am
surprised it didn't use a seqscan instead. Are you using enable_seqscan
= off? Not a great idea.) Since you know you are looking for a table,
you could improve matters by adding a constraint on refclassid:
dep.refclassid = 'pg_class'::regclass
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
