Mon Jun 23 08:29:47 PDT 2008
- Previous message: [Slony1-general] Re: Mixing 3 slony on 3 databases on the same servers
- Next message: [Slony1-general] Re: Mixing 3 slony on 3 databases on the same servers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andrew Sullivan wrote: > On Sat, Jun 21, 2008 at 11:24:37PM +0200, Cyril SCETBON wrote: > >> Don't you think Slony should check if an earlier transaction exists but >> also if relations locked (in that transaction) are concerned by the >> replication ? >> > > There's no way for Slony to know this. I agree it would be nice, but it's > simply impossible. This is a consequence of the way MVCC in Postgres works. > I was thinking that simply looking at pg_locks (known for hurting performance) would help. > (I'm oversimplifying, note, because there are a few tricks in 8.3 and up > that have solved some of these problems. ok > But that won't help you.) > Damn :-( Thanks > A > _______________________________________________ > Slony1-general mailing list > Slony1-general at lists.slony.info > http://lists.slony.info/mailman/listinfo/slony1-general > -- Cyril SCETBON
- Previous message: [Slony1-general] Re: Mixing 3 slony on 3 databases on the same servers
- Next message: [Slony1-general] Re: Mixing 3 slony on 3 databases on the same servers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list