Wed Jan 12 05:52:12 PST 2005
- Previous message: [Slony1-general] Reason for minXID logic?
- Next message: [Slony1-general] Reason for minXID logic?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck at Yahoo.com #
- Previous message: [Slony1-general] Reason for minXID logic?
- Next message: [Slony1-general] Reason for minXID logic?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list