postgresqlautovacuum

PG log : could not (re)acquire exclusive lock for truncate scan


PG logs are getting fill with

2019-03-08 07:01:20 PST LOG: automatic vacuum of table "hpdpidb.hpdpidb_app.dp_catalog_object_versession": could not (re)acquire exclusive lock for truncate scan

Can anyone tell about this logging message? Why I am getting this? Do I need to worry about this? How to ignore/fix this?


Solution

  • The error message mostly means that you should upgrade PostgreSQL to a later version.

    It was removed from the code in this commit in April 2013.

    The message itself is nothing to worry about: it means that VACUUM could not truncate (reduce in size) a table whose last pages have become empty.

    In current PostgreSQL versions, the corresponding message has been reduced to log level DEBUG2, so it wouldn't show up in your log.