|
Home > Archive > Slony1 PostgreSQL Replication > August 2005 > sl_event table not getting cleaned out
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
sl_event table not getting cleaned out
|
|
| David Parker 2005-08-06, 3:23 am |
| In a test-bed running slony 1.0.2, we have a cluster initialized and a
replication set defined, but no subscribers. The local slon is running.
What we are seeing is even when no transactions are happening, the
sl_event table keeps growing with 'SYNC' records. From looking at the
tables and at the cleanupEvent() procedure, it looks like the sl_event
table is never getting deleted because we have no sl_confirm records.
Does this behavior make sense given the configuration, or does it
indicate that I've screwed something up?
Thanks in advance....
- DAP
====================
====================
==============
David Parker Tazz Networks
| |
| cbbrowne-swQf4SbcV9C7WVzo/KQ3Mw@public.gmane.org 2005-08-06, 3:23 am |
| > In a test-bed running slony 1.0.2, we have a cluster initialized and a
> replication set defined, but no subscribers. The local slon is running.
>
> What we are seeing is even when no transactions are happening, the
> sl_event table keeps growing with 'SYNC' records. From looking at the
> tables and at the cleanupEvent() procedure, it looks like the sl_event
> table is never getting deleted because we have no sl_confirm records.
>
> Does this behavior make sense given the configuration, or does it
> indicate that I've screwed something up?
All seems sensible.
If there's no node confirming anything, it makes sense that nothing would
get purged.
It's also possible that 1.0.2 is less aggressive at pruning obsolete
events than more recent editions...
|
|
|
|
|