[postgis-users] Debugging shp2pgsql inserts

[Travis Kirstine]

The problem is that once the first transaction fails I'm not quick enough
to stop subsequent transactions.

Regards


On 19 July 2013 13:48, Wilkins, Brian <bwilkins at harris.com> wrote:

>  It should be the last one at the top where all those ERROR messages get
> displayed. The first to fail stops everything.****
>
> ** **
>
> ** **
>
> *From:* postgis-users-bounces at lists.osgeo.org [mailto:
> postgis-users-bounces at lists.osgeo.org] *On Behalf Of *Travis Kirstine
> *Sent:* Friday, July 19, 2013 1:43 PM
> *To:* PostGIS Users Discussion
> *Subject:* [postgis-users] Debugging shp2pgsql inserts****
>
> ** **
>
> I've been attempting to import a large shapefile into postgis and I keep
> running into "ERROR:  current transaction is aborted, commands ignored
> until end of transaction block" when importing the data.****
>
>  Is there a easy method to determine which INSERT causes the transaction
> to fail? It appears the only why is to catch the stdout as soon as psql
> errors****
>
> shp2pgsql -I -W LATIN1 -s 3857 mybigshp.shp mytbl > mysql.sql****
>
> psql -U user -o log.txt mydb < mysql.sql****
>
> Thanks****
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20130719/453eb914/attachment.html>