[postgis-users] OT: pgsql2shp temporary table persists (avpgcon)

[Robert Burgholzer]

Sometimes all you need is someone to listen ...I  managed to solve the problem as follows:

The table was somehow stuck in the system table "pg_class".  Just had to delete it from there, using the following query:

delete from pg_class where relname = '__pgsql2shp_tmp_table';

Now, I don't know if this was an advisable way to handle this or not, but it seemed to work. Pgsql2shp now behaves as it did before my ill-fated cancellation. 

Anyone have an opinion as to whether this is a bug or not?

Robert


-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net [mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Robert Burgholzer
Sent: Friday, January 06, 2006 2:31 PM
To: PostGIS Users Discussion
Subject: RE: [postgis-users] OT: pgsql2shp temporary table persists (avpgcon)

More Info:
The "vacuum full" did not succeed in removing the phantom table, my problems with shp2pgsql from the command line persist as well.

________________________________________
From: postgis-users-bounces at postgis.refractions.net [mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Robert Burgholzer
Sent: Friday, January 06, 2006 2:02 PM
To: PostGIS Users Discussion
Subject: [postgis-users] OT: pgsql2shp temporary table persists (avpgcon)

I ran into a problem running avpgcon --I managed to goof up my db somehow, I think cancelling a pgsql2shp query at a bad time. Although this problem occurred using avpgcon, I believe that the source of the problem may lie in the shp2pgsql routine somehow.



Now, when opening up the avpgcon add theme dialog a phantom table shows up in the list named "__pgsql2shp_tmp_table". Whenever I try to load a shape from this database it fails, and the postgres error console shows it asking for one of the columns in this phantom table, regardless of the table I am actually asking for.  This even happens when using p2sql2shp from the command line regardless of the query I put in.  It shows up in multiple clients (2 different workstations) and seems to affect only this database. I can load things fine from other databases.  I have restarted my postmaster process to no avail, and am currently performing a "vacuum full" in hopes that this will solve it.

I will report back if this solves the problem, but I am thinking this may be an obscure bug in the shp2pgsql routine. Any clues?

thanks

Robert W. Burgholzer
Nonpoint Source Data Analyst
University of Maryland, College Park
Chesapeake Bay Program Office
410 Severn Avenue, Suite 305B
Annapolis, MD, 21403
Phone: (410) 267-5779
rburghol at chesapeakebay.net
http://www.chesapeakebay.net/

_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users