# Adding TimescaleDB to Postgres

**URL:** <https://forum.inductiveautomation.com/t/adding-timescaledb-to-postgres/112750>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [December 10, 2025, 10:46pm UTC](https://forum.inductiveautomation.com/t/adding-timescaledb-to-postgres/112750 "2025-12-10T22:46:08Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Shea\_Molthen](https://avatars.discourse-cdn.com/v4/letter/s/c37758/32.png) [@Shea\_Molthen](https://forum.inductiveautomation.com/u/Shea_Molthen)\
**Post date:** [December 16, 2025, 2:23pm UTC](https://forum.inductiveautomation.com/t/adding-timescaledb-to-postgres/112750/3 "2025-12-16T14:23:50Z")

</div>

> [@michael.flagler](#):
>
> you

Thanks for the response. So even with multiple tables, I could still convert them to hypertables and Ignition would just query them separately? And then the future partitions will be all handled by Timescale?

Further, are there any other issues / things I should think about? I found this: [Problematic Historian Query with TimescaleDB - #8 by pascal.fragnoud](https://forum.inductiveautomation.com/t/problematic-historian-query-with-timescaledb/68760/8) and was wondering if Timescale still has this issue?

Thanks again!

---

_[View the full topic](https://forum.inductiveautomation.com/t/adding-timescaledb-to-postgres/112750)._