Re: slow information schema with thausand users, seq.scan pg_authid
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-hackers@postgresql.org, andrew@supernews.com
Date: 2006-02-06T18:29:10Z
Lists: pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes: > Andrew - Supernews wrote: >> Perhaps you missed the fact that the query was not one that he wrote, >> but is the query that psql uses for \ds ? > I did miss that. Perhaps with dependency tracking and all, we don't > need the left joins anymore? I don't see anything wrong with leaving the left joins as-is, on the grounds that 1. the planner can simplify the left joins to inner joins, eg the join to pg_namespace should be simplified on the strength of the test on nspname. (This seems to be broken in HEAD, but it does work in 8.1 --- I think I broke it with the changes to treat IN as a ScalarArrayOp. Will fix.) 2. HEAD also knows how to change the order of the left joins at need. The real question to me is why the planner doesn't want to use the index on pg_authid.oid. That's pretty curious ... regards, tom lane