<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Qlik Sense: Postgres in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Postgres/m-p/1413742#M10992</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello friends - I was wondering if you anyone has opinions on how to best setup postgres as a standalone service along with the Qlik Sense environment.&amp;nbsp; We currently have this setup in production but are running into issues while upgrading QS 3.2 SR1 to the September release.&amp;nbsp; Our postgres service runs on two different nodes using windows clustering/shared storage.&amp;nbsp; QS setup is a mutli-node environment with shared persistence.&amp;nbsp; How are most companies tackling the issue of not having postgres as a single point of failure?&amp;nbsp; Any thoughts on this would be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pranav&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 23 Oct 2017 13:43:34 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2017-10-23T13:43:34Z</dc:date>
    <item>
      <title>Qlik Sense: Postgres</title>
      <link>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Postgres/m-p/1413742#M10992</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello friends - I was wondering if you anyone has opinions on how to best setup postgres as a standalone service along with the Qlik Sense environment.&amp;nbsp; We currently have this setup in production but are running into issues while upgrading QS 3.2 SR1 to the September release.&amp;nbsp; Our postgres service runs on two different nodes using windows clustering/shared storage.&amp;nbsp; QS setup is a mutli-node environment with shared persistence.&amp;nbsp; How are most companies tackling the issue of not having postgres as a single point of failure?&amp;nbsp; Any thoughts on this would be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pranav&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Oct 2017 13:43:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Postgres/m-p/1413742#M10992</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-10-23T13:43:34Z</dc:date>
    </item>
  </channel>
</rss>

