Kyle Bateman <[EMAIL PROTECTED]> writes: > I noticed that it seemed a bit slow to query > information_schema.view_column_usage. As I look at the code in > information_schema.sql, I'm not sure why pg_user is referenced twice > (once without an alias). It looks like we can take out the first > pg_user and remove the DISTINCT keyword and this improves the efficiency > significantly.
The unconstrained join against pg_user is clearly unnecessary, and in fact I took it out a few days ago. I'm not sure whether the SELECT DISTINCT is still needed --- it might be, if there can be multiple pg_depend entries linking the same entities. Peter, any thoughts? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly