Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY" - Mailing list pgsql-bugs

From Tom Lane
Subject Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"
Date
Msg-id 19752.1195329103@sss.pgh.pa.us
Whole thread Raw
In response to 8.3b2: problem using "COPY ... TO/FROM .... BINARY"  ("Thomas H." <me@alternize.com>)
Responses Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"  ("Thomas H." <me@alternize.com>)
List pgsql-bugs
"Thomas H." <me@alternize.com> writes:
> i'm not sure it its really a bug - the manual specifies that COPY ...
> BINARY between different PGSQL versions might be problematic.

> nevertheless: i've imported several tables from 8.2.5 to 8.3b2 without
> any problems, until one table produced an error on a timestamp field:

I'll bet a nickel that you built one version with float timestamps and
the other with integer ...

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Thomas H."
Date:
Subject: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"
Next
From: "Thomas H."
Date:
Subject: Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"