| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | David De Maeyer <david(at)adnuvo(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: binary timestamp conversion |
| Date: | 2009-08-17 16:41:27 |
| Message-ID: | 20090817164127.GF4782@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
David De Maeyer wrote:
> I am now facing a puzzling challenge: converting binary timestamp
> data! If pgfsck did properly recover the timestamp data as a binary
> string, pgfsck will use a default timestamp, "1900-01-01 00:00:00",
> presumably because the date/time encoding varies from platform to
> platform.
There are two representations, one using 64 bit integers and the other
using floating point. Which one is your installation using depends on
compile-time settings.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-08-17 16:45:23 | Re: ERROR: XLogFlush: request AF/5703EDC8 is not satisfied --- flushed only to AF/50F15ABC |
| Previous Message | Greg Stark | 2009-08-17 16:35:23 | Re: ERROR: attempted to delete invisible tuple |