Alvaro Herrera writes:
> 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 tha
Excerpts from Tom Lane's message of mié oct 20 13:57:16 -0300 2010:
> "Aleksandr Dushein" 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 sto
"Aleksandr Dushein" 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 av
Excerpts from Aleksandr Dushein's message of mié oct 20 06:44:09 -0300 2010:
> FATAL: invalid cache id: 19
Hmm, try removing pg_internal.init from directories under "base/" and
restart single mode. (You then need to run vacuum on the specified
database to get out of the other problem).
--
Álv
The following bug has been logged online:
Bug reference: 5718
Logged by: Aleksandr Dushein
Email address: adush...@rutube.ru
PostgreSQL version: 9.0.1
Operating system: FreeBSD 8.1-RELEASE #0: Mon Jul 19 02:36:49 UTC 2010
r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GE
