Thread

1. Exposing some hidden serializable transaction costs

   Christophe Pettus <xof@thebuild.com> — 2025-06-30T23:00:22Z

   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 kind of cost constant to filtered rows to reflect that?
   
   
   

2. Re: Exposing some hidden serializable transaction costs

   Greg Sabino Mullane <htamfids@gmail.com> — 2025-07-21T19:10:31Z

   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