I would imagine you'd need a pretty edge case query with a ton of rows
before you would really be able to have enough difference to change plans.
And what would it change to?
Cheers,
Greg
--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support
Serialized transactions have a cost that is currently not accounted for in
planning time: Rows that are retrieved to be filtered by a query get
SIReadLocks. This can made an otherwise-good query plan problematic, since it
contributes to query cancellations. Would it be appropriate to add some
