[Bucardo-general] Running maintenance routines inside of Bucardo

[Greg Sabino Mullane]

>> - Have Bucardo do the cleanups based on PG version, rather than 
>> cronjobs (e.g. vacuum pg_listener, purge_bucardo_delta)

This item has a bug assigned to it:

http://bucardo.org/bugzilla/show_bug.cgi?id=9

> The extra connections to the databases would be only in comparison to
> a nonexistent ideal, right? Because current cron jobs for maintenance
> do require extra connections anyway.

Yep.

> This is the way I'd lean -- separate and less likely to interfere 
> with other things and complicate the already complex kid code.

Agreed. I'm envisioning a forked MCP (perhaps with a separate prefix to
keep things clean*) that runs at a regular interval. The nice thing
about this level is that will allow us to do things that are independent
of kids and controllers running. The only example I can think of at the
moment is bucardo_compress_delta(), but that could be a big win for
systems where kicks don't happen often.

> One possible counter to the "separate and simpler" note above is that
> having maintenance run inside of a kid would mean the kid wouldn't be
> contending for locks on the same rows, etc. during maintenance. It's
> possible it's better to have the kid wait till maintenance is done.

I'm not too worried about this. The primary maintenance we need to do
for old versions is pg_listener. Second is probably bucardo_delta, but
the rows that are affected are ones that are already guaranteed to be
not used by any processes anymore.

* Clever TLAs welcome. VAC? CLN? MNT? FIX? GSA? WLY?

-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: OpenPGP digital signature
Url : https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20100113/127499c6/attachment.bin