Horton

BUG #14941: Vacuum crashes

Lyes Ameddah <lyes.amd@gmail.com>

View thread View on postgr.es
From: lyes.amd@gmail.com
To: pgsql-bugs@postgresql.org
Cc: lyes.amd@gmail.com
Date: 2017-12-01T16:09:07Z
Lists: pgsql-bugs, pgsql-hackers 
The following bug has been logged on the website:

Bug reference:      14941
Logged by:          Lyes Ameddah
Email address:      lyes.amd@gmail.com
PostgreSQL version: 9.6.0
Operating system:   CentOs 7
Description:        

Hello, 

I make a complete empty once a week in an automated way and it happens that
the vacuum is stuck on a table (perhaps another process has a lock first).


The behavior I would like to see is that the void ignores this table and
moves to another instead of being blocked. 

Is it possible to have a solution to this problem please? 
Thank you!

Commits

  1. Add option SKIP_LOCKED to VACUUM and ANALYZE

  2. Rename VACOPT_NOWAIT to VACOPT_SKIP_LOCKED

  3. Add parenthesized options syntax for ANALYZE.

  4. Don't allow VACUUM VERBOSE ANALYZE VERBOSE.

  5. Fix inadequate locking during get_rel_oids().

  6. Avoid having autovacuum workers wait for relation locks.