| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | Rakesh Kumar <rakeshkumar464a3(at)gmail(dot)com> |
| Cc: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Serializable read and blocking |
| Date: | 2016-08-11 12:34:37 |
| Message-ID: | CACjxUsPjvDbv0ZQauCKRN8if1z44D-i14YKovWhMPpnw13iZEA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Aug 11, 2016 at 7:11 AM, Rakesh Kumar
<rakeshkumar464a3(at)gmail(dot)com> wrote:
> The question is re the following claim:
>
> - Readers do not block readers.
> - Readers do not block writers.
> - Writers do not block readers.
> - Writers may block writers.
>
>
> Are the above statements true even with SET TRANSACTION SERIALIZEABLE mode.
> I am specifically interested in the 3rd condition (- Writers do not
> block readers.)
Yes.
https://wiki.postgresql.org/wiki/SSI
http://vldb.org/pvldb/vol5/p1850_danrkports_vldb2012.pdf
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2016-08-11 13:08:00 | Re: Jsonb extraction very slow |
| Previous Message | Rakesh Kumar | 2016-08-11 12:11:32 | Serializable read and blocking |