On Wed, Feb 07, 2007 at 01:32:33PM -0600, Dan Falconer wrote:
>
> Well, we're talking about a table that presently has 114+ million rows.
> I
> believe it takes quite a while to run each vacuum, which may greatly hinder
> our inventory system.
Why? VACUUM doesn't block anything.
> As for autovacuum, I remember that causing some
> issues, especially when we're rolling out a big change: sometimes it's
> forgotten, and we run into the problem of having to kill the site when slony
> starts trying it's exclusive lock while a the vacuum blocks it...
If the problem is only that sometimes you forget to disable things,
that seems to be your change release procedures that need fixing.
You _have_ to vacuum; this is part of the design of the system, and
if you don't do the vacuuming, your system _will_ crawl.
> Actually, I may try doing some time trials on the slave database, just
> to see
> how much time it'll take to vacuum the big table several times in a row. I
> recall the vacuums running exponentially faster when they're run very
> frequently.
Right. The less you have to clean up, the less time it takes. Just
like in the house :)
A
--
Andrew Sullivan | [EMAIL PROTECTED]
Everything that happens in the world happens at some place.
--Jane Jacobs
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
