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

From Jürgen Purtz
Subject Re: Additional Chapter for Tutorial
Date
Msg-id de79497b-b498-bea7-8651-0f2e6f5037b0@purtz.de
Whole thread Raw
In response to Re: Additional Chapter for Tutorial  (Erik Rijkers <er@xs4all.nl>)
Responses Re: Additional Chapter for Tutorial  (Erik Rijkers <er@xs4all.nl>)
List pgsql-hackers
On 02.11.20 09:44, Erik Rijkers wrote:
> 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
>
>
Because there have been no more comments in the last days I created a 
consolidated patch. It contains Erik's suggestion and some tweaks for 
the text size within graphics.

--

J. Purtz


Attachment

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Move catalog toast table and index declarations
Next
From: Pavel Stehule
Date:
Subject: hard readable explain due JIT