From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | pgsql-general(at)postgresql(dot)org, Kirill Müller <kirill(dot)mueller(at)ivt(dot)baug(dot)ethz(dot)ch> |
Subject: | Re: Enumeration of tables is very slow in largish database |
Date: | 2012-01-11 13:53:06 |
Message-ID: | 1326289986.2300.17.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 2012-01-11 at 14:44 +0100, Andres Freund wrote:
> On Wednesday, January 11, 2012 11:07:23 AM Kirill Müller wrote:
> > Hi all,
> >
> > we have a Postgres/PostGIS database with 100+ schemas and 200+ tables in
> > each schema, generated automatically. When adding a new PostGIS layer in
> > QGis, the application obviously enumerates all tables, and this takes
> > minutes. Even browsing the database in pgAdmin3 is horribly slow -- it
> > takes several seconds to e.g. open a schema (click on a schema's "+" in
> > the tree view).
> Are you actually sure its the database and not just pgadmin thats getting
> really slow?
>
> If you connect via psql and use \dt (see \? for a list of commands) and
> consorts, is it that slow as well?
>
\dt won't be as slow as pgAdmin. \dt only gets the table name, owner,
and stuff like that. Kinda quick. pgAdmin will get also all the other
informations, like columns, triggers, constraints, functions, types,
etc.
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
PostgreSQL Sessions #3: http://www.postgresql-sessions.org
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Duffy | 2012-01-11 14:00:07 | Re: pgAdmin - Query - out of memory for query result |
Previous Message | Guillaume Lelarge | 2012-01-11 13:50:32 | Re: pgAdmin - Query - out of memory for query result |