public inbox for [email protected]  

help / color / mirror / Atom feed

From: Erik Rijkers <[email protected]>
To: Jürgen Purtz <[email protected]>
Cc: Justin Pryzby <[email protected]>
Cc: David G. Johnston <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Additional Chapter for Tutorial
Date: Mon, 02 Nov 2020 09:44:54 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<CAKFQuwZ_USvnhZ5wQLFtpr8v+iMiwvZOiVZhviQwPYGDVR7w+g@mail.gmail.com>
	<[email protected]>
	<CAKFQuwbqiZ4Er_e21oXt8J_JDyNucLMcW7murkMr0v=pTy10RA@mail.gmail.com>
	<CAKFQuwbtReW3dBO0HmZCb8rF4z-w+oFt24nPko8pbAk4Y2VWEw@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On 2020-11-02 09:26, Jürgen Purtz wrote:

> OLD:
> 
>     A first approach to implement protections against concurrent
>     access to the same data may be the locking of critical
>     rows. Two such techniques are:
>     <emphasis>Optimistic Concurrency Control</emphasis> (OCC)
>     and <emphasis>Two Phase Locking</emphasis> (2PL).
>     <productname>PostgreSQL</productname> implements a third, more
>     sophisticated technique: <firstterm>Multiversion Concurrency
>     Control</firstterm> (MVCC). The crucial advantage of MVCC ...
> 
> Proposal:
> 
>     A first approach to implement protections against concurrent
>     access to the same data may be the locking of critical
>     rows.
>     <productname>PostgreSQL</productname> implements a more
>     sophisticated technique which avoids any locking:
> <firstterm>Multiversion Concurrency
>     Control</firstterm> (MVCC). The crucial advantage of MVCC ...
> 
> Any thoughts or other suggestions?
> 

Yes, just leave it out. Much better, as far as I'm concerned.

Erik

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Additional Chapter for Tutorial
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox