Large number of rows in pg_type and slow gui (pgadmin) refresh

Robert Klaus wrote on 03.01.2013 16:50:

We have 36,000+ rows returned by " SELECT oid, format_type(oid,
typtypmod) AS typname FROM pg_type".

My manager says this is only a small number compared to what is
expected by next summer.

Why do you need so many types?
That sounds like something in your design is not right.

When I run this select statement on the database server it returns in
under 1 second but it takes a minute to open some tabs using pgAmin
III (1.16.1).

Is there a workaround for this - most of the rows returned are from
one schema. If we could elimiate it from the listed schemas it would
help. Is this possible in pgAdmin III?

That sounds more like a pgAdmin problem and not a PostgreSQL problem.

Thomas

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Yes, I consider it a tool issue and not a database issue. Is there
somewhere else I should be posting this to?

Thanks,
Robert

-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org] On Behalf Of Thomas Kellerer
Sent: Thursday, January 03, 2013 11:31 AM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Large number of rows in pg_type and slow gui
(pgadmin) refresh

Robert Klaus wrote on 03.01.2013 16:50:

We have 36,000+ rows returned by " SELECT oid, format_type(oid,
typtypmod) AS typname FROM pg_type".

My manager says this is only a small number compared to what is
expected by next summer.

Why do you need so many types?
That sounds like something in your design is not right.

When I run this select statement on the database server it returns in
under 1 second but it takes a minute to open some tabs using pgAmin
III (1.16.1).

Is there a workaround for this - most of the rows returned are from
one schema. If we could elimiate it from the listed schemas it would
help. Is this possible in pgAdmin III?

That sounds more like a pgAdmin problem and not a PostgreSQL problem.

Thomas

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make
changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Robert Klaus wrote on 03.01.2013 18:45:

Yes, I consider it a tool issue and not a database issue. Is there
somewhere else I should be posting this to?

There is a pgAdmin mailing list, see here: http://www.postgresql.org/community/lists/

Thomas

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

-----Original Message-----
From: Thomas Kellerer [mailto:spam_eater@gmx.net]
Sent: Thursday, January 03, 2013 12:31 PM
To: pgsql-general@postgresql.org
Subject: Re: Large number of rows in pg_type and slow gui (pgadmin)
refresh

Robert Klaus wrote on 03.01.2013 16:50:

We have 36,000+ rows returned by " SELECT oid, format_type(oid,
typtypmod) AS typname FROM pg_type".

My manager says this is only a small number compared to what is
expected by next summer.

Why do you need so many types?
That sounds like something in your design is not right.

Thomas

Probably those are not the types Robert created explicitly.
There must be lots of tables/views (m.b. lots of partitions) in the database. Every table/view adds couple records to pg_type: one type for table/view record and one type the set (array) of table/view records.

Regards,
Igor Neyman

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Igor Neyman wrote:

Thomas Kellerer wrote:

Why do you need so many types?

Probably those are not the types Robert created explicitly.
There must be lots of tables/views (m.b. lots of partitions) in
the database. Every table/view adds couple records to pg_type:
one type for table/view record and one type the set (array) of
table/view records.

Also, I think use of domains can help make a database more
self-documenting and aid in integrity enforcement, and it's not too
hard to get to a few thousand of those in a complex database.

Anyway, for problems with pgadmin, your best bet would be to post
to the pgadmin-support list.

-Kevin

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general