Re: tid_blockno() and tid_offset() accessor functions - Mailing list pgsql-hackers

From Andres Freund
Subject Re: tid_blockno() and tid_offset() accessor functions
Date
Msg-id zzsoruna42ab5rsdsdoahw6v33pa62afclvg4cqd55azsdizgc@bt27dd5b7hn4
Whole thread
In response to Re: tid_blockno() and tid_offset() accessor functions  (Matthias van de Meent <boekewurm+postgres@gmail.com>)
Responses Re: tid_blockno() and tid_offset() accessor functions
List pgsql-hackers
Hi,

On 2026-03-13 18:08:04 +0100, Matthias van de Meent 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. While PostgreSQL (in core) currently only knows about the heap
> AM, we should probably keep clear of pretending that all tableAMs
> produce TIDs that behave exactly like heap's do.

Meh. As long as tids themselves are split like they are, without any
variability of the amount of space dedicated for either component, I don't see
any advantage in that.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Speed up COPY FROM text/CSV parsing using SIMD
Next
From: Andres Freund
Date:
Subject: Re: Buffer locking is special (hints, checksums, AIO writes)