>> But, nworkers_launched is always set to 0 in
>> InitializeDSMForeignScan(), so that won’t work. Any other ideas?
>
> At that state it's simply not yet known how many workers will be
> actually launched (they might not start successfully or such). Why do
> you need to know it there and not later?
>
> - Andres
I need to know at some point *before* I actually start scanning. The
ParallelContext pointer is only available in EstimateDSMForeignScan(),
InitializeDSMForeignScan(), and ReInitializeDSMForeignScan().
If there is some other way to discover the actual worker count, I’m open to
that. The three functions above are not particularly helpful to me so I’m
happy to look somewhere else.
— Korry
