From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Fran G <poupou1980(at)gmail(dot)com> |
Cc: | "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Serializable Isolation Level |
Date: | 2017-05-25 01:56:34 |
Message-ID: | CAKFQuwayua28Q2VFbMMw+QM4zYF2DVkaYVxhR_aMMb_f0d_WDw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Wednesday, May 24, 2017, Fran G <poupou1980(at)gmail(dot)com> wrote:
> David, Thanks for the quick response.
> I do have a primary key defined. But my table itself has just 256 rows. I
> suspect for this small a size, postgres might have grouped several ids
> together which could cause this issue. The underlying concept which I
> gather from your post, is that postgres is keeping track of not only the
> data being accessed for modification, but also the path to access it. While
> my observations do support this, I never came across documentation which
> state this explicitly. Have I understood the problem right?
>
https://www.postgresql.org/docs/9.6/static/transaction-iso.html#XACT-SERIALIZABLE
The last bullet seems apropos.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Danielsson | 2017-05-25 17:23:13 | Custom order |
Previous Message | Fran G | 2017-05-25 01:09:28 | Re: Serializable Isolation Level |