[postgis-users] Insert performance issues

[Charlton Purvis]

Cool.  One more thing, you might want to consider Dave's advice in
response to an earlier email of mine dated 10/25/2003 having to do w/
slow addgeomoetrycolumn execution.  Once I removed it, things flew.

[from Dave]
If you want you can remove that portion from AddGeometryColumns() - just
stick null in instead. 

The only part that depends on those column being present is the advanced
STATS package (makefile USE_STATS=1).

Charlton

> -----Original Message-----
> From: Gerry Creager N5JXS [mailto:gerry.creager at tamu.edu]
> Sent: Tuesday, October 28, 2003 9:39 AM
> To: PostGIS Users Discussion
> Subject: Re: [postgis-users] Insert performance issues
> 
> Excellent idea.  Thanks for the paradigm shift.  The use of hourly, or
> daily, tables is one thing I'd briefly considered but not put
sufficient
> time into.  You've just crystallized its use.
> 
> I can do a much shorter, 48 hour history and dump a day's worth of
data
> into the archive db.  That'd give me real fast queries and allow me to
> keep solely unique historic data (archival info _is_ important).
> 
> We're branching into models, especially EPA-based ozone mapping and
> modelling, and looking at sea-breeze influence.  Hence, we're going to
> have to become more efficient.
> 
> Thanks!
> gerry