| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Robert Klaus <rklaus(at)nexgenwireless(dot)com> |
| Cc: | pgadmin-support(at)postgresql(dot)org |
| Subject: | Re: Large number of rows in pg_type and slow gui (pgadmin) refresh |
| Date: | 2013-01-06 17:49:21 |
| Message-ID: | 1357494561.336.8.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On Sun, 2013-01-06 at 11:27 -0600, Robert Klaus wrote:
> Get all schemas, except some of them. One schema will have 90+% of the database objects.
>
You can already do that without having a custom pgAdmin.
> If we could eliminate that schema fewer rows would be returned by the underlying queries, allowing us to continue using pgAdmin.
>
> I've only been working with this company (and postgresql) for 90 days so if there is a better way (other than rewriting the application that creates all those tables and views) please let me know how to proceed.
>
Get into the properties of your database, select the Definition tab, add
your schema name in the "Schema restriction" textbox (make sure you put
single quotes around it), and click OK. Disconnect, reconnect... should
work.
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2013-01-06 18:55:24 | Re: pgadmin3 - Crash on renaming |
| Previous Message | Guillaume Lelarge | 2013-01-06 17:33:00 | Re: Can't access URLs in documentation |