"Graeme B. Bell" <[email protected]> writes:
> Every year or two the core count goes up. Can/should/does postgres ever
> attempt two strategies in parallel, in cases where strategy A is generally
> good but strategy B prevents bad worst case behaviour? Kind of like a
> Schrödinger's Cat approach to scheduling. What problems would it raise?
You can't run two plans and have them both returning rows to the client,
or performing inserts/updates/deletes as the case may be.
regards, tom lane
--
Sent via pgsql-performance mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
