Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY" - Mailing list pgsql-bugs

From Magnus Hagander
Subject Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"
Date
Msg-id 1195491690.7785.1.camel@mha-laptop.clients.sollentuna.se
Whole thread Raw
In response to Re: 8.3b2: problem using "COPY ... TO/FROM .... BINARY"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Sun, 2007-11-18 at 20:38 -0500, Tom Lane wrote:
> Magnus Hagander <magnus@hagander.net> 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 usual :-)
>
> > 8.3 is built with integer timestamps, 8.2 and earlier with float
> > timestamps.
>
> Hmm, is that documented as a version discrepancy for the Win32 builds?
>
> IIRC we had rough consensus for switching the default setting to integer
> timestamps in 8.4.  Perhaps it would be better for the Win32 build to
> wait till 8.4 before switching, for consistency with other platforms.

The switch is in that it's the default on the MSVC build. So two
different decisions (making that the default on MSVC, and making the
MSVC build the default) together made that third.

I'm fine dropping the default on MSVC until 8.4, if it's going to happen
then. The downside then is that people won't be able to upgrade to the
next beta without initdb, right? Which isn't too good, but it's better
to make such a change during beta than to have to do it during
release...

//Magnus

pgsql-bugs by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: BUG #3758: Postmaster Service
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #3760: Comment on restore database