Re: Use T_IntList for uint32

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Subject: Re: Use T_IntList for uint32
Date: 2020-09-01 05:56:35
Message-ID: 20200901055635.GI3511@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 01, 2020 at 01:27:15AM -0400, Tom Lane wrote:
> I've occasionally wondered about having exactly two physical List
> implementations, one for 32-bit payloads and one for 64-bit payloads, and
> then putting a trivial macros-or-static-inlines layer in front of that
> that uses casts to supply variants for pointers, signed ints, unsigned
> ints, etc etc. There hasn't yet been enough reason to pursue doing it
> though.

FWIW, moving pg_list.h & co to have just two list implementations, based
on say bits32 and a new bits64 is something I was thinking about while
reading this thread.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Junfeng Yang 2020-09-01 06:14:45 Is it possible to set end-of-data marker for COPY statement.
Previous Message Michael Paquier 2020-09-01 05:51:58 Re: 回复:how to create index concurrently on partitioned table