[postgis-devel] shp2pgsql transactions

[Kevin Neufeld]

I think a "commit batch size" parameter would be my preference.  That would permit someone to choose a custom commit 
size of 1000 records, leave the default of 'all' (a single BEGIN/END), or disable it completely.

Having multiple commits is useful to someone loading large shapefiles (ie. +2GB) since it keeps the transaction log size 
down.

I do, however, generally subscribe to the all-or-nothing mentality.  But since I know people also sometimes prefer to 
just load their data and deal with missing records later, I propose a second parameter of "continue on error" that 
defaults to "false".

-- Kevin

strk wrote:
> On Wed, Oct 21, 2009 at 04:03:28PM +0100, Mark Cave-Ayland wrote:
>> Michael Orlitzky wrote:
>>
>>> I see that the shp2pgsql utility is adding END/BEGIN transaction 
>>> delimiters once for every 250 INSERT statements.
>> Yeah; I'm not a fan of this since generally you either want everything 
>> in a transaction or you don't. I'd like to propose just adding a single 
>> transaction block around the whole file, which people can then strip off 
>> really easily if they don't want it.
> 
> +1
> 
> --strk;
> 
>  Free GIS & Flash consultant/developer      ()  ASCII Ribbon Campaign
>  http://foo.keybit.net/~strk/services.html  /\  Keep it simple! 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel