Mark Anns wrote:
> How the planning factors of PGStrom differs from planning factos of
> PostgreSQL?
I don't know what exactly you mean by a "planning factor".
What PGStrom does is estimate the cost of the GPU operations
and attach these costs to a custom scan node which is part of
a query plan.
Many different plans are generated; some will involve PGStrom,
some will not. The optimizer then chooses among these plans the
one with the lowest total cost.
Yours,
Laurenz Albe
