after a couple of months of quite operation, we are getting the error
pgpool detected difference of the number of inserted, updated, or
deleted
touples..
why isn't pgpool triggers the failover event ?
it looks most rationale to me, so that users can continue to work,
and sysadmin can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I share the same question Asaf did. Also, if possible, it would be
interesting to list all cases in which a node is detached and the
failover event is triggered.
- -Ramon
On 06/06/2010 09:55 AM, Asaf Ohaion wrote:
after a couple of months of
BTW : what is 'replication_stop_on_mismatch' and has it got anything to do
with this issue ?
replication_stop_on_mismatch only affects SELECT. So it does not
anything to do with the issue.
I have to admit that current document regarding
replication_stop_on_mismatch is quite incorrect and hard
Vlad Kosilov vkosi...@... writes:
solution is to give pgpool user a superuser (CREATEUSER,CREATEDB)
permissions.
I had the same problem when using dblink between two databases on the same
host.
Instead of using a superuser, I found that if you explicitly set the host, port
and username, the
