On Wed, May 25, 2016 at 09:57:05PM +0000, William Widener wrote:
> However, a legacy Java app performs periodic table UPDATEs 
> which are not replicated.
> 
> Performing the equivalent postgres UPDATE command manually on the 
> master replicates with no problem.

The only real way this can happen is if the Java app is disabling triggers 
(e.g. with session_repliation_role). Not something it should be doing.

Being as you said "legacy", I'm thinking it is probably something else, 
such as looking at the wrong database, or an unexpected rollback. Cranking 
up the Postgres logs via log_statement='all' should show you exactly what 
is going on with the app.


-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
Url : http://lists.slony.info/pipermail/slony1-general/attachments/20160525/76de7be9/attachment.pgp