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

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

"Thomas H." <me(at)alternize(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas H. 2007-11-17 20:13:28 Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"
Previous Message Thomas H. 2007-11-17 19:45:00 8.3b2: problem using "COPY ... TO/FROM .... BINARY"