Re: Size and size_t in dsa API - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Size and size_t in dsa API
Date
Msg-id CAEepm=0k_3EeeJozFFdkd72jXX75=YnFPSxpawwSosjLhPKxJQ@mail.gmail.com
Whole thread Raw
In response to Size and size_t in dsa API  ("Ideriha, Takeshi" <ideriha.takeshi@jp.fujitsu.com>)
Responses RE: Size and size_t in dsa API  ("Ideriha, Takeshi" <ideriha.takeshi@jp.fujitsu.com>)
List pgsql-hackers
On Thu, Sep 20, 2018 at 6:28 PM Ideriha, Takeshi
<ideriha.takeshi@jp.fujitsu.com> wrote:
> As a non-expert developer's opinion, I think mixing of Size and size_t makes difficult to understand source code.

Agreed.  Let's change them all to size_t and back-patch that to keep
future back-patching easy.  Patch attached.

-- 
Thomas Munro
http://www.enterprisedb.com

Attachment

pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: Is it possible for postgres_fdw to push down queries on co-locatedtables?
Next
From: Marco Slot
Date:
Subject: Segfault when creating partition with a primary key and sql_droptrigger exists