On 5 November 2015 at 23:10, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > David Steele wrote: > >> The important thing about this implementation was that nothing was >> terminated unless it had exceed a timeout AND was blocking another >> process. > > This seems a nice idea, but you need to take the effect on vacuum of > idle-in-xact sessions too. If the operator left for the day and their > session doesn't block any other process, the next day you could find > some tables bloated to such extreme as to cause problems later on.
The additional qualifier "and isn't pinning xmin" would probably be useful there. Often it's pretty harmless to keep an xact open for ages, the problem has, until the recent changes in pg_stat_activity, been knowing when. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
