Postgres Pro
Downloads
Home   >   mailing lists

Re: Cannot use a standalone backend to VACUUM in "postgres"" - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: Cannot use a standalone backend to VACUUM in "postgres""
Date
Msg-id 20080408015312.GI5095@alvh.no-ip.org
Whole thread Raw
In response to Cannot use a standalone backend to VACUUM in "postgres""  (Manuel Sugawara <masm@fciencias.unam.mx>)
Responses Re: Cannot use a standalone backend to VACUUM in "postgres""  (Manuel Sugawara <masm@fciencias.unam.mx>)
Re: Cannot use a standalone backend to VACUUM in "postgres""  (Manuel Sugawara <masm@fciencias.unam.mx>)
List pgsql-general
Tree view 
Manuel Sugawara wrote:

Hi Manuel,

> The funny thing is that there was no open transactions, even after
> restarting the cluster the same message was logged. Today, the
> database stopped working as expected:
>
> ERROR: database is shut down to avoid wraparound data loss in database "postgres"
> HINT: Stop the postmaster and use a standalone backend to VACUUM in "postgres"

I suggest you look for temp tables that have not been reclaimed.  We've
had a couple of reports where leftover temp tables have stopped the
frozen-xid counter from advancing.  (They would have a very old
relfrozenxid.)

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-general by date:

Previous
From: Manuel Sugawara
Date:
Subject: Cannot use a standalone backend to VACUUM in "postgres""
Next
From: "Markus Wollny"
Date:
Subject: tsvector_update_trigger throws error "column is not of tsvector type"