Thu Jun 23 00:51:17 PDT 2011
- Previous message: [Slony1-general] postgres slony-i master node tables can't be written after running for few days
- Next message: [Slony1-general] postgres slony-i master node tables can't be written after running for few days
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 23/06/2011 08:41, rodney a écrit : > Hi, > > I connect to the both master and slave nodes directly. > > I already re-configure slony, and it is working properly now > > for master node , the triggers are: > <---------------------------------------------------------------------------------- (...) > ----------------------------------------------------------------------------------> OK. > > > for slave node, the triggers are: > <---------------------------------------------------------------------------------- (...) > ----------------------------------------------------------------------------------> OK. > > I don't know how to reproduce the problem, just waiting it to happen > again. To give more information about how I setup slony, Following is my > scripts I used to configure slony > These scripts seem OK. I would guess something has reenabled the disabled triggers. But what? - -- Stéphane Schildknecht Loxodata Contact régional PostgreSQL -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4C8HUACgkQA+REPKWGI0F5PQCeIjtELBNpIAM14g8MWrehHqcN nq8AnRIxmDG4Hj/o5MZmFe+VXsH1+zHO =zi3p -----END PGP SIGNATURE-----
- Previous message: [Slony1-general] postgres slony-i master node tables can't be written after running for few days
- Next message: [Slony1-general] postgres slony-i master node tables can't be written after running for few days
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list