From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Yet another small patch - reorderbuffer.c:1099 |
Date: | 2016-04-05 20:32:00 |
Message-ID: | CA+Tgmoa6OJWnezmyvVkrXO-B-OpYzT=GsoRKtXwjDQyoqDvEiw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Apr 5, 2016 at 10:38 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> IMO the code is wrong. There should be a single block comment saying
> something like "Remove the node from its containing list. In the FOO
> case, the list corresponds to BAR and therefore we delete it because
> BAZ. In the QUUX case the list is PLUGH and we delete in because THUD."
> Then a single line dlist_delete(...) follows.
>
> The current arrangement looks bizantine to me, for no reason. If we
> think that one of the two branches might do something additional to the
> list deletion, surely that will be in a separate stanza with its own
> comment; and if we ever want to remove the list deletion from one of the
> two cases (something that strikes me as unlikely) then we will need to
> fix the comment, too.
+1 to everything here except for the way byzantine is spelled.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | David Steele | 2016-04-05 20:39:48 | Re: [PATCH v12] GSSAPI encryption support |
Previous Message | Peter Geoghegan | 2016-04-05 20:31:50 | Re: WIP: Covering + unique indexes. |