| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | "Thomas H(dot)" <me(at)alternize(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY" |
| Date: | 2007-11-18 15:56:46 |
| Message-ID: | 1195401406.5848.10.camel@mha-laptop.clients.sollentuna.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2007-11-18 15:57:38 | Re: BUG #3750: Invalid frontend message type 112 |
| Previous Message | Thomas H. | 2007-11-17 20:13:28 | Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY" |