> It should not forward transactions which are requested to be
> SERIALIZABLE to standbys. If you just suppress the SET statement
> (or substitute REPEATABLE READ), queries in that transaction can
> return incorrect results.
Yes. Once "SET default_transaction_isolation to serializable" (or its
va
On Wed, Apr 13, 2016 at 5:54 PM, Kevin Grittner wrote:
> See this example, and imagine that
> the transaction generating the list of receipts for the closed
> batch is run on the standby before the transaction adding the last
> receipt commits. Or test it.
https://wiki.postgresql.org/wiki/SSI#D
On Wed, Apr 13, 2016 at 1:30 AM, Alexander Pyhalov wrote:
> Tatsuo Ishii писал 13.04.2016 02:36:
>>>
>>> On 04/12/2016 16:50, Adrian Klaver wrote:
On 04/12/2016 01:06 AM, Alexander Pyhalov wrote:
>>>
>>> I understand. I mean perhaps pgpool shouldn't forward these statements
>>> to slaves
Tatsuo Ishii писал 13.04.2016 02:36:
On 04/12/2016 16:50, Adrian Klaver wrote:
On 04/12/2016 01:06 AM, Alexander Pyhalov wrote:
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 rest
> 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
On 04/12/2016 07:02 AM, Alexander Pyhalov wrote:
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 thr
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 log
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
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:
"
