| Lists: | pgadmin-support |
|---|
| From: | Chris Kelley <iamchriskelley(at)gmail(dot)com> |
|---|---|
| To: | pgadmin-support(at)postgresql(dot)org |
| Subject: | pgadmin error - sql window |
| Date: | 2011-04-13 15:49:18 |
| Message-ID: | BANLkTimYnOhw5JZjxaKhEWhUYmx5D5DeNQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgadmin-support |
Hi,
I have a persistent PgAdmin problem - when I click the SQL window icon from
the PgAdmin main window, the program freezes and must be force-closed. This
happens without fail, and this behavior has persisted despite reinstalls,
registry wipes, and upgrades. I believe this behavior first occurred after
trying to process to parse a wikipedia dump file with a massive (~100 Mb)
query. I can still execute queries using the psql console window, but as I'm
fairly new to full-blown sql (coming from Access) this really slows down the
development process. Currently I am using PgAdminIII 1.12.2. This issue is
limited to my work desktop computer (Dell T1500 quadcore with Windows 7
32-bit), which does have a centrally managed Symantec Endpoint antivirus
installed. My personal netbook is running the same version of PgAdminIII
without issue.
I'd really appreciate any help you can offer, and would be happy to supply
additional info if needed.
Thanks in advance,
Chris
| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Chris Kelley <iamchriskelley(at)gmail(dot)com> |
| Cc: | pgadmin-support(at)postgresql(dot)org |
| Subject: | Re: pgadmin error - sql window |
| Date: | 2011-04-13 16:03:01 |
| Message-ID: | BANLkTinD9h-Zgka1jS-VE62UBznQFCwqfw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgadmin-support |
On Wed, Apr 13, 2011 at 4:49 PM, Chris Kelley <iamchriskelley(at)gmail(dot)com> wrote:
> Hi,
> I have a persistent PgAdmin problem - when I click the SQL window icon from
> the PgAdmin main window, the program freezes and must be force-closed. This
> happens without fail, and this behavior has persisted despite reinstalls,
> registry wipes, and upgrades. I believe this behavior first occurred after
> trying to process to parse a wikipedia dump file with a massive (~100 Mb)
> query. I can still execute queries using the psql console window, but as I'm
> fairly new to full-blown sql (coming from Access) this really slows down the
> development process. Currently I am using PgAdminIII 1.12.2. This issue is
> limited to my work desktop computer (Dell T1500 quadcore with Windows 7
> 32-bit), which does have a centrally managed Symantec Endpoint antivirus
> installed. My personal netbook is running the same version of PgAdminIII
> without issue.
> I'd really appreciate any help you can offer, and would be happy to supply
> additional info if needed.
Sounds like you've hit a known bug which should be fixed in 1.12.3,
due to be released in the next few days. Try deleting the
pgadmin_histoqueries.xml file which stores the query history - it
should be in %APPDATA%\postgresql\
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company