Horton

Re: table AM option passing

Álvaro Herrera <alvherre@kurilemu.de>

View thread View on postgr.es
From: Álvaro Herrera <alvherre@kurilemu.de>
To: Andres Freund <andres@anarazel.de>
Cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>, Zsolt Parragi <zsolt.parragi@percona.com>, Nathan Bossart <nathandbossart@gmail.com>
Date: 2026-03-31T16:10:51Z
Lists: pgsql-hackers

Attachments

Hi,

On 2026-Mar-30, Álvaro Herrera wrote:

> I just pushed the part of 0001 that modifies the API of table_insert and
> its sibling functions.  So here 0001 adds the options bitmask to
> table_update and table_delete, which is important for REPACK; and 0002
> is identical as before and makes the interface (IMO) a bit more
> future-proof.

FWIW I just posted 0001 as part of the repack series here [1]; 0002 is
inessential, so I didn't; but here's both of them.  I have drafted
commit messages also.

[1] https://postgr.es/m/202603311523.iqhng5ljkzpq@alvherre.pgsql

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"Pensar que el espectro que vemos es ilusorio no lo despoja de espanto,
sólo le suma el nuevo terror de la locura" (Perelandra, C.S. Lewis)

Commits

  1. Give an 'options' parameter to tuple_delete/_update

  2. Fix vicinity of tuple_insert to use uint32, not int, for options

  3. Have table_insert and siblings use an unsigned type for options

  4. Remove the following unused type definitions: bool8, bool16, bool32, word8,