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
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
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
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
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
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: