Excerpts from Tom Lane's message of mié oct 20 13:57:16 -0300 2010: > "Aleksandr Dushein" <adush...@rutube.ru> writes: > > Description: Cannot start postgres (FATAL: invalid cache id: 19) > > > Hello. I was upgraded my database from 8.4.4 то 9.0.1 one week ago by > > pg_dump/pg_restore. Yesterday database stop responding with message ERROR: > > database is not accepting commands to avoid wraparound data loss > > I trying to restart in single mode and fail with the same error. > > Ugh. The "invalid cache id" failure is my fault. You can fix that by > applying this patch to 9.0: > http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=c98cd9bdb618794643b670c8240c0aad213340c7 > after which you'll probably need to do a manual vacuum with a standalone > backend before the DB will restart. > > However, the bigger question is how you got into this state in the first > place. Even if you'd had autovacuum turned off, it should have > protected you against a wraparound. I suspect that pg_upgrade is > failing to preserve datfrozenxid and related values properly.
This exact symptom was just reported twice in pgsql-es-ayuda. Upgrading to 9.0.4 fixed the problem. One of them used pg_upgrade from a previous version, the other one did not. I'm not sure that it's worthwhile to expore the underlying cause, but it seems clear that pg_upgrade is not the only possibly guilty party. -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
