From: | maxim(dot)boguk(at)gmail(dot)com |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #8954: Wrong text in database log during "truncate scan" |
Date: | 2014-01-24 12:37:17 |
Message-ID: | 20140124123717.26701.48436@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 8954
Logged by: Maksym
Email address: maxim(dot)boguk(at)gmail(dot)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(dot)app(at)*** 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(dot)app(at)*** from [local] [vxid:297/14422865
txid:2179070646] [VACUUM] STATEMENT: VACUUM public.vacancy_response
2014-01-24 16:19:11 MSK 7134 cron(dot)app(at)*** 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2014-01-24 14:29:00 | Re: BUG #8954: Wrong text in database log during "truncate scan" |
Previous Message | Michael Meskes | 2014-01-24 08:09:26 | Re: BUG #8893: Precompiler ECPG doesn't check Var-List in Select corrrect. |