-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everyone,
First I have had pgpool-II with 2 backends. It worked nicely. Then I configured pgpool-II with 4 backends. Now, it works, but all of a sudden I'm getting this in log: 2011-01-14 11:37:00 LOG: pid 6431: pool_read_message_length2: message length (25) in slot 2 does not match with slot 0(30) 2011-01-14 11:37:00 LOG: pid 6431: pool_read_message_length2: message length (25) in slot 3 does not match with slot 0(30) 2011-01-14 11:37:00 LOG: pid 6431: pool_read_message_length2: message length (25) in slot 2 does not match with slot 0(30) 2011-01-14 11:37:00 LOG: pid 6431: pool_read_message_length2: message length (25) in slot 3 does not match with slot 0(30) It's only slot 2 or 3, does that match backend ids? Would it mean that for some reason for my new backends (2 and 3) the message length is not consistent? This is weird, as I have identical PG versions on all nodes, and I have simply copied entire /etc/postgresql config to all nodes, so the config is identical. - -- Regards, mk - -- Premature optimization is the root of all fun. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNMDdNAAoJEFMgHzhQQ7hO9pYH/RXVaJyXOxsTATPWtWDIo8ap ll+08b7CiWiIpyVhWGMXYHVqP5Sp1aOS45SM7woX3LgaQOhJJ0KoOMSD4d5n1nv+ K9TZKN0HOkTGCWvv5rG86z4Riu/v8iTBN6vEiXHTfVErfpf2zoK3XUqMhgREUN88 FQwaj3ZxfdT1a+WQgqocK7qIkdT1Aede8x+aQiRfJhA++7LGggSP8vwLM/AAyuFs VlPPhWqCXgvZ7S6tCC/5WK86ZsuRCxRS4eNJNbQetOoyMemCygHQhvB5bsYU4l0X zbLI3GV3LXYRMRN1Rjr1F/wRMo6MnYYBCEWWNt4KFikexJOUbpW031++LF73MoI= =xKgd -----END PGP SIGNATURE----- _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
