Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

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


  • From: "Jim C. Nasby" <jnasby(at)pervasive(dot)com>
  • To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • Cc: Hannu Krosing <hannu(at)skype(dot)net>, pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: \d on database with a lot of tables is slow
  • Date: Tue, 27 Sep 2005 17:46:26 -0500
  • Message-id: <20050927224626(dot)GC30974(at)pervasive(dot)com>

On Mon, Sep 26, 2005 at 03:00:44PM -0400, Tom Lane wrote:
> "Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> >>> I have a client with a database that contains 4000 relations according
> >>> to vacuum verbose, and \d in psql is painfully slow. In particular...
> 
> It's presumably mostly in the pg_table_is_visible() calls.  Not sure if
> we can do much to speed those up, but: how many schemas in your search
> path?  What's the distribution of pg_class entries among the schemas?

db=# show search_path;
 decibel, pg_sysviews, information_schema, rrs, public

db=# select schema_name, count(*) from pg_user_tables group by schema_name;
 public         |   764
 ledger         |     6
 state          |     2
 _track_replica |    10
 repair         |     3
 summarized     |   586
 orders         |   512
 snapshot       |  1012
 acl            |    10

db=# 

Also, do you have any idea on the 'Did not find relation named
"table-thats-there"' error? table-thats-there isn't a temp table, and I don't
believe they're even using temp tables, so I don't think that's the issue.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby(at)pervasive(dot)com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group