Re: [BUGS] 8.3b2: problem using COPY ... TO/FROM .... BINARY

2007-11-19 Thread Magnus Hagander
On Sun, 2007-11-18 at 20:38 -0500, Tom Lane wrote: Magnus Hagander [EMAIL PROTECTED] writes: On Sat, 2007-11-17 at 21:13 +0100, Thomas H. wrote: I'll bet a nickel that you built one version with float timestamps and the other with integer ... both versions are the official win32

Re: [BUGS] 8.3b2: problem using COPY ... TO/FROM .... BINARY

2007-11-18 Thread Magnus Hagander
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

Re: [BUGS] 8.3b2: problem using COPY ... TO/FROM .... BINARY

2007-11-18 Thread Tom Lane
Magnus Hagander [EMAIL PROTECTED] writes: On Sat, 2007-11-17 at 21:13 +0100, Thomas H. wrote: 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

[BUGS] 8.3b2: problem using COPY ... TO/FROM .... BINARY

2007-11-17 Thread Thomas H.
hi there 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: from

Re: [BUGS] 8.3b2: problem using COPY ... TO/FROM .... BINARY

2007-11-17 Thread Tom Lane
Thomas H. [EMAIL PROTECTED] 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

Re: [BUGS] 8.3b2: problem using COPY ... TO/FROM .... BINARY

2007-11-17 Thread Thomas H.
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: