Horton

Re: Additional Chapter for Tutorial

Jürgen Purtz <juergen@purtz.de>

View thread View on postgr.es
From: Jürgen Purtz <juergen@purtz.de>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Erik Rijkers <er@xs4all.nl>, Justin Pryzby <pryzby@telsasoft.com>, "David G. Johnston" <david.g.johnston@gmail.com>
Date: 2020-11-07T12:24:53Z
Lists: pgsql-hackers, pgsql-docs

Attachments

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

Commits

  1. Align some terms in arch-dev.sgml to glossary

  2. doc: Copy-edit the "Overview of PostgreSQL Internals" chapter

  3. Merge postmaster and postgres command into just postgres. postmaster