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

From Magnus Hagander
Subject Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"
Date
Msg-id 1195401406.5848.10.camel@mha-laptop.clients.sollentuna.se
Whole thread Raw
In response to Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"  ("Thomas H." <me@alternize.com>)
Responses Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Sat, 2007-11-17 at 21:13 +0100, Thomas H. wrote:
> 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...

That means Tom is right, as usual :-)

8.3 is built with integer timestamps, 8.2 and earlier with float
timestamps.

//Magnus

pgsql-bugs by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: BUG #3750: Invalid frontend message type 112
Next
From: Tom Lane
Date:
Subject: Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"