[pgadmin-support] pgAdmin Query Tool hangs when working with GIS data

[Michael Willekes]

Hello,

I've run into a  the same issue described here:

"Query Tool history makes the Query Tool unusable after BIG query had been
executed
"

Hardware:
- Windows 7 64 bit, 2 GB Ram, 2.8 Ghz

Tools:
- PostgreSQL 9.0.1, compiled by Visual C++ build 1500, 32-bit
- pgAdmin 1.12.1 (Oct 3, 2010, rev:REL-1_12_1)
- PostGIS 1.5.2

I used shp2pgsql from the PostGIS toolkit to generate an SQL Query from a
shapefile(*).  The generated .SQL file is not too big (~13MB) but is a
little odd in that some of the generated geometry columns are excessively
wide (>250K characters on a single line).  The query executes fine (data is
correctly loaded into the database), but subsequent attemps to load the
pgAdmin query tool cause pgAdmin to hang (has to be killed from Task
Manager).

Deleting 'pgadmin_histoqueries.xml' resolves the issue.  I
uninstalled/reinstalled pgAdmin several times, but didn't know about the
existance of this history file (which was stored in my Windows AppData Dir -
and 'survived' an uninstall/reinstall - which of course meant that each
install exhibited the same problem).

It's probably not a common scenario, but it took me a while to find the
issue, so I thought I'd mention it here...

Regards,
Mike

(*) Shapefile:
http://www.naturalearthdata.com/downloads/10m-physical-vectors/10m-coastline/

Re: [pgadmin-support] pgAdmin Query Tool hangs when working with GIS data

[Michael Willekes]

The history file is only 14 MB (4219 lines long) but the PostGIS geometry
columns (auto-generated from a .SHP file) result in individual INSERT
statements that are as much as 50 characters long.



This file is used by the query tool since 1.12. Do you know which size
> it was?
>
>
> --
> Guillaume
>  http://www.postgresql.fr
>  http://dalibo.com
>

Re: [pgadmin-support] pgAdmin Query Tool hangs when working with GIS data

[Michael Willekes]

Thanks for investigating. It was simple to workaround once I realized what
the problem was.  My only concern was that I had inadvertently triggered the
issue, and it was not obvious how to resolve/workaround it.

If someone runs into a similar issue, hopefully a search will turn-up this
thread.

Mike

On Tue, Dec 21, 2010 at 4:58 PM, Guillaume Lelarge
wrote:

> Le 20/12/2010 22:20, Guillaume Lelarge a écrit :
> > Le 20/12/2010 16:39, Michael Willekes a écrit :
> >> The history file is only 14 MB (4219 lines long) but the PostGIS
> geometry
> >> columns (auto-generated from a .SHP file) result in individual INSERT
> >> statements that are as much as 50 characters long.
> >>
> >
> > Is it possible to get the SQL query? by private mail. My idea is to try
> > on my laptop and see if I found any issue. Thanks.
> >
>
> I tried your SQL file, but don't have your issue. It just works for me.
> Damn slow, but works.
>
>
> --
> Guillaume
>  http://www.postgresql.fr
>  http://dalibo.com
>