large object dump-restore problem(bug?)

From: Risko Peter <peter(at)risko(dot)hu>
To: risko gergely <risko(at)atom(dot)hu>, pgsql-general(at)postgresql(dot)org
Subject: large object dump-restore problem(bug?)
Date: 2002-04-25 20:37:49
Message-ID: Pine.LNX.4.21.0204252237260.363-100000@pepehost.ike
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello,

I am using postgresql 7.2.1-2 on Debian (woody). Everything is fine, but
it seems to me that lo dumping/restoring (or lo_import?) is buggy:

-with psql I import some lo into the db:
vegzes=# \lo_import /pl.sh 'alma'
lo_import 16590
vegzes=# \lo_list
Large objects
ID | Description
-------+-------------
16590 | alma
(1 row)
-It is okay, now I dump the db, in bash:
pg_dump -o -b -u -Ft vegzes >vegzes.dump
-It's okay, now I drop and recreate the db (bash):
dropdb -U postgres vegzes
createdb -T template0 -U postgres vegzes
-It's ok., let me restore it (bash):
pg_restore -v -u -d vegzes vegzes.dump
User name: postgres
pg_restore: connecting to database for restore
Password:
pg_restore: implied data-only restore
pg_restore: executing <Init> Max OID
pg_restore: disabling triggers
pg_restore: restoring data for table BLOBS
pg_restore: restoring large object OID 16590
pg_restore: connecting to database vegzes as user postgres
Password:
pg_restore: creating table for large object cross-references
pg_restore: restored 1 large objects
pg_restore: enabling triggers
pg_restore: disabling triggers
pg_restore: enabling triggers
-It's okay, let me check the db (psql):
vegzes=# \lo_list
Large objects
ID | Description
-------+-------------
16600 |

Here is my problem. The lo I restored has a new ID, and the description
vanished. Is there a solution for this?

thanks: Peter RISKO

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Robert J. Sanford, Jr. 2002-04-25 20:41:02 Re: odd psql behaviour on OSX
Previous Message Robert J. Sanford, Jr. 2002-04-25 20:21:16 Re: odd psql behaviour on OSX