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

From Tom Lane
Subject Re: pgsql-server/src/bin/pg_dump pg_backup_archiver.c
Date
Msg-id 11755.1041630471@sss.pgh.pa.us
Whole thread Raw
In response to pgsql-server/src/bin/pg_dump pg_backup_archiver.c  (inoue@postgresql.org (Hiroshi Inoue))
Responses Re: pgsql-server/src/bin/pg_dump pg_backup_archiver.c
List pgsql-committers
inoue@postgresql.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

pgsql-committers by date:

Previous
From: inoue@postgresql.org (Hiroshi Inoue)
Date:
Subject: pgsql-server/src/bin/pg_dump pg_backup_archiver.c
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql-server/src backend/commands/typecmds.c t ...