[Pgpool-general] Cannot trigger out-of-sync
Jaume Sabater
jsabater at gmail.com
Sun Jan 17 09:46:56 UTC 2010
On Sun, Jan 17, 2010 at 10:00 AM, Tatsuo Ishii <ishii at sraoss.co.jp> wrote:
> pcp commands do not tell DB nodes are in out-of-sync status. So I'm
> not sure what he is expecting here but I think it might be better to
> trigger failover in this case (ERROR: pgpool detected difference of
> the number of inserted, updated or deleted tuples). Opinions?
I think that this is very hard to tell unless you have all possible
cases in your mind. Even in this specific scenario (returning
different number of rows), which are all the possible reasons for it
to happen? In other words, are we totally positive that, when a
different number of (affected) rows is returned, we ALWAYS have an
out-of-sync situation?
--
Jaume Sabater
http://linuxsilo.net/
"Ubi sapientas ibi libertas"
More information about the Pgpool-general
mailing list