Re: Reading timestamp values from Datums gives garbage values - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: Reading timestamp values from Datums gives garbage values
Date
Msg-id 703542da-87ec-48ca-8392-bf6f79ee6deb@enterprisedb.com
Whole thread Raw
In response to Reading timestamp values from Datums gives garbage values  (Sushrut Shivaswamy <sushrut.shivaswamy@gmail.com>)
Responses Re: Reading timestamp values from Datums gives garbage values
Re: Reading timestamp values from Datums gives garbage values
List pgsql-hackers
On 5/20/24 16:37, Sushrut Shivaswamy wrote:
> Hey,
> 
> I'm trying to read a timestamp column as EPOCH.
> My query is as follows.
> ```
> SELECT EXTRACT(EPOCH FROM timestamp_column) FROM table;
> 
> column
> ----------
> 
> 1716213097.86486
> ```
> When running in the console this query gives valid epoch output which
> appears to be of type double.
> 
> When trying to read the query response from the Datum, I get garbage values.
> I've tried various types and none of them read the correct value.
> ```
> 
> Datum current_timestamp = SPI_getbinval(SPI_tuptable->vals[i],
> SPI_tuptable->tupdesc, 5, &isnull);
> 
> double current_time = DatumGetFloat8(current_timestamp); // prints 0
> 
> int64 time = DatumGetUint64(current_timestamp); // prints 5293917674
> ```
> 

TimestampTz is int64, so using DatumGetInt64 is probably the simplest
solution. And it's the number of microseconds, so X/1e6 should give you
the epoch.

regards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Speed up clean meson builds by ~25%
Next
From: Robert Haas
Date:
Subject: Re: Speed up clean meson builds by ~25%