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

From Thomas H.
Subject Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"
Date
Msg-id 473F4B68.1060002@alternize.com
Whole thread Raw
In response to Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"  (Magnus Hagander <magnus@hagander.net>)
List pgsql-bugs
tom lane wrote:
>> 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 ...

both versions are the official win32 builds from postgresl.org...

- thomas

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"
Next
From: Kris Jurka
Date:
Subject: Re: BUG #3751: Conversion error using PreparedStatement.setObject()