Forgot to add I'm running the following POSTGIS="1.3.3SVN" GEOS="3.0.0-CAPI-1.4.1" PROJ="Rel. 4.5.0, 22 Oct 2006" USE_STATS
(the SVN is probably from about a week ago. I haven't reloaded the latest SVN yet) Thanks, Regina -----Original Message----- From: Paragon [mailto:[EMAIL PROTECTED] Sent: Thursday, April 10, 2008 10:00 PM To: '[email protected]' Subject: Slow vacuuming Has anyone noticed an issue in 8.3 with vacuuming or clustering on geometries. I remember there was an issue with running PostgreSQL on Xeon processors - is that still a problem? I've been loading tiger data and for large states like Florida and California, my process seems to be hanging a lot vacuuming and some on clustering of the geometries. I'm beginning to point the finger at my clustered geometries (but I'm performing experiments now to see if I can rule it out). At first I blamed the box, but now they beefed it up to a 2 processor Quad Core and added 4 gig and I upped some settings. I'm not sure. This seemed to be faster on the old server I was on (which was considerably slower and running 8.2) , but then too many variables have changed. E.g. the old was regular non-xeon processors. Anyrate too many variables have changed between the 2 -e.g. before I was running with Tiger 2006SE loading via Ogr and now I'm loading shape via shp2pgsql Tiger2007FE and they've change the whole structure anyway. All I know is that for some reason my Vacuum analyze on my florida edges table never seems to complete. This may not be an issue but could be just something stupid with my configuration - like my box happens to be 32-bit instead of 64-bit which frustrates me. RedHat Linux EL 5 is a new experience to me anyway. Thanks, Regina _______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
