[GENERAL] Re: problems with pg_dumplo (was Re: backup with blobs)
On Fri, Apr 20, 2001 at 12:48:36PM +0200, Karel Zak wrote: > > > > when working on an own database things works perfect. However I have a > > reproduceable problem on a different database when importing blobs > > into a single table while the old blobs still existing (no matter if > > using -r or not) > > Do you have right permissions for DB and dirs with LO dumps? > yes, I'm in real god-mode. > > However: the problem is not happening on a new created database, so > > maybe there is a problem on my system. > > Hmm.. may be, sounds curious if everythig is right on mew DB. > It is curious and I dont want play around any more on my testmachine. Later in the weekend I will jump into the production-server and dump all the stuff and try to restore the data in a new installed 7.1-environment. I'll post my success/failure here then. thnx, peter -- mag. peter pilsl phone: +43 676 3574035 fax : +43 676 3546512 email: [EMAIL PROTECTED] sms : [EMAIL PROTECTED] pgp-key available ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[GENERAL] Re: problems with pg_dumplo (was Re: backup with blobs)
On Fri, Apr 20, 2001 at 10:27:11AM +0200, Karel Zak wrote: > > > > Thanx to Tom for this great tool. > > Sure :-) > sorry !! I ment to say, Thnx for giving this tool to me. Even more thanx for writing this great tool to you !! :) > > pg_dumplo -i (without -r) add *new* LO to DB and update LO oid in some > tab.attr only. The option '-r' remove old LO and import new. > > Try: > > pg_dumplo -a -d my_db -s /my_dump/dir > pg_dump [with relevant options for your DB] > my.dump > DROP DATABASE my_db; > CREATE DATABASE my_db; > psql my_db < my.dump > pg_dumplo -i -d my_db -s /my_dump/dir > when working on an own database things works perfect. However I have a reproduceable problem on a different database when importing blobs into a single table while the old blobs still existing (no matter if using -r or not) However: the problem is not happening on a new created database, so maybe there is a problem on my system. I will install 7.1 on a different machine and try if I can import all my data before migrating to 7.1 on a production-server. When I want to migrate _all_ data from one 7.1 to another 7.1 : does a brute filecopy do it ? Thanx a lot for your help, peter -- mag. peter pilsl phone: +43 676 3574035 fax : +43 676 3546512 email: [EMAIL PROTECTED] sms : [EMAIL PROTECTED] pgp-key available ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[GENERAL] Re: problems with pg_dumplo (was Re: backup with blobs)
On Fri, Apr 20, 2001 at 02:12:23AM +0200, Peter Pilsl wrote: > On Wed, Apr 18, 2001 at 06:07:33PM -0400, Tom Lane wrote: > > > > No need to re-invent the wheel; use the attached. > > > > Thanx to Tom for this great tool. Sure :-) > Unfortunately it does not work in my testenvironment. > When importing the blobs again, I always get the following error: > > lupo:/tmp/pgdump_lo # pg_dumplo -i -d peter -s ./ -u user -p pass > 66611 blobtestlo_oid peter/blobtest/lo_oid/66611 > 66707 blobtestlo_oid peter/blobtest/lo_oid/66707 > 66867 blobtestlo_oid peter/blobtest/lo_oid/66867 > > 70579 blobtestlo_oid peter/blobtest/lo_oid/70579 > 70643 blobtestlo_oid peter/blobtest/lo_oid/70643 > pg_dumplo: lo_import: can't create inv object for ".//peter/blobtest/lo_oid/70643" > > pg_dumplo: ROLLBACK What do you do before this import? pg_dumplo -i (without -r) add *new* LO to DB and update LO oid in some tab.attr only. The option '-r' remove old LO and import new. Try: pg_dumplo -a -d my_db -s /my_dump/dir pg_dump [with relevant options for your DB] > my.dump DROP DATABASE my_db; CREATE DATABASE my_db; psql my_db < my.dump pg_dumplo -i -d my_db -s /my_dump/dir Karel -- Karel Zak <[EMAIL PROTECTED]> http://home.zf.jcu.cz/~zakkr/ C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
