From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Hiroshi Inoue <inoue(at)postgresql(dot)org>, pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql-server/src/bin/pg_dump pg_backup_archiver.c |
Date: | 2003-01-06 05:52:44 |
Message-ID: | 3E1919AC.A57C232C@tpf.co.jp |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Tom Lane wrote:
>
> inoue(at)postgresql(dot)org (Hiroshi Inoue) writes:
> > src/bin/pg_dump: pg_backup_archiver.c
>
> > Log message:
> > Adjust lo type in contrib during pg_restore so that pg_restore could
> > reload the type.
>
> I find this really ugly, and I do not believe this code belongs in
> pg_dump (nor pg_restore). We are not in the habit of putting kluges
> into pg_dump to adjust system catalog entries for version-to-version
> changes, and I certainly don't think that we should put in such a kluge
> for a type that's only contrib.
>
> The correct way to update contrib/lo for 7.3 is to load the 7.3
> definition into a database before restoring the old definition.
>
> If someone fails to do that, it'd be okay to supply this fix as a script
> in contrib/lo to run against the database after-the-fact. But I object
> to putting it into pg_restore.
Please tell me how we avoid the failure
ERROR: Unable to identify an operator '=' for types 'oid' and 'lo'
You will have to retype this query using an explicit cast
in pg_restore.
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-01-06 05:55:13 | Re: pgsql-server/src/bin/pg_dump pg_backup_archiver.c |
Previous Message | Bruce Momjian - CVS | 2003-01-06 05:46:18 | pgsql-server/ /configure /configure.in rc/incl ... |