BUG #8954: Wrong text in database log during "truncate scan"

The following bug has been logged on the website:

Bug reference:      8954
Logged by:          Maksym
Email address:      maxim.boguk@gmail.com
PostgreSQL version: 9.2.4
Operating system:   Linux
Description:

Hi,

If manual vacuum performed in the table and could not required lock for
truncate scan it wrote a bit misleading error message:

2014-01-24 16:19:11 MSK 7134 cron.app@*** from [local] [vxid:297/14422865
txid:2179070646] [VACUUM] LOG:  automatic vacuum of table
"hh_data.public.vacancy_response": could not (re)acquire exclusive lock for
truncate scan
2014-01-24 16:19:11 MSK 7134 cron.app@*** from [local] [vxid:297/14422865
txid:2179070646] [VACUUM] STATEMENT:  VACUUM public.vacancy_response
2014-01-24 16:19:11 MSK 7134 cron.app@*** from [local] [vxid:297/0 txid:0]
[VACUUM] LOG:  duration: 589175.931 ms  statement: VACUUM
public.vacancy_response


Please note "automatic vacuum of table".
It was definitely not autovacuum but manual vacuum run.