> On 04/12/2016 16:50, Adrian Klaver wrote: >> On 04/12/2016 01:06 AM, Alexander Pyhalov wrote: >>> 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? >>> >> >> I would say the above is coming from Postgres not pgpool: > > I understand. I mean perhaps pgpool shouldn't forward these statements > to slaves.
Yeah, PostgreSQL used to accept the command on standbys (at least in 9.0). The restriction was added later on. It woule be nice if you send a bug report to the pgpool-II bug tracker to not forget it. http://pgpool.net/mediawiki/index.php/Bug_tracking_system Best regards, -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
