table "db1.public.a" and all behind "db1.public.a" tables did not do analyzing

From: mark_2014 <maxiangqian(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: table "db1.public.a" and all behind "db1.public.a" tables did not do analyzing
Date: 2014-02-21 02:43:52
Message-ID: 1392950632104-5792980.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

when I used vacuumdb -d db1 -z -v > /BACKUP/script/db1.$LOG_DATE.log 2>&1
it occued this error [automatic vacuum of table "db1.public.a": could not
(re)acquire exclusive lock for truncat]
and table "db1.public.a" and all behind "db1.public.a" tables did not do
analyzing.
I want to know:
1.why table "db1.public.a" and all behind "db1.public.a" tables did not do
analyzing?

log is below:
#PostGreSQL: VACUUM 2014-02-07 05:36:16 CST user db1 [local] CSTINFO:
vacuuming "public.t1"
#PostGreSQL: VACUUM 2014-02-07 05:36:16 CST user db1 [local] CSTINFO:
analyzing "public.t1"
#PostGreSQL: VACUUM 2014-02-07 05:36:16 CST user db1 [local] CSTINFO:
vacuuming "public.t2"
#PostGreSQL: VACUUM 2014-02-07 05:36:16 CST user db1 [local] CSTINFO:
analyzing "public.t2"

#PostGreSQL: VACUUM 2014-02-07 05:36:16 CST user db1 [local] CSTINFO:
vacuuming "public.a"
#PostGreSQL: VACUUM 2014-02-07 05:36:18 CST user db1 [local] CSTLOG:
automatic vacuum of table "db1.public.a": could not (re)acquire exclusive
lock for truncate scan

#PostGreSQL: VACUUM 2014-02-07 05:36:18 CST user db1 [local] CSTINFO:
vacuuming "public.b"
#PostGreSQL: VACUUM 2014-02-07 05:36:18 CST user db1 [local] CSTINFO:
vacuuming "public.c"
#PostGreSQL: VACUUM 2014-02-07 05:36:20 CST user db1 [local] CSTINFO:
vacuuming "public.d"
#PostGreSQL: VACUUM 2014-02-07 05:36:20 CST user db1 [local] CSTINFO:
vacuuming "public.e"
#PostGreSQL: VACUUM 2014-02-07 05:36:27 CST user db1 [local] CSTINFO:
vacuuming "public.f"
#PostGreSQL: VACUUM 2014-02-07 05:36:27 CST user db1 [local] CSTINFO:
vacuuming "public.g"
#PostGreSQL: VACUUM 2014-02-07 05:36:27 CST user db1 [local] CSTINFO:
vacuuming "public.h"
#PostGreSQL: VACUUM 2014-02-07 05:36:27 CST user db1 [local] CSTINFO:
vacuuming "public.i"
#PostGreSQL: VACUUM 2014-02-07 05:36:36 CST user db1 [local] CSTINFO:
vacuuming "public.j"
#PostGreSQL: VACUUM 2014-02-07 05:36:37 CST user db1 [local] CSTINFO:
vacuuming "public.k"
#PostGreSQL: VACUUM 2014-02-07 05:36:37 CST user db1 [local] CSTINFO:
vacuuming "public.m"

--
View this message in context: http://postgresql.1045698.n5.nabble.com/table-db1-public-a-and-all-behind-db1-public-a-tables-did-not-do-analyzing-tp5792980.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

Browse pgsql-general by date

  From Date Subject
Next Message James Harper 2014-02-21 05:14:40 semi-variable length type
Previous Message rob stone 2014-02-21 02:25:05 Re: Will Postgres work with Oracle Forms 6i?