Thu Jan 14 05:00:23 PST 2016
- Previous message: [Slony1-general] log insert/update query executed on subscriber
- Next message: [Slony1-general] log insert/update query executed on subscriber
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
----- Original Message ----- > From: Krzysztof Jakowczyk <krzysztof.jakowczyk at unity.pl> > To: Glyn Astill <glynastill at yahoo.co.uk>; Steve Singer <ssinger at ca.afilias.info>; Steve Singer <steve at ssinger.info> > Cc: slony1-general <slony1-general at lists.slony.info> > Sent: Thursday, 14 January 2016, 11:32 > Subject: Re: [Slony1-general] log insert/update query executed on subscriber > > Cause databases have huge load and this setting will kill disk array. ;) We'll regardless, any action performed by your triggers will roll back. Perhaps you could log the information you need with a RAISE LOG/NOTICE in your trigger instead of trying to store it in a transactional table?
- Previous message: [Slony1-general] log insert/update query executed on subscriber
- Next message: [Slony1-general] log insert/update query executed on subscriber
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list