Re: \d on database with a lot of tables is slow

I wrote:
> It's presumably mostly in the pg_table_is_visible() calls.

I did some profiling on a test case with 10000 tables, and noticed that
a big part of the problem is that the catalog caches become entirely
useless: almost every catcache lookup ends up going to the underlying
tables.  This is because MAXCCTUPLES in catcache.c is fixed at 5000,
and that's not an adequate working set for this many tables.  If you
are willing to throw memory at the problem, you could try increasing
MAXCCTUPLES (to say 50K or 100K) and see if that helps.
        regards, tom lane