Thu Jan 14 03:32:30 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 ]
Cause databases have huge load and this setting will kill disk array. ;) -- Pozdrawiam, Krzysztof Jakowczyk Administrator Systemów Unix Grupa Unity | ul. Przedmiejska 6-10, 54-201 Wrocław ul. Conrada 55B, 31-357 Kraków | ul. Złota 59, 00-120 Warszawa On 14.01.2016 12:16, Glyn Astill wrote: >> From: Krzysztof Jakowczyk <krzysztof.jakowczyk at unity.pl> >> To: 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, 10:04 >> Subject: Re: [Slony1-general] log insert/update query executed on subscriber >> >> >> Our java aplication have bug and from time to time it's trying to insert >> row on subscriber node (which shouldn't happend). My developers wants to >> have query with parametrs which is executed on subscriber node. Table >> audit.slon_audit is created only on subscriber node to catch "bad" >> INSERT/UPDATE queries. I know that this queries shoud executed only on >> origin. I want to find the cause of this behavior of our aplication. >> >> > > In that case why not just set log_min_duration_statement=0 for the user(s) of the java app? > . >
- 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