From: pgsql-sql <pgsql-sql@fc.emc.com.ph>
To: zakkr@zf.jcu.cz
Cc: tjk@tksoft.com
Cc: pgsql-sql@postgresql.org
Subject: Re(2): Re(2): Large Object dump ?
Date: Wed, 01 Nov 2000 21:44:50 +0800
Message-ID: <fc.000f5672007948d8000f5672007948d8.7948ed@fc.emc.com.ph> (raw)
because of some problems (see below). i was also thinking that it was
just a compatibility problem of pg_dumplo-0.0.5 to postgresql 6.5.3.
and because i needed it badly, i wrote a "quick & dirty" perl script.
1. When I tried showing all LO of my_db, I got this message:
pg_dumplo -w -d my_db
NOTICE: (transaction aborted): queries ignored until END
NOTICE: (transaction aborted): queries ignored until END
NOTICE: (transaction aborted): queries ignored until END
Database 'my_db' contains 0 large objects.
My observation: my_db actually contains large objects.
2. When I tried this
pg_dumplo -a -d my_db -s /my_dump/dir
I got this.
<< CUT >>
dump for_payment.application (218 large obj)
lo_export: can't open inv object 4654657:
/fs/linux/work/tools/pg_dumplo-0.0.5/pg_dumplo
lo_export: can't open inv object 4654689:
/fs/linux/work/tools/pg_dumplo-0.0.5/pg_dumplo
lo_export: can't open inv object 4654881:
/fs/linux/work/tools/pg_dumplo-0.0.5/pg_dumplo
lo_export: can't open inv object 4654081:
/fs/linux/work/tools/pg_dumplo-0.0.5/pg_
<< CUT >>
Exported 1131 large objects.
NOTICE: LockReleaseAll: xid loop detected, giving up
My observation: The tree (directories) were created but 1131 large objects
were not there.
The lo_dump.index file is not readable
(contains garbage).
peace,
sherwin
zakkr@zf.jcu.cz writes:
>
>On Wed, 1 Nov 2000, pgsql-sql wrote:
>
>> You can try the script I made for exporting all my Pg database.
>> Ideas were borrowed from pg_dumplo-0.0.5.
>> Make it sure that you have "Perl5 extension for PostgreSQL - Pg.pm"
>> installed.
>
> Why you re-write pg_dumplo to perl and not use directly it? Perl
>love? :-)
>
> Karel
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: pgsql-sql@fc.emc.com.ph, zakkr@zf.jcu.cz, tjk@tksoft.com
Subject: Re: Large Object dump ?
In-Reply-To: <fc.000f5672007948d8000f5672007948d8.7948ed@fc.emc.com.ph>
References: <fc.000f5672007948d8000f5672007948d8.7948ed@fc.emc.com.ph>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox