Dumb question about binary cursors and #ifdef HAVE_INT64_TIMESTAMP - Mailing list pgsql-hackers

From Dann Corbit
Subject Dumb question about binary cursors and #ifdef HAVE_INT64_TIMESTAMP
Date
Msg-id D425483C2C5C9F49B5B7A41F8944154701000B19@postal.corporate.connx.com
Whole thread Raw
Responses Re: [GENERAL] Dumb question about binary cursors and #ifdef HAVE_INT64_TIMESTAMP  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Re: [GENERAL] Dumb question about binary cursors and #ifdef HAVE_INT64_TIMESTAMP  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

If I create a binary cursor on a recent version of PostgreSQL, how can I tell if the timestamp data internally is an 8 byte double or an 8 byte integer?

I see an #ifdef that changes the code path to compute timestamps as one type or the other, but I do not know how to recognize the internal format of the type that will be returned in a binary cursor.

How can I do that?

 

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: psql \dFp's behavior
Next
From: Hannu Krosing
Date:
Subject: Re: VLDB Features