Hi,
I'm not sure what the cause of this error is, but I figured I
should post it. I had to restore from back to stop getting these errors
"ERROR: cache lookup failed for type 813612037" . This was from a
database running beta4, i'm now running beta5.
-michael
LOG: unexpected EOF on client connection
ERROR: duplicate key violates unique constraint "pg_type_typname_nsp_index"
ERROR: duplicate key violates unique constraint "pg_type_typname_nsp_index"
CONTEXT: SQL statement "create temp table tmp_children ( uniqid bigint,
memberid bigint, membertype varchar(50), ownerid smallint, tag varc
har(50), level int4 )"
PL/pgSQL function "fngetcompositeids2" line 14 at SQL statement
ERROR: duplicate key violates unique constraint "pg_type_typname_nsp_index"
CONTEXT: SQL statement "create temp table tmp_children ( uniqid bigint,
memberid bigint, membertype varchar(50), ownerid smallint, tag varc
har(50), level int4 )"
PL/pgSQL function "fngetcompositeids2" line 14 at SQL statement
ERROR: cache lookup failed for type 813612037
FATAL: cache lookup failed for type 813612037
LOG: server process (PID 10449) exited with exit code 1
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back
the current transaction and exit, because another server process exit
ed abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back
the current transaction and exit, because another server process exit
ed abnormally and possibly corrupted shared memory.
--More--(74%)