From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Colin Stearman" <cstearman(at)infofind(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: pg_dump/pg_restore |
Date: | 2002-11-24 17:57:24 |
Message-ID: | 27053.1038160644@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"Colin Stearman" <cstearman(at)infofind(dot)com> writes:
> 1. Large objects dumped, deleted then restored do not retain their original=
> OIDs. Big problem as we reference their OIDs in tables.
They're not supposed to (indeed cannot). pg_restore is supposed to arrange
for references to large-object OIDs to be updated to the new values,
however. I believe it looks in columns of types OID and LO --- if you
stored your references in plain int columns, that was a mistake.
If you're using the -o option simply because you think you need it for
blobs, you don't need it.
> 2. The pg_restore command --list indicated no Blobs in the dump file even w=
> hen there are. For example:
> 75; 0 BLOBS BLOBS=20
Looks like you have blobs to me: that entry wouldn't even be there,
otherwise.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2002-11-24 18:11:00 | Re: Bug #822: Condition on rule is not respected. |
Previous Message | Adam Buraczewski | 2002-11-24 17:37:09 | PostgreSQL 7.3rc1: initdb fais with '-W' switch given in the command line. |