Re:

> -----Original Message-----
> From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
> Sent: 12 September 2002 00:53
> To: Dave Page
> Cc: Oliver Elphick; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS]
>
>
> OK, I am going to add these items to the open items list
> because I am having trouble keeping track of all the
> compatibility changes for pg_dump.
>
> I have:
>
>     Loading 7.2 pg_dumps
>             opaque language handler no longer recognized
>
> What else is there?
>
> Do cast problems related to pg_dump loading or to working
> with the data after the load?  Is it casts in user functions?

Oliver reported:

2.  The dump produced:    CREATE TABLE cust_alloc_history (        ...       "year" integer DEFAULT
date_part('year'::text,               ('now'::text)::timestamp(6) with time zone) NOT NULL,        ...   ERROR:  Column
"year"is of type integer but default expression is 
of type double precision           You will need to rewrite or cast the expression

For an original definition of:
    year         INTEGER      DEFAULT
date_part('year',CURRENT_TIMESTAMP)

Regards, Dave.