Problems with vacuumdb
Hi all.
I am receiving the following message when I do the vacuumdb process on a
production database:
INFO: vacuuming "pg_catalog.pg_largeobject"
INFO: index "pg_largeobject_loid_pn_index" now contains 4828104 row
versions in 37078 pages
DETAIL: 278 index row versions were removed.
116 index pages have been deleted, 116 are currently reusable.
CPU 0.52s/1.23u sec elapsed 225.77 sec.
vacuumdb: vacuuming of database "log" failed: ERROR: canceling query due to
user request
It seems to me that the process performs successfully a reindex of
pg_largeobject_loid_pn_index, but it doesn't finish the vacuuming of
pg_largeobject.
I'm running PostgreSQL 8.0.3 on Debian GNU/Linux. The command I am using is:
/usr/local/pgsql/bin/vacuumdb -d -e -v log >/home/pgsql/vacuum_log.log
Is there anything you would suggest, in order for the vacuum process to get
through? Any parameters I should fix?
Thanks in advance,
-----------------------------------------------
Ignacio Colmenero
Software Development
Micotan Software Company Ltd.
"Ignacio Colmenero" <ignacio.colmenero@micotan.com> writes:
I am receiving the following message when I do the vacuumdb process on a
production database:
vacuumdb: vacuuming of database "log" failed: ERROR: canceling query due to
user request
Do you have a statement_timeout limit set?
regards, tom lane
No. The statement_timeout parameter is set to 0.
Thanks.
-----------------------------------------------
Ignacio Colmenero
Software Development
Micotan Software Company Ltd.
-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org] On Behalf Of Tom Lane
Sent: September 19, 2005 2:36 PM
To: Ignacio Colmenero
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Problems with vacuumdb
"Ignacio Colmenero" <ignacio.colmenero@micotan.com> writes:
I am receiving the following message when I do the vacuumdb process on a
production database:
vacuumdb: vacuuming of database "log" failed: ERROR: canceling query due
to
user request
Do you have a statement_timeout limit set?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
No. The statement_timeout parameter is set to 0.
Thanks.
-----------------------------------------------
Ignacio Colmenero
Software Development
Micotan Software Company Ltd.
-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org] On Behalf Of Tom Lane
Sent: September 19, 2005 2:36 PM
To: Ignacio Colmenero
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Problems with vacuumdb
"Ignacio Colmenero" <ignacio.colmenero@micotan.com> writes:
I am receiving the following message when I do the vacuumdb process on a
production database:
vacuumdb: vacuuming of database "log" failed: ERROR: canceling query due
to
user request
Do you have a statement_timeout limit set?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster