[Bucardo-general] child_q_ relations linger & entries in q table with no updates/inserts/deletes

Bill McGonigle bill at bfccomputing.com
Tue Jan 11 19:39:06 UTC 2011

Thanks, Greg.

I put the automation I came up with on the Cron page:


Additional sets of eyes appreciated, of course.  Seems to work correctly

I couldn't figure out how to cast this SQL:

  select 'freezer.child_q_' || to_char(now()+'1 day

into something that DROP TABLE would accept, so I did the date math in
shell script.  Non-ideal, probably.  I suppose this ought to get its own
stored procedure at some point.


On Mon, January 10, 2011 10:15 pm, Greg Sabino Mullane wrote:
> The q stuff gets moved by the bucardo_purge_q function to
> the master_q table, which then gets sent to child
> tables in the freezer schema. If you don't care about
> this old data (and many do not), you can simply drop
> all the child_q_* tables.
>> ... un-purged q table entries.  They have NULL values for
>> 'started' or 'aborted', so the bucardo_purge_q_table
>> function doesn't see them, but they also don't have
>> any 'updates', 'deletes', or 'inserts', which seems odd.
> Odd, that would seem to indicate a controller starting
> a q entry and a kid never picking it up. It should be
> safe to nuke older ones, and automate that, by using
> the cdate column.
> --
> Greg Sabino Mullane greg at endpoint.com
> End Point Corporation
> PGP Key: 0x14964AC8

Bill McGonigle, Owner
BFC Computing, LLC
Telephone: +1.603.448.4440
Email, IM, VOIP: bill at bfccomputing.com
VCard: http://bfccomputing.com/vcard/bill.vcf
Social networks: bill_mcgonigle/bill.mcgonigle

More information about the Bucardo-general mailing list