<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Timescale DB VS Postgres]]></title><description><![CDATA[<p dir="auto">Has any one done any comparison of the two ?   When would one be recommend over the other.  I have noticed at times with Timescale I often get disconnects from nxmc  when im doing a lot at once.  I have never had these issues with mysql or postgres.</p>
<p dir="auto">Thanks,</p>
<p dir="auto">Gary</p>
]]></description><link>https://forum.netxms.org/topic/6559/timescale-db-vs-postgres</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 09:23:20 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/6559.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 04 Jun 2020 15:31:16 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Timescale DB VS Postgres on Mon, 08 Jun 2020 21:48:17 GMT]]></title><description><![CDATA[<p dir="auto">With postgres or mysql there's a problem of housekeeping - deleting old datapoints when storage time elapses. This process may create big load on the database, especially if it's big.<br />
For timescale deletion is very optimal - a whole chunk of data for one day is deleted. There are a few sets of chunks - one for "Default" retention time and a few other sets &lt;7 days, 7..30, 30..90, 90..180, &gt;180 days. But the trick is that it's not possible to delete a daily chunk, if it contains data for at least one DCI that retention time has not elapsed yet. As the result, timescale database might take more storage space.<br />
Currently there's an issue when changing DCI retention time - <a href="https://track.radensolutions.com/issue/NX-1795" rel="nofollow ugc">https://track.radensolutions.com/issue/NX-1795</a></p>
<p dir="auto">Can you give more details, what exactly you are doing in nxmc when you get disconnected? Does it replicates reliably, or randomly?</p>
]]></description><link>https://forum.netxms.org/post/28026</link><guid isPermaLink="true">https://forum.netxms.org/post/28026</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Mon, 08 Jun 2020 21:48:17 GMT</pubDate></item><item><title><![CDATA[Reply to Timescale DB VS Postgres on Fri, 05 Jun 2020 08:53:42 GMT]]></title><description><![CDATA[<p dir="auto"><a href="https://blog.timescale.com/blog/timescaledb-vs-6a696248104e/" rel="nofollow ugc">https://blog.timescale.com/blog/timescaledb-vs-6a696248104e/</a></p>
<p dir="auto"><a href="https://docs.timescale.com/latest/introduction/timescaledb-vs-postgres" rel="nofollow ugc">https://docs.timescale.com/latest/introduction/timescaledb-vs-postgres</a></p>
]]></description><link>https://forum.netxms.org/post/28016</link><guid isPermaLink="true">https://forum.netxms.org/post/28016</guid><dc:creator><![CDATA[Woody]]></dc:creator><pubDate>Fri, 05 Jun 2020 08:53:42 GMT</pubDate></item></channel></rss>