Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"

From: "Thomas H(dot)" <me(at)alternize(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"
Date: 2007-11-17 20:13:28
Message-ID: 473F4B68.1060002@alternize.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Magnus Hagander 2007-11-18 15:56:46 Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"
Previous Message Tom Lane 2007-11-17 19:51:43 Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"