Re: tid_blockno() and tid_offset() accessor functions

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: tid_blockno() and tid_offset() accessor functions
Date: 2026-03-13 17:18:09
Message-ID: CAKAnmmLVcPH1p=C=K7uAxg1Q+VeCJzty8xr=f7wmJSK3GBzcfQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 13, 2026 at 1:08 PM Matthias van de Meent <
boekewurm+postgres(at)gmail(dot)com> wrote:

> As for naming; I'd personally prefer to have 'heap' included in the names
> here (e.g. heaptid_blkno(tid) or heap_blkno[_of](tid)), because
> not all AMs may map tid.blkno exactly to a block number in the main fork.

All our docs and code mention blocks and offsets as the components of a
tid, so -1 on making things more obtuse.

--
Cheers,
Greg

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Burd 2026-03-13 17:21:38 Re: Speed up COPY FROM text/CSV parsing using SIMD
Previous Message Matthias van de Meent 2026-03-13 17:08:04 Re: tid_blockno() and tid_offset() accessor functions