[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] SSI and predicate locks - a non-trivial use case
From:       Kevin Grittner <kgrittn () ymail ! com>
Date:       2013-08-31 14:19:06
Message-ID: 1377958746.95936.YahooMailNeo () web162906 ! mail ! bf1 ! yahoo ! com
[Download RAW message or body]

Kevin Grittner <kgrittn@ymail.com> wrote:

>  - We don't distinguish between heap relation locks which need to

> prohibit inserts (those caused by a table scan) and heap relation
> locks which don't conflict with inserts (those caused by promotion
> from finer granularity).  We would reduce false positives if we
> did.


Correction: in the above point "prohibit" is misleading.

s/prohibit/cause read-write conflicts with/


A single read-write conflict does not cause blocking or transaction rollback.


--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
[prev in list] [next in list] [prev in thread] [next in thread]