On Sat, May 04, 2013 at 05:30:46PM +0200, Michelle Sullivan wrote: > So perhaps put it in the bucardo_purge_delta() function? Seems you can > continually vacuum full it with no ill effects or slowdown or locking > issues so doing it every 15 minutes will un-noticable... and every day > wouldn't be an issue either...
I would prefer to keep it separate from that function. For one thing, I'd need to rename it to keep things honest! :) I think we'll simply have the MCP/VAC call bucardo_purge_delta on each database, then do a second round to vacuum pg_listener on any databases that need it. Keeping it separate will also allow us to vacuum more or less often than purge_delta, should we need to in the future. -- Greg Sabino Mullane [email protected] End Point Corporation PGP Key: 0x14964AC8
signature.asc
Description: Digital signature
_______________________________________________ Bucardo-general mailing list [email protected] https://mail.endcrypt.com/mailman/listinfo/bucardo-general
