Hi,
On 2017-05-10 13:09:38 -0700, Jeff Janes wrote:
> Autovacuum's analyze starts a transaction when it starts on a table, and
> holds it for the duration. This holds back the xmin horizon.
Yea, I also complained about this:
http://archives.postgresql.org/message-id/20151031145303.GC6064%40alap3.
Autovacuum's analyze starts a transaction when it starts on a table, and
holds it for the duration. This holds back the xmin horizon.
On a TPC-B-like benchmark, this can be a problem. While it is
autoanalyzing pgbench_accounts and pgbench_history, dead-but-for-analyze
tuples accumulate rapidly in
