On January 11, 2005 09:51 pm, Jan Wieck wrote:
> On 1/11/2005 11:24 PM, Josh Berkus wrote:
> > Jan, Chris,
> >
> > Due to James Black's issue, we figured out that Slony won't purge
> > anything from s_log_1 which is younger than the oldest XID on the server.
> >
> > What's the techincal reason for this?   The result is that orphaned
> > transactions cause a pretty fast buildup of s_log_1 rows.  Not that
> > orphaned transactions aren't a problem on their own, but we're wondering
> > if this isn't fixable in Slony *before* PostgreSQL gets an
> > open_idle_transaction_timeout setting.
>
> With "orphaned transaction" you mean idle transaction in progress, like
> those created by some braindead client interface autocommit misfeatures?
>
> I'm not sure there is a technical reason for this. Sounds more like a
> side effect of a relaxed "what we don't purge now, we purge later"
> strategy.

The attached patch apears to address this, thoughts?




>
>
> Jan


-- 
Darcy Buskermolen
Wavefire Technologies Corp.
ph: 250.717.0200
fx:  250.763.1759
http://www.wavefire.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cleanup_thread.c.patch
Type: text/x-diff
Size: 891 bytes
Desc: not available
Url : http://gborg.postgresql.org/pipermail/slony1-general/attachments/20050112/7c6a86c4/cleanup_thread.c.bin