| From: | Claire McLister <mclister(at)zeesource(dot)net> |
|---|---|
| To: | pgsql general list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Large object restore problem w/triggers |
| Date: | 2006-01-12 18:12:39 |
| Message-ID: | A7B179B6-7451-4325-A67F-41C21CA16C2C@zeesource.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
We have a database with a bunch of large objects, who's ids we
reference in a table. There is a trigger associated with inserts and
updates on the table to delete the old value when inserting a new
large object associated with a row in the table.
This causes a problem when doing a pg_dump and pg_restore. The dump
works fine, but when doing a restore it tries to trigger a delete of
an old large object. It seems that the object id is associated with
the database that was dumped, and not the one that was restored. So,
lo_unlink fails and the whole restore aborts.
Has anyone seen this behavior before? Am I doing something wrong?
Is there a workaround for this?
Thanks for your help.
Claire
PS. The dump command was pg_dump --b -Ft -o db > db.tar
Restore command: pg_restore -O -d db db.tar
--
Claire McLister mclister(at)zeesource(dot)net
1684 Nightingale Avenue Suite 201
Sunnyvale, CA 94087 408-733-2737(fax)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-01-12 18:23:14 | Re: Large object restore problem w/triggers |
| Previous Message | rlee0001 | 2006-01-12 18:07:57 | Re: Returning SQL statement |