Hi,
Is there any other place we could try to get this question answered?
This is a really important matter for us, please answer.
Ger.
daniel.cre...@l-3com.com wrote:
Question: Could it be that a failover was triggered for a different
number of rows in a previous version? We were under the
Question: Could it be that a failover was triggered for a different
number of rows in a previous version? We were under the impression
that
this was the behaviour.
Thanks a lot,
Ger.
Hi again,
Could someone kindly give me an answer to the questions above? I do
Does PGPool handle all queries in the same order on every node? If so, I
do not think there can be any legal reason for the number of rows to be
different.
Any thoughts about the failover policy? IMHO, it is a significant issue
if backends with different data are allowed to coexist.
@pgfoundry.org
Subject: [Pgpool-general] Cannot trigger out-of-sync
Hi,
I want to trigger an out-of-sync for a pgpool cluster in our
test-environment, but am unable to do it.
As I understood it, if pgpools get a different number of rows back
from
a query, it should trigger an out of sync
On Sun, Jan 17, 2010 at 10:00 AM, Tatsuo Ishii is...@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
: [Pgpool-general] Cannot trigger out-of-sync
Hi,
I want to trigger an out-of-sync for a pgpool cluster in our
test-environment, but am unable to do it.
As I understood it, if pgpools get a different number of rows back
from
a query, it should trigger an out of sync for one of the databases
