Re: Additional Chapter for Tutorial - Mailing list pgsql-hackers

From Erik Rijkers
Subject Re: Additional Chapter for Tutorial
Date
Msg-id 759f7a615736d8066b3441571d371c68@xs4all.nl
Whole thread Raw
In response to Re: Additional Chapter for Tutorial  (Jürgen Purtz <juergen@purtz.de>)
Responses Re: Additional Chapter for Tutorial
List pgsql-hackers
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





pgsql-hackers by date:

Previous
From: Jürgen Purtz
Date:
Subject: Re: Additional Chapter for Tutorial
Next
From: Amit Kapila
Date:
Subject: Re: Enumize logical replication message actions