Re: Anyone using pgreplicator?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I haven't used it, but if you see everything reaching the server is
it possible that a commit isn't occurring?  UPDATE UPDATE UPDATE
ROLLBACK.  Is autocommit on?  Even if it is on, it is possible that
however PgReplicator functions turns off autocommit and for whatever
reason the commit does not occur.

Sorry this isn't really specific, but I've never used it before, just
generic advice based on what you have said.  GL, is if you find the
answer please post.

- -----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org]On Behalf Of Alan Graham
Sent: Saturday, April 17, 2004 11:53 PM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Anyone using pgreplicator?


Apologies if this is off topic, but I've tried the pgreplicator
forums,
and they appear to be dormant.  I've also tried the general list..

I'm trying to get a multi master replication app running,  I thought
I
was doing well, I've got past all of the problems mentioned on the
pgreplicator forums and (checking the archives) on this list, ie, tcl
installed ok, script changes for postgresql 7.3.4 in, communications
using scp as user replicator working...  Everything in fact works.
Except that it doesn't actually replicate.  When I synchronise. I can
see the traffic going between the sites.  I can see the record being
replicated appearing on the flow table,  I can see it on the history
file on both the source and the destination, so it's reaching the
destination.  There is no sign of any error in any of the
pgreplicator
logs or the system logs.  I've even started postgresql in debug log
mode
and tailed the log while started the replicator on the remote site.
I
see the communications come in, and see the commands being entered.
But
the data isn't being changed on the destination.

Any pgreplicator users out there seen this sort of thing before?

Any suggestions as to debug options, extra logging, etc, I can try?

I thought it might be a permissions issue, but all users have full
access.  The replicator user can make the changes by submitting an
SQL
update.  pgreplicator has a 'rejected sql' log file, but that's
empty.
I'm at my wits end...

Regards
- --
Alan Graham <alan.graham@infonetsystems.com.au>


- ---------------------------(end of
broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBQJbCWCh4imLwvL+vEQJhywCbB2YKC/HFqfyieBt+pNmyJYm+90UAn0YO
g/NQC30RPHTlRW9YLnk1PSX7
=+74p
-----END PGP SIGNATURE-----