Tue Jan 18 06:38:29 PST 2011
- Previous message: [Slony1-general] sl_status not updated, despite replication working (slony 2.0.6)
- Next message: [Slony1-general] sl_status not updated, despite replication working (slony 2.0.6)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, 18 Jan 2011 09:20:38 -0500, Steve Singer <ssinger at ca.afilias.info> wrote: > On 11-01-18 08:22 AM, Guillaume Lelarge wrote: >> On Tue, 18 Jan 2011 08:04:18 -0500, Steve Singer<ssinger at ca.afilias.info> >> wrote: >>> On 11-01-18 05:08 AM, Guillaume Lelarge wrote: >>[...] >>> Are the confirms for those events confirming they have been processed by >> >>> the master making it back to the slave (look at sl_confirm on the slave) >>> >> >> No, the oldest one is around the same time when I stopped the slave. >> > > Are the SYNC's from node to making it to your origin? (do they show up > in sl_event on the origin). If yes, do the confirms for those events > show up in sl_confirm on the origin. Or in other words are the sync's > from node 2 making it to the origin? > No, they don't make it to the origin. -- Guillaume http://www.postgresql.fr http://dalibo.com
- Previous message: [Slony1-general] sl_status not updated, despite replication working (slony 2.0.6)
- Next message: [Slony1-general] sl_status not updated, despite replication working (slony 2.0.6)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list