| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Manuel Sugawara <masm(at)fciencias(dot)unam(dot)mx> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Cannot use a standalone backend to VACUUM in "postgres"" |
| Date: | 2008-04-08 01:53:12 |
| Message-ID: | 20080408015312.GI5095@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Wollny | 2008-04-08 02:08:17 | tsvector_update_trigger throws error "column is not of tsvector type" |
| Previous Message | Manuel Sugawara | 2008-04-08 01:44:44 | Cannot use a standalone backend to VACUUM in "postgres"" |