From: | Hellmuth Vargas <hivs77(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | problem with restore: collision id`s lob |
Date: | 2011-12-01 19:21:20 |
Message-ID: | CAN3Qy4p-1rW8-qn=NpdXRtWDdO+mnDTurY0eAwWu90CrLtRJ3g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
is that I have a number of postgres cluster we want to consolidate into a
single cluster. Every cluster has a database with different schemas names
each therefore inprinciple could create a single database where they could
live all schemas and should have no problem, we generate a dump and SQL file,
we begin to restore files and at first annoyed with the first and second but
the third and fourth at the time you are restoring lob the following error:
pg_restore: *** aborted because of error
pg_restore: [archiver] could not create large object 21709: ERROR:
duplicate key value violates unique constraint
"pg_largeobject_metadata_oid_index" DETAIL: Key (oid)=(21709) already
exists. pg_restore: *** aborted because of error
Thanks
From | Date | Subject | |
---|---|---|---|
Next Message | Frank Lanitz | 2011-12-01 20:48:54 | Re: Use a custom postgresql.conf? |
Previous Message | Bèrto ëd Sèra | 2011-12-01 07:18:10 | Re: transaction error handling |
From | Date | Subject | |
---|---|---|---|
Next Message | David Johnston | 2011-12-01 19:31:26 | Re: recursive inner trigger call |
Previous Message | Red Light | 2011-12-01 19:17:54 | Re: recursive inner trigger call |