# \#postgres

**URL:** https://community.tulip.co/tag/postgres/267.md

[Latest](https://community.tulip.co/latest.md) · [Categories](https://community.tulip.co/categories.md) · [Tags](https://community.tulip.co/tags.md)

---

## [Update Postgres connector function to support the 'interval' data type](https://community.tulip.co/t/update-postgres-connector-function-to-support-the-interval-data-type/9947)

<div class="topic-metadata">

**Author:** [@Richard-SNN](https://community.tulip.co/u/Richard-SNN)\
**Replies:** 1\
**Last updated:** [December 1, 2023, 8:27pm UTC](https://community.tulip.co/t/update-postgres-connector-function-to-support-the-interval-data-type/9947 "2023-12-01T20:27:01Z")

</div>

I have a Postgres query (really TimescaleDB) that returns multiple intervals as a datatype. Unfortuantly to get the data into Tulip I have to use the EXTRACT('epoch' from \<...\>) method to convert it to an integer. This …
