If so, adding some randomness in the decision process would suffice to
counter the adversarial input argument you raised.

This is specifically addressed by the paper. Indeed, randomly choosing
a pivot is a common strategy. It won't fix the problem.

Too bad. I must admit that I do not see how to build a test case which would trigger a worst case behavior against a qsort which chooses the pivot randomly, but I have not read the paper, and possibly there is an element of context which is eluding me.


Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to