On Fri, Dec 1, 2017 at 1:53 PM, Bossart, Nathan <bossa...@amazon.com> wrote: > There is already an internal flag called VACOPT_NOWAIT that gives > autovacuum this ability in certain cases (introduced in the aforementioned > commit), and I recently brought up this potential use-case as > justification for a patch [0]. I'd be happy to submit a patch for > providing VACOPT_NOWAIT to users if others think it's something we should > do.
Seems entirely reasonable to me, provided that we only update the extensible-options syntax: VACUUM [ ( option [, ...] ) ] [ table_and_columns [, ...] ] I don't want to add any more options to the older syntax: VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [ ANALYZE ] [ table_and_columns [, ...] ] I am slightly confused as to how we got on to this topic since the subject is "Vacuum crashes", but perhaps Lyes was simply speaking imprecisely. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company