From: | Alexander Pyhalov <alp(at)rsu(dot)ru> |
---|---|
To: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
Subject: | pgpool-II: cannot use serializable mode in a hot standby |
Date: | 2016-04-12 08:06:42 |
Message-ID: | 570CAC92.2060303@rsu.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi.
We have application which explicitly does
set default_transaction_isolation to 'serializable' .
It is connected to PostgreSQL master/slave cluster through pgpool-II
(pgpool2 3.4.3-1.pgdg70+1). Our logs are filling with
ERROR: 0A000: cannot use serializable mode in a hot standby DETAIL:
"default_transaction_isolation" is set to "serializable". HINT: You can
use "SET default_transaction_isolation = 'repeatable read'" to change
the default. db netstat, client 10.160.1.38, user nf2pg LOCATION:
GetSerializableTransactionSnapshot, predicate.c:1588 STATEMENT: DISCARD ALL
It seems pgpool sends these statements to the slave server. Is it
pgpool/application misconfiguration or pgpool issue?
--
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Ignatov | 2016-04-12 10:50:11 | Freezing localtimestamp and other time function on some value |
Previous Message | Marc Mamin | 2016-04-11 14:17:49 | Re: 9.5 - Is there any way to disable automatic rollback? |