On Thu, 15 Dec 2022 at 18:26, David Rowley wrote:
> I propose the attached which gets rid of the not-so-great casting
> method that was originally added to this test to try and force the seq
> scan. It seems a little dangerous to put in hacks like that to force
> a particular plan when the result
I'm in the middle of working on making some adjustments to the costs
of Incremental Sorts and I see the patch I wrote changes the plan in
the drop-index-concurrently-1 isolation test.
The particular plan changed currently expects:
---
Sort
Sort Key: i
