From: | "Dann Corbit" <DCorbit(at)connx(dot)com> |
---|---|
To: | "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | <pgsql-hackers(at)postgresql(dot)org>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Dumb question about binary cursors and #ifdefHAVE_INT64_TIMESTAMP |
Date: | 2007-12-11 21:23:26 |
Message-ID: | D425483C2C5C9F49B5B7A41F8944154701000B1B@postal.corporate.connx.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
> -----Original Message-----
> From: Alvaro Herrera [mailto:alvherre(at)alvh(dot)no-ip(dot)org]
> Sent: Tuesday, December 11, 2007 1:11 PM
> To: Dann Corbit
> Cc: pgsql-hackers(at)postgresql(dot)org; pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] Dumb question about binary cursors and
> #ifdefHAVE_INT64_TIMESTAMP
>
> 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).
Tom's post clued me in.
It's:
show integer_datetimes;
Or (in my case):
PQparameterStatus(conn, "integer_datetimes")
From | Date | Subject | |
---|---|---|---|
Next Message | Ivan Sergio Borgonovo | 2007-12-11 21:25:44 | Re: top posting (was: Hijack!) |
Previous Message | Obe, Regina | 2007-12-11 21:21:14 | Re: Hijack! |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-12-11 21:31:17 | Re: VLDB Features |
Previous Message | Dann Corbit | 2007-12-11 21:18:34 | Re: Dumb question about binary cursors and #ifdefHAVE_INT64_TIMESTAMP |