"Graeme B. Bell" <grb@skogoglandskap.no> writes:
> Every year or two the core count goes up. Can/should/does postgres ever attempt two strategies in parallel, in cases
wherestrategy A is generally good but strategy B prevents bad worst case behaviour? Kind of like a Schr�dinger's Cat
approachto 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