Re: pgsql-server/src/bin/pg_dump pg_backup_archiver.c

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: inoue(at)postgresql(dot)org (Hiroshi Inoue)
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql-server/src/bin/pg_dump pg_backup_archiver.c
Date: 2003-01-03 21:47:51
Message-ID: 11755.1041630471@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2003-01-04 00:46:09 pgsql-server/src backend/commands/typecmds.c t ...
Previous Message Hiroshi Inoue 2003-01-03 18:05:02 pgsql-server/src/bin/pg_dump pg_backup_archiver.c