public inbox for [email protected]  

help / color / mirror / Atom feed

Pre-PG18 parallel scan estimation: accessing planned worker count from amestimateparallelscan()
2+ messages / 2 participants
[nested] [flat]

* Pre-PG18 parallel scan estimation: accessing planned worker count from amestimateparallelscan()
@ 2026-06-25 01:46  Sivaprasad <[email protected]>
  0 siblings, 1 reply; 2+ messages in thread

From: Sivaprasad @ 2026-06-25 01:46 UTC (permalink / raw)
  To: [email protected]

Hello,

While adding parallel scan support to the Biscuit
<https://github.com/CrystallineCore/Biscuit; index access method, I ran
into a question about the pre-PG18 parallel scan API.

Biscuit partitions scan work into a fixed number of segments at estimation
time and assigns those segments to parallel participants via a
shared-memory descriptor in the DSM segment. Because the segment layout
depends on the number of participants, we need the planned worker count
during amestimateparallelscan() — the only callback that both sizes the DSM
allocation and runs in the same process immediately before
aminitparallelscan().

The callback signatures across versions are:
-

   -

   PG16: Size (*)(void)
   -

   PG17: Size (*)(int nkeys, int norderbys)
   -

   PG18+: Size (*)(Relation, int *nworkers*, int nchunks)


In PG18+, nworkers is available directly. In PG16 and PG17 it is not.

My question: prior to PG18, was there any supported mechanism by which an
index AM could determine the planner's intended parallel worker count
during scan estimation?

Thanks,
Sivaprasad Murali
Biscuit index access method


^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: Pre-PG18 parallel scan estimation: accessing planned worker count from amestimateparallelscan()
@ 2026-06-25 05:42  Peter Geoghegan <[email protected]>
  parent: Sivaprasad <[email protected]>
  0 siblings, 0 replies; 2+ messages in thread

From: Peter Geoghegan @ 2026-06-25 05:42 UTC (permalink / raw)
  To: Sivaprasad <[email protected]>; +Cc: [email protected]

On Wed, Jun 24, 2026 at 9:46 PM Sivaprasad <[email protected]> wrote:
> My question: prior to PG18, was there any supported mechanism by which an index AM could determine the planner's intended parallel worker count during scan estimation?

No.

-- 
Peter Geoghegan






^ permalink  raw  reply  [nested|flat] 2+ messages in thread

end of thread, other threads:[~2026-06-25 05:42 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-06-25 01:46 Pre-PG18 parallel scan estimation: accessing planned worker count from amestimateparallelscan() Sivaprasad <[email protected]>
2026-06-25 05:42 ` Peter Geoghegan <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox