Re: Transaction serialization

From: Dusan Milanov <dusanmilanov(at)gmail(dot)com>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: Forums postgresql <pgsql-general(at)postgresql(dot)org>
Subject: Re: Transaction serialization
Date: 2016-06-24 19:44:24
Message-ID: 703a0294-cd9b-b96a-276d-a4153383c3b6@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thank you Thomas, this was exactly what I was looking for.

On 24.6.2016 0:57, Thomas Munro wrote:
> On Fri, Jun 24, 2016 at 4:13 AM, Dusan Milanov <dusanmilanov(at)gmail(dot)com> wrote:
>> Hi,
>>
>> A question about transactions: does postgres report serialization errors
>> before a transaction is committed? Obviously, it does on commit, but how
>> about previous statements? Can there be an ERRCODE_T_R_SERIALIZATION_FAILURE
>> error as a response to anything else but the commit?
> Yes. See src/test/isolation/expected/project-manager.out, which shows
> how to reach this error:
>
> postgres=# UPDATE person SET is_project_manager = false WHERE person_id = 1;
> ERROR: could not serialize access due to read/write dependencies
> among transactions
> DETAIL: Reason code: Canceled on identification as a pivot, during write.
> HINT: The transaction might succeed if retried.
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Long, Jie 2016-06-24 20:30:56 Re: [BUGS] BUG #14210: DB crash: system logger process was terminated by exception 0xFFFFFFFFwith exception 0xFFFFFFFF
Previous Message Jeff Beck 2016-06-24 13:59:43 Re: Slave claims requested WAL segment already removed - but it wasn't