From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Code comment change |
Date: | 2019-07-02 02:03:24 |
Message-ID: | CAH2-WzmA2H+rL-xxF5o6QhMD+9x6cJTnz2Mr3Li_pbPBmqoTBQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Jun 23, 2019 at 3:36 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> Pushed. Thanks!
I wonder what the comment is supposed to mean.
I think that it's addressing the situation prior to commit 70508ba7aed
in 2003, which was the point when the "fast" root concept was
introduced. Prior to that commit, there was only what we would now
call a true root, and _bt_getroot() had to loop to make sure that it
reliably found it without deadlocking, while dealing with concurrent
splits. This was necessary because the old design also involved
maintaining a pointer to each page's parent in each page, which sounds
like a seriously bad approach to me.
I think that the whole sentence about "the standard class of race
conditions" should go. There is no more dance. Nothing in
_bt_getroot() is surprising to me. The other comments explain things
comprehensively.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 2019-07-02 02:04:37 | Re: Bug: ECPG: Cannot use CREATE AS EXECUTE statemnt |
Previous Message | Michael Meskes | 2019-07-02 02:01:24 | Re: [PATCH] memory leak in ecpglib |