<?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 Re: Nuxeo with a fault-tolerant PostgreSQL configuration in Nuxeo Forum</title>
    <link>https://connect.hyland.com/t5/nuxeo-forum/nuxeo-with-a-fault-tolerant-postgresql-configuration/m-p/326772#M13773</link>
    <description>&lt;P&gt;We'd love to but the problem is that the hot standby is still read-only, which prevents even a transaction &lt;CODE&gt;BEGIN&lt;/CODE&gt; from being executed on it. As the Nuxeo framework is pluggable, we don't have any way of knowing for a given HTTP request if the whole work to be executed will be read-only w.r.t. the database, or if somewhere a listener will want to write data. So in all cases we have to start a transaction very early, which prevents a hot standby from being used.&lt;/P&gt;
&lt;P&gt;A way to improve this would be to have at the URL level some way of discriminating between requests that are going to be purely read-only and those who don't, but that's not something we have today.&lt;/P&gt;
&lt;P&gt;&lt;A href="http://postgresxc.wikia.com/wiki/Postgres-XC_Wiki"&gt;Postgres-XC&lt;/A&gt; may be a better bet, but we haven't tested it yet.&lt;/P&gt;</description>
    <pubDate>Tue, 16 Oct 2012 23:05:48 GMT</pubDate>
    <dc:creator>Florent_Guillau</dc:creator>
    <dc:date>2012-10-16T23:05:48Z</dc:date>
    <item>
      <title>Nuxeo with a fault-tolerant PostgreSQL configuration</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/nuxeo-with-a-fault-tolerant-postgresql-configuration/m-p/326771#M13772</link>
      <description>&lt;P&gt;With the recent release of PostgreSQL 9.2, repmgr 2.0-beta (http://www.postgresql.org/about/news/1411/), and JDBC4 Postgresql Driver Version 9.2-1000 (with basic failover support), does Nuxeo have plans to test and/or document a fault-tolerant Nuxeo/PostgreSQL configuration with master/hot-standby PostgreSQL servers and automatic failover.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Oct 2012 23:13:33 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/nuxeo-with-a-fault-tolerant-postgresql-configuration/m-p/326771#M13772</guid>
      <dc:creator>ron_1</dc:creator>
      <dc:date>2012-10-03T23:13:33Z</dc:date>
    </item>
    <item>
      <title>Re: Nuxeo with a fault-tolerant PostgreSQL configuration</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/nuxeo-with-a-fault-tolerant-postgresql-configuration/m-p/326772#M13773</link>
      <description>&lt;P&gt;We'd love to but the problem is that the hot standby is still read-only, which prevents even a transaction &lt;CODE&gt;BEGIN&lt;/CODE&gt; from being executed on it. As the Nuxeo framework is pluggable, we don't have any way of knowing for a given HTTP request if the whole work to be executed will be read-only w.r.t. the database, or if somewhere a listener will want to write data. So in all cases we have to start a transaction very early, which prevents a hot standby from being used.&lt;/P&gt;
&lt;P&gt;A way to improve this would be to have at the URL level some way of discriminating between requests that are going to be purely read-only and those who don't, but that's not something we have today.&lt;/P&gt;
&lt;P&gt;&lt;A href="http://postgresxc.wikia.com/wiki/Postgres-XC_Wiki"&gt;Postgres-XC&lt;/A&gt; may be a better bet, but we haven't tested it yet.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Oct 2012 23:05:48 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/nuxeo-with-a-fault-tolerant-postgresql-configuration/m-p/326772#M13773</guid>
      <dc:creator>Florent_Guillau</dc:creator>
      <dc:date>2012-10-16T23:05:48Z</dc:date>
    </item>
    <item>
      <title>Re: Nuxeo with a fault-tolerant PostgreSQL configuration</title>
      <link>https://connect.hyland.com/t5/nuxeo-forum/nuxeo-with-a-fault-tolerant-postgresql-configuration/m-p/326773#M13774</link>
      <description>&lt;P&gt;I was specifically inquiring about high-availability/failover as opposed to increased scalability by leveraging the hot-standby for queries.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Oct 2012 05:01:30 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/nuxeo-forum/nuxeo-with-a-fault-tolerant-postgresql-configuration/m-p/326773#M13774</guid>
      <dc:creator>ron_1</dc:creator>
      <dc:date>2012-10-18T05:01:30Z</dc:date>
    </item>
  </channel>
</rss>

