| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Gianni Ceccarelli <dakkar(at)thenautilus(dot)net>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: SSI and predicate locks - a non-trivial use case |
| Date: | 2013-08-31 14:19:06 |
| Message-ID: | 1377958746.95936.YahooMailNeo@web162906.mail.bf1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Kevin Grittner <kgrittn(at)ymail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2013-08-31 20:42:29 | Re: My Experiment of PG crash when dealing with huge amount of data |
| Previous Message | Kevin Grittner | 2013-08-31 14:10:26 | Re: SSI and predicate locks - a non-trivial use case |