Hi,
2 possible bugs in pg_dump/pg_restore related to
large objects.
1. Large objects dumped, deleted then restored
do not retain their original OIDs. Big problem as we reference their OIDs
in tables.
2. The pg_restore command --list indicated no Blobs
in the dump file even when there a
"Colin Stearman" <[EMAIL PROTECTED]> 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
On Sat, 23 Nov 2002 [EMAIL PROTECTED] wrote:
> Luís Mota ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> Condition on rule is not respected.
>
> Long Description
> I think I spoted a bug while developing a database. To
I seem to have a little problem here. I have a pg_dump
file that I created with pg 7.1.3 that I just can not
seem to get to load into 7.2.3.
I know that I used the dump file to migrate to 7.2.3
originally, however in upgrading to osx 10.2.2 it
doen't seem to work when I try to use psql:
psql dbn
Tom,
You are 100% right about pg_restore fixing up OID references in tables to
blobs (and presumably any other objects). I should have checked more
carefully and given the program more credit.
I will remove the -o as it is not necessary, as you say.
That resolves my script problem Thanks!.
Re
So, as I said I have a problem restoring data created
with pg_dump. Here is something interesting.
The pg_dump file contains a couple of tables. Some of
them are working. If I go to the line that psql is
telling me is failing, I find the commands to begin
recreating the table:
COPY "fcopenjobs" F
Theodore Petrosky <[EMAIL PROTECTED]> writes:
> COPY "fcopenjobs" FROM stdin;
> If I copy and paste the lines (from the dump file)
> into psql one by one, it will input fine. However, If
> I cut and paste more that two lines, the input fails.
I'm wondering about newline representations, myself.
Tom,
I have checked the dump file with hexedit and find
that the lines end with '0A' hex. Only one character.
What is strange is that I have multiple tables, some
of them are going in fine.
Ted
-- Tom Lane <[EMAIL PROTECTED]> wrote:
> Theodore Petrosky <[EMAIL PROTECTED]> writes:
> > COPY "fco
