Thu Jan 20 06:26:32 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 11-01-19 04:58 AM, Guillaume Lelarge wrote: > > 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. > This patch has been merged into REL_2_0_STABLE > Thanks. > > Regards. > >
- 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