On 2014-12-02 12:22:42 -0800, Jeff Janes wrote: > Or maybe I overestimate how hard it would be to make vacuum > restartable.
That's a massive project. Which is why I'm explicitly *not* suggesting that. What I instead suggest is a separate threshhold after which vacuum isn't going to abort automaticlaly after a lock conflict. So after that threshold just behave like anti wraparound vacuum already does. Maybe autovacuum_vacuum/analyze_force_threshold or similar. If set to zero, the default, that behaviour is disabled. If set to a positive value it's an absolute one, if negative it's a factor of the normal autovacuum_vacuum/analyze_threshold. Greetings, Andres Freund -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
