> In the workloads where it might not be a good idea (very long queries on
> the standby, many dead tuples on the primary) you need to think very
> carefuly about the strategy of avoiding conflicts anyway, and explicit
> configuration is required as well.
>
> Does anybody have an argument against changing the default value?
On balance, I think it's a good idea. It's easier for new users,
conceptually, to deal with table bloat than query cancel.
Have we done testing on how much query cancel it actually eliminates?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
