From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Guerin <guerin(at)rentec(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: DB Crash, recoverable? |
Date: | 2005-01-26 19:54:03 |
Message-ID: | 18953.1106769243@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Michael Guerin <guerin(at)rentec(dot)com> writes:
> Our database just reset and now I'm getting Errors in the log and I
> would like to know if this is recoverable. Here's the segment of the
> log right before and after it reset.
> ERROR: duplicate key violates unique constraint "pg_type_typname_nsp_index"
> 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 varchar(50), level int4 )"
> PL/pgSQL function "fngetcompositeids2" line 14 at SQL statement
Hmm, looks like a previous incarnation of this table was not completely
deleted. Does it help if you REINDEX pg_type?
> => select version();
> version
> -----------------------------------------------------------------------------
> PostgreSQL 8.0.0beta5 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.4.2
You really shouldn't be still using such an old beta version. There are
a heck of a lot of bug fixes since beta5 ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Eduardo Vázquez Rodríguez | 2005-01-26 20:02:29 | Postgres 8.0 on FAT32 |
Previous Message | Michael Guerin | 2005-01-26 19:07:24 | DB Crash, recoverable? |