| From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
|---|---|
| To: | Steve Singer <ssinger(at)ca(dot)afilias(dot)info> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Johann 'Myrkraverk' Oskarsson" <johann(at)2ndquadrant(dot)com> |
| Subject: | Re: walprotocol.h vs frontends |
| Date: | 2011-08-15 16:33:12 |
| Message-ID: | CAEYLb_Un7naQUe3urCGjshTZBXRVdFBRiNOiB+5bsruy1FYL6Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 15 August 2011 16:56, Steve Singer <ssinger(at)ca(dot)afilias(dot)info> wrote:
> This would mean that anyone using the floating point timestamps today won't
> be able to use pg_upgrade to upgrade to whichever version we remove them
> from. 8.3 had float based timestamps as the default and I suspect many
> installations with the default 8.3 settings have been upgraded via
> pg_upgrade to 9.0 built the old timestamps representation.
Really? I find that slightly surprising, considering that a quick look
at master's timestamp.c suggests that the choice to use the in64
representation over the double representation is entirely a case of
compile time either/or. There is no apparent fall-back to the double
representation available to binaries built without
--disable-integer-datetimes.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-08-15 16:40:58 | Re: walprotocol.h vs frontends |
| Previous Message | Magnus Hagander | 2011-08-15 16:15:35 | Re: walprotocol.h vs frontends |