Re: Strange coding in _mdfd_openseg()

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Strange coding in _mdfd_openseg()
Date: 2020-01-26 20:18:18
Message-ID: CA+hUKG+w-De=midogvE2TQ6vOaTEWe+i2UyivYy7UN_xUVk_cw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jan 26, 2020 at 8:23 AM Noah Misch <noah(at)leadboat(dot)com> wrote:
> Agreed. The rest of md.c won't cope with a hole in this array, so allowing
> less-than-or-equal here is futile. The patch in the original post looks fine.

Thanks. Pushed.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2020-01-26 20:22:03 Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?)
Previous Message Tom Lane 2020-01-26 20:13:49 EXPLAIN's handling of output-a-field-or-not decisions