From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Hemicharger99 <jgerbec(at)roadrunner(dot)com> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: PgAdmin locks up on server |
Date: | 2011-09-08 19:24:42 |
Message-ID: | CA+OCxoweJ_U4GKyU_Ybi3F7ux35a0DMVVbm4NNr8s3cdSPjymA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Thu, Sep 8, 2011 at 7:13 PM, Hemicharger99 <jgerbec(at)roadrunner(dot)com> wrote:
> Running on Windows Server 2008 R2 with a 6-core processor and 16GB of RAM,
> anytime PgAdmin is opened, it eventually locks up when attempting to do just
> about anything.
Anything?
> What kills it instantly is when you open a database and then click the SQL
> window button along the top, it stops responding instantly.
That has been known to happen when the query history file has been
corrupted. You could try deleting it:
%APPDATA%\postgres\pgadmin_histoqueries.xml
> Also, when
> opening a table using View Data >> All Rows or View Data >> Filtered Rows,
> it eventually locks up within 5 minutes.
Only in cases where people have tried to load tables with millions of
rows, or fewer, but very large rows (for example, rows containing
multi-megabyte PostGIS geometries). In a nutshell, the controls in
pretty much any OS have finite limits on the amount of data they can
handle well.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitriy MiksIr | 2011-09-09 19:29:27 | Re: feature request |
Previous Message | Hemicharger99 | 2011-09-08 18:13:13 | PgAdmin locks up on server |