[postgis-devel] Issue 110 in postgis: shp2pgsql new option to not batch commit
codesite-noreply at google.com
codesite-noreply at google.com
Wed Feb 4 04:38:07 PST 2009
Comment #3 on issue 110 by mark.cav... at siriusit.co.uk: shp2pgsql new option
to not batch commit
http://code.google.com/p/postgis/issues/detail?id=110
Sure. In terms of performance, putting everything in one transaction is a
lot quicker
than inserting everything separately. So removing the COMMIT every 250
records with
actually speed things up, and saves you having to manually sort out by hand
what got
inserted and what didn't - you can just re-run the batch. It still makes
sense to
wrap everything within a single transaction.
So then the solution you're looking for is actually ii).
ATB,
Mark.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
More information about the postgis-devel
mailing list