[postgis-users] Insert performance issues

Charlton Purvis cpurvis at asg.sc.edu
Mon Oct 27 10:58:32 PST 2003


Sorry to have joined the thread so late.  Good chance that I've missed
the crux of the messages.

But I read through the thread, and your initial questioned seemed to be
centered around insert performance.  And I am intimate w/ that beast.

I'd HIGHLY recommend that you use the pgsql COPY command instead of lots
of inserts.  It reduced my insert time exponentially from something like
12 hours to 5 minutes for about 5 million records.  Kind of crazy, eh?

That is, if you can lock the table you're updating w/o effecting your
production system.  Also, removing all indices on the table before
copying helps, too.  Then rebuild and analyze them once your table is
populated.

Charlton



More information about the postgis-users mailing list