[postgis-users] shp2pgsql creates spatial index *before* itinsertsdata? Is that right?

Ethan Alpert ealpert at digitalglobe.com
Thu Mar 9 08:57:34 PST 2006

In the case of loading multiple sets of data then you wouldn't select
the -I option to create an index either.

-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of
Stephen Woodbridge
Sent: Wednesday, March 08, 2006 7:24 PM
To: PostGIS Users Discussion
Subject: Re: [postgis-users] shp2pgsql creates spatial index *before*
itinsertsdata? Is that right?

Markus Schaber wrote:
> Hi, Ethan,
> Ethan Alpert wrote:
>>Shouldn't a VACUUM ANALYZE <table_name> also occur ?
> ANALYZE does make sense in some cases, when the statistical
> of values changes. VACUUM does not make sense on a freshly created and
> populated table, only UPDATES and DELETEs cause VACUUMs to be needed.
> CLUSTER and some ALTER TABLE commands also rewrite the table, making
> VACUUM obsolete.
> Btw, most recent PostgreSQL installations have Autovacuum running, so
> the table will be vacuumed and analzyed as needed.

I think another important point to remember here is the in many cases, 
for me at least, I end up loading multiple shapefiles into the same 
table and I don't want to slow that down with useless analyzing when  am

going to load more data.

postgis-users mailing list
postgis-users at postgis.refractions.net

More information about the postgis-users mailing list