| From: | Erik Rijkers <er(at)xs4all(dot)nl> |
|---|---|
| To: | Jürgen Purtz <juergen(at)purtz(dot)de> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Additional Chapter for Tutorial |
| Date: | 2020-11-02 06:15:28 |
| Message-ID: | c5328f092e9f6b05c0061d6f1842cc4a@xs4all.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On 2020-11-01 16:38, Jürgen Purtz wrote:
> On 30.10.20 17:45, Erik Rijkers wrote:
>>
>> And I wrote down some separate items:
>>
>> 1.
>> 'Two Phase Locking' and 'TPL' should be, I think,
>> 'Two-Phase Commit'. Please someone confirm.
>> (no changes made)
>>
>> Erik Rijkers
>
> All suggestions so far are summarized in the attached patch with the
> following exceptions:
>
> - 'Two Phase Locking' is the intended term.
OK, so what is 'Two Phase Locking'? The term is not explained, and not
used anywhere else in the manual. You propose to introduce it here, in
the tutorial. I don't know what it means, and I am not really a
beginner.
'Two Phase Locking' should be explained somewhere, and how it relates
(or not) to Two-Phase Commit (2PC), don't you agree?
Erik Rijkers
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jürgen Purtz | 2020-11-02 08:26:27 | Re: Additional Chapter for Tutorial |
| Previous Message | Thomas Munro | 2020-11-01 20:59:49 | Re: What does "[backends] should seldom or never need to wait for a write to occur" mean? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-11-02 06:22:03 | Re: bulk typos |
| Previous Message | Amit Kapila | 2020-11-02 06:14:25 | Re: Parallel copy |