Horton

Re: Additional Chapter for Tutorial

Erik Rijkers <er@xs4all.nl>

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

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