| From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | 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 14:00:55 |
| Message-ID: | CAEYLb_X=FaWnu3tYt6WC0hRnHc0O8vZV9P6OH7vZ-GtFfaiLVA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 15 August 2011 12:22, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> The basic reason for this is that we're putting TimestampTz fields in
> the protocol. This also means that the protocol actually changes
> definition depending on if the server is compiled with integer or
> float timestamps.
Without commenting on what should be done in your specific case, I
wonder whether it's time to fully retire the deprecated double
representation of timestamps. Is anyone actually expected to rely on
their availability when 9.2 is released? This also caused difficulties
for Johann Oskarsson recently, during work on PL/Java.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-08-15 14:20:34 | Re: walprotocol.h vs frontends |
| Previous Message | Robert Haas | 2011-08-15 13:42:05 | Re: VACUUM FULL versus TOAST |