ScanKeys passed to table_beginscan in SeqNext

From: Josh Innis <joshinnis(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: ScanKeys passed to table_beginscan in SeqNext
Date: 2025-07-15 02:49:40
Message-ID: CAAZtsUrVttOAt-=ToK3djQJW6f74vJ83Ew8o38KYbu-YHB=T1A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello PG Devs,

For an extension I am working on. I want to create a new storage
access method. To do this, I would like/need to get scan_keys passed to
table_beginscan in SeqNext. For reference, the comments in SeqRecheck

/*
* Note that unlike IndexScan, SeqScan never use keys in heap_beginscan
* (and this is very bad) - so, here we do not check are keys ok or not.
*/

Is there a plan to have scan keys passed to table_beginscan in SeqNext? and
if not, is there a reason why? I know the heap access method has support
for it.

I am trying to build a key/value access method for a very specific use case
and this seems to be my best option. I don't want to use an index because
part of the goal of adding this access method to the project is to reduce
write amplification of updates, and to make that work with an index would
be much more sophisticated and I feel would be more likely to break.

Thank You,
Josh Innis

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2025-07-15 03:06:29 Re: Some ExecSeqScan optimizations
Previous Message Yugo Nagata 2025-07-15 02:16:40 Re: Suggestion to add --continue-client-on-abort option to pgbench