Re: how to vacuum from standalone backend

On 12/14/2010 01:04 PM, Steve Clark wrote:
> Help!
>
> This is postgresql 8.1.3 also the database debug can easily be
> recreated if I have to drop it
> but I can't seem to do that either.
>
> vacuumdb debug
> vacuumdb: could not connect to database debug: FATAL: database is not
> accepting commands to avoid wraparound data loss in database "debug"
> HINT: Stop the postmaster and use a standalone backend to vacuum
> database "debug".
>
> I am getting the above message. I am not quite sure how to proceed.
>
> I did the following:
> postgres -D /usr/local/pgsql/data debug
>
> WARNING: database "debug" must be vacuumed within 1000000 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
> WARNING: database "debug" must be vacuumed within 1000000 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
>
> PostgreSQL stand-alone backend 8.1.3
> backend> vacuum full debug;
>
> backend> vacuum full debug;
> WARNING: database "debug" must be vacuumed within 999999 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
> ERROR: relation "debug" does not exist
> backend> vacuum full;
> WARNING: database "debug" must be vacuumed within 999998 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
> WARNING: database "debug" must be vacuumed within 999997 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
> WARNING: database "debug" must be vacuumed within 999996 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
> WARNING: database "debug" must be vacuumed within 999995 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
> WARNING: database "debug" must be vacuumed within 999994 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
> WARNING: database "debug" must be vacuumed within 999993 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
> WARNING: database "debug" must be vacuumed within 999992 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
> WARNING: database "debug" must be vacuumed within 999991 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
> WARNING: database "debug" must be vacuumed within 999990 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
> WARNING: database "debug" must be vacuumed within 999989 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
> WARNING: database "debug" must be vacuumed within 999988 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
> WARNING: database "debug" must be vacuumed within 999987 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
> WARNING: database "debug" must be vacuumed within 999986 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
> WARNING: database "debug" must be vacuumed within 999985 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
> WARNING: database "debug" must be vacuumed within 999984 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
> WARNING: database "debug" must be vacuumed within 999983 transactions
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "debug".
> ERROR: could not access status of transaction 449971277
> DETAIL: could not open file "pg_clog/01AD": No such file or directory
>
>
> Now what?
>
> Thanks in advance.
>
>
Please disregard - figured out how to drop the database.
drop database debug - not dropdb debug - duh!
> --
> Stephen Clark
> *NetWolves*
> Sr. Software Engineer III
> Phone: 813-579-3200
> Fax: 813-882-0209
> Email: steve(dot)clark(at)netwolves(dot)com
> http://www.netwolves.com

--
Stephen Clark
*NetWolves*
Sr. Software Engineer III
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve(dot)clark(at)netwolves(dot)com
http://www.netwolves.com