Re: Standardize type of variable when extending Buffers

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: gurjeet(at)singh(dot)im
Cc: ranier(dot)vf(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Standardize type of variable when extending Buffers
Date: 2023-07-10 06:27:37
Message-ID: 20230710.152737.470170365139526120.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Fri, 7 Jul 2023 11:29:16 -0700, Gurjeet Singh <gurjeet(at)singh(dot)im> wrote in
> On Fri, Jul 7, 2023 at 6:12 AM Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> wrote:
> >
> > Hi,
> >
> > This has already been discussed in [1].
> > But I thought it best to start a new thread.
> >
> > The commit 31966b1 introduced the infrastructure to extend
> > buffers.
> > But the patch mixed types with int and uint32.
> > The correct type of the variable counter is uint32.
> >
> > Fix by standardizing the int type to uint32.
> >
> > patch attached.
>
> LGTM.

LGTM, too.

I don't think it will actually come to play, since I believe we won't
be expanding a relation by 16TB all at once. Nevertheless, I believe
keeping things tidy is a good habit to stick to.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2023-07-10 06:39:27 Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
Previous Message Masahiko Sawada 2023-07-10 06:23:27 Re: Add hint message for check_log_destination()