@@ -252,11 +252,13 @@ protocol to make nodes agree on a serializable transactional order.
252252 </para>
253253
254254 <para>
255- <productname>PostgreSQL</> does not offer this type of replication,
256- though <productname>PostgreSQL</> two-phase commit (<xref
257- linkend="sql-prepare-transaction"> and <xref
258- linkend="sql-commit-prepared">)
259- can be used to implement this in application code or middleware.
255+ <productname>Postgres Pro Enterprise</productname> provides
256+ <filename>multimaster</filename> extension that implements this
257+ type of replication. Using <filename>multimaster</filename>, you
258+ can configure a synchronous shared-nothing cluster that provides
259+ Online Transaction Processing (<acronym>OLTP</acronym>) scalability
260+ for read transactions, as well as ensures high availability with
261+ automatic disaster recovery.
260262 </para>
261263 </listitem>
262264 </varlistentry>
@@ -307,7 +309,7 @@ protocol to make nodes agree on a serializable transactional order.
307309 <entry align="center">Slony</entry>
308310 <entry align="center">pgpool-II</entry>
309311 <entry align="center">Bucardo</entry>
310- <entry align="center"></entry>
312+ <entry align="center"><filename>multimaster</filename> extension of <productname>Postgres Pro Enterprise</productname>< /entry>
311313 </row>
312314
313315 <row>
