On Sun, Oct 21, 2007 at 04:24:05PM -0400, Tom Lane wrote:
> "Heikki Linnakangas" <[EMAIL PROTECTED]> 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.
Don't we already say you should use 8.3 pg_dump to dump your old db when
upgrading?
> 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?
Unless it's something that's only temporary, I would prefer something that
would migrate the actual schema instead of requiring a domain sitting there
*forever*. The overhead isn't large, but it's there...
//Magnus
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
