Re: BUG #3682: Incomplete database restore - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #3682: Incomplete database restore
Date
Msg-id 28892.1192998245@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #3682: Incomplete database restore  ("Heikki Linnakangas" <heikki@enterprisedb.com>)
Responses Re: BUG #3682: Incomplete database restore
Re: BUG #3682: Incomplete database restore
List pgsql-bugs
"Heikki Linnakangas" <heikki@enterprisedb.com> writes:
> Perhaps we should include the functionality of that script in pg_dump.

I'm pretty uncomfortable with the notion of having pg_dump deliberately
throw data away.  Another problem is that even if we did that, it would
only help people who dumped their old DB with 8.3 pg_dump.

Having the functionality in pg_restore would be a little saner, but it
still seems like a big wart.

As for the datatype issue, I wonder whether we should just advise people
to do
    CREATE DOMAIN public.tsvector AS pg_catalog.tsvector;
before restoring?

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Heikki Linnakangas"
Date:
Subject: Re: BUG #3682: Incomplete database restore
Next
From: Tom Lane
Date:
Subject: Re: BUG #3686: Incorrect numeric type conversion to long in plpythonu