Re: Postgres BackUp and Restore: ERROR: duplicate key violates unique constraint "pg_largeobject_loid_pn_index"

From: Sam Mason <sam(at)samason(dot)me(dot)uk>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Postgres BackUp and Restore: ERROR: duplicate key violates unique constraint "pg_largeobject_loid_pn_index"
Date: 2009-05-12 13:31:20
Message-ID: 20090512133120.GF22221@samason.me.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, May 12, 2009 at 05:25:26PM +0530, CM J wrote:
> The above results in following exception and the data is not getting
> restored:
>
> ERROR: duplicate key violates unique constraint "pg_largeobject_loid_pn_index"
>
> What else do i need to drop/delete to completely reinitialize my
> database ?

There are "large objects"[1] remaining in the system. The way I've
removed them in the past was by doing a boring:

DELETE FROM pg_largeobject;

A TRUNCATE could probably be used here as well. I wouldn't go as far as
dropping and re-creating the table though.

--
Sam http://samason.me.uk/

[1] http://www.postgresql.org/docs/current/static/catalog-pg-largeobject.html

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Andrew Gould 2009-05-12 13:32:34 Re: Putting many related fields as an array
Previous Message Sam Mason 2009-05-12 13:10:43 Re: Putting many related fields as an array