Search Postgresql Archives

Re: Dumb question about binary cursors and #ifdefHAVE_INT64_TIMESTAMP

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: Alvaro Herrera [mailto:alvherre@xxxxxxxxxxxxxx]
> Sent: Tuesday, December 11, 2007 1:11 PM
> To: Dann Corbit
> Cc: pgsql-hackers@xxxxxxxxxxxxxx; pgsql-general@xxxxxxxxxxxxxx
> Subject: Re:  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")


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux