[postgis-users] RE: Slow vacuuming

[Paragon]

Update.  My vacuum is running fine now.  I posted the same issue to the
PostgreSQL newsgroup.  Turns out I was just being really stupid and had set
my vacuum costs in my postgresql.conf to never use any IO.  Setting these
back to default makes vacuum run within seconds now.
 
Thanks,
Regina

  _____  

From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Paragon
Sent: Thursday, April 10, 2008 11:39 PM
To: 'PostGIS Users Discussion'
Subject: RE: [postgis-users] RE: Slow vacuuming


Upping my work_mem didn't seem to make a difference although it improved my
query speed on some other things. 
 
vacuum analyze fl.fl_edges;  
 
I ruled out clustering as the issue since I have dropped all indexes on that
table before I reran vacuum analyze.
 
I thought maybe there was some corruption somewhere so I had copied that
data to a temp table with a bulk insert
 
SELECT * INTO fl.fl_edges_temp FROM fl.fl_edges
 
(which ran in about 80 secs) - total records 2,231,947
 
Then I did a 
truncate table fl.fl_eges
 
and repopulated which took about 90 seconds.  And now vacuuming patiently
for the past 15 minutes or so.
 
Any other thoughts,
Thanks
Regina
 
 
 
 
 >  I'm going to up my work_mem once my current state load is done or at
least at a safe breaking point.
> 
>  Thanks,
> Regina
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20080413/a5e037bf/attachment.html>