Re: [GENERAL] Dumb question about binary cursors and #ifdef HAVE_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). -- Alvaro Herrera http://www.flickr.com/photos/alvherre/ "Y eso te lo doy firmado con mis lágrimas" (Fiebre del Loco) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [GENERAL] Dumb question about binary cursors and #ifdef HAVE_INT64_TIMESTAMP
"Dann Corbit" <[EMAIL PROTECTED]> writes: > 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? PQparameterStatus(conn, "integer_datetimes") regards, tom lane ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[GENERAL] Dumb question about binary cursors and #ifdef HAVE_INT64_TIMESTAMP
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?
