Обсуждение: No restore of BLOB data (permissions?)
pg_restore: [archiver] could not create large object 16591
pg_restore: *** aborted because of error
1691; 0 0 BLOB COMMENTS - BLOB COMMENTS
Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase.
Hi,
Try this command
Pg_restore.exe –i –h localhost -p 5432 –U (username) -d (database_name) –V “ Path of your Backup files”
Jayakumar M
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Jordi Mulet
Sent: Tuesday, August 28, 2007 3:32 PM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] No restore of BLOB data (permissions?)
Hi,
I tried to backup and restore a database (including blob data) and pg_restore give me an error (pg_dump seems to be working Ok).
Message.
pg_restore -c -h localhost -p 5432 -U postgres -d database1 -v database1.backup
pg_restore: restoring BLOBS
pg_restore: [archiver] could not create large object 16591
pg_restore: *** aborted because of error
pg_dump.exe -h localhost -p 5432 -U postgres -v -o -F c -b database1 -f "database1.backup"
database1.backup is created (aprox. 25 MB)
error code 0
I tried pg_restore -l in order to list contents of backup file and it seems some problem is detected on database1.backup:
1690; 0 0 BLOBS - BLOBS
1691; 0 0 BLOB COMMENTS - BLOB COMMENTS
Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase.
DISCLAIMER:
This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated..
Jordi Mulet <jmuletalbiach@yahoo.com> writes:
> Hi,=0A I tried to backup and restore a database (including blob data) and =
> pg_restore give me an error (pg_dump seems to be working Ok).=0AMessage.=0A=
> pg_restore -c -h localhost -p 5432 -U postgres -d database1 -v database1.b=
> ackup=0A=0Apg_restore: restoring BLOBS=0Apg_restore: [archiver] could not c=
> reate large object 16591=0Apg_restore: *** aborted because of error=0A=0Apg=
> _dump.exe -h localhost -p 5432 -U postgres -v -o -F c -b database1 -f "da=
> tabase1.backup"=0A=0Adatabase1.backup is created (aprox. 25 MB)=0A=0Aerror =
> code 0=0A=0AI tried pg_restore -l in order to list contents of backup fil=
> e and it seems some problem is detected on database1.backup:=0A=0A1690; 0 0=
> BLOBS - BLOBS =0A1691; 0 0 BLOB COMMENTS - BLOB COMMENTS=0A=0A=0A =
Please fix your mailer to not mangle text like that ...
Anyway. I'm wondering about version skew. What PG version is this, and
in particular are the pg_restore and server the same version? What
shows up in the postmaster log when this happens?
regards, tom lane
Version 8.2. pg_restore 8.2.4 pg_dump 8.2.4 Info on log file: 2007-08-29 08:46:52 ERROR: duplicate key violates unique constraint "pg_largeobject_loid_pn_index" Regards, Jordi Please fix your mailer to not mangle text like that ... Anyway. I'm wondering about version skew. What PG version is this, and in particular are the pg_restore and server the same version? What shows up in the postmaster log when this happens? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly ____________________________________________________________________________________Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. http://tv.yahoo.com/
Jordi Mulet <jmuletalbiach@yahoo.com> writes:
> Info on log file:
> 2007-08-29 08:46:52 ERROR: duplicate key violates unique constraint "pg_lar=
> geobject_loid_pn_index"
So the problem is you've already *got* that blob, or at least one with
the same OID, in the target database. Try restoring into an empty
database.
regards, tom lane