| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Dann Corbit <DCorbit(at)connx(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Dumb question about binary cursors and #ifdef HAVE_INT64_TIMESTAMP |
| Date: | 2007-12-11 21:11:15 |
| Message-ID: | 20071211211115.GM10710@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Dann Corbit wrote:
> 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?
SHOW integer_timestamp;
(actually, IIRC, this is one of the params that the server will send you
at session start).
--
Alvaro Herrera http://www.flickr.com/photos/alvherre/
"Y eso te lo doy firmado con mis lágrimas" (Fiebre del Loco)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2007-12-11 21:11:27 | Re: top posting |
| Previous Message | Scott Marlowe | 2007-12-11 21:07:42 | Re: top posting |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-12-11 21:15:46 | Re: Dumb question about binary cursors and #ifdef HAVE_INT64_TIMESTAMP |
| Previous Message | Hannu Krosing | 2007-12-11 21:08:01 | Re: VLDB Features |