On Tue, 18 Jan 2011 15:38:29 +0100, Guillaume Lelarge
<guillaume at lelarge.info> wrote:
> 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.

I've done more tests on this issue. It appears than I didn't have the last
source of 2.1. I couldn't get it from my customer's office (git pull didn't
work, they have really hard firewall rules).

Now that I have it, after some checks, 2.1 is not affected by my issue.
a6893dbbaa782d7ca4b22ff1cee2b7953a29e89c
(http://git.postgresql.org/gitweb?p=slony1-engine.git;a=commitdiff;h=a6893dbbaa782d7ca4b22ff1cee2b7953a29e89c)
seeming related to my issue, I tried it on 2.0.6 and, tadam, now it works.

I think this bug fix should be applied on REL_2_0_STABLE, so that it
doesn't bite any more 2.0 users.

Thanks.

Regards.


-- 
Guillaume
 http://www.postgresql.fr
 http://dalibo.com