Re: KEY UPDATE / UPDATE / NO KEY UPDATE distinction vs. README.tuplock

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Florian Pflug <fgp(at)phlo(dot)org>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: KEY UPDATE / UPDATE / NO KEY UPDATE distinction vs. README.tuplock
Date: 2014-10-23 23:55:29
Message-ID: 20141023235529.GJ1791@alvin.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Florian Pflug wrote:

> It seems that README.tuplock never got updated when the KEY SHARE patch's
> lock level were changed from being KEY UPDATE / UPDATE / SHARE / KEY SHARE
> to UPDATE / NO KEY UPDATE / SHARE / KEY SHARE.

You're right. We changed the tuple lock modes at the last minute and
I forgot to update this README. I just pushed it; thanks for the patch
and for improving the wording of that paragraph also.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2014-10-23 23:55:46 Re: [PATCH] add ssl_protocols configuration option
Previous Message Robert Haas 2014-10-23 23:51:26 Re: [PATCH] add ssl_protocols configuration option