Tom Lane writes:
> A conncurrent-xacts limit isn't perfect of course, but I think it'd
> be pretty good, and certainly better than anything based on the
> available load-average numbers.
The concurrent transaction limit would allow you to control the absolute
load of the PostgreSQL server, but we can already do that and it's not
what we're after here. The idea behind the load average based approach is
to make the postmaster respect the situation of the overall system.
Additionally, the concurrent transaction limit would only be useful on
setups that have a lot of idle transactions. Those setups exist, but not
everywhere.
To me, both of these approaches are in the "if you don't like it, don't
use it" category.
--
Peter Eisentraut peter_e@gmx.net http://funkturm.homeip.net/~peter