That's just that some other process has some DML going on in the table that is supposed to be truncated. No lock, no truncate.
HTH, Bambi. From: pgsql-admin-ow...@postgresql.org [mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Nik Tek Sent: Wednesday, April 10, 2013 4:58 PM To: pgsql-performa...@postgresql.org; pgsql-admin@postgresql.org Subject: [ADMIN] Postgres log(pg_logs) have lots of message Hi, Could some please explain what these warnings mean in postgres. I see these messages a lot when automatic vacuum runs. 1 tm:2013-04-10 11:39:20.074 UTC db: pid:13766 LOG: automatic vacuum of table "DB1.nic.pvxt": could not (re)acquire exclusive lock for truncate scan 1 tm:2013-04-10 11:40:22.849 UTC db: pid:14286 LOG: automatic vacuum of table "DB1.nic.pvxt": could not (re)acquire exclusive lock for truncate scan 1 tm:2013-04-10 11:41:17.500 UTC db: pid:14491 LOG: automatic vacuum of table "DB1.nic.pvxt": could not (re)acquire exclusive lock for truncate scan Thank you Nik This email and any files included with it may contain privileged, proprietary and/or confidential information that is for the sole use of the intended recipient(s). Any disclosure, copying, distribution, posting, or use of the information contained in or attached to this email is prohibited unless permitted by the sender. If you have received this email in error, please immediately notify the sender via return email, telephone, or fax and destroy this original transmission and its included files without reading or saving it in any manner. Thank you.
