<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>> You could do the replication in the database (e.g. postgresql with <br><div>> slony). Then you do not need the supermaster feature.<br><br>That is something we are actually trying to avoid at all costs: we have Oracle doing regular notify and transfer requests on port 53.<br><br>We explicitly do not want to depend on any particular database features for DNS records' replication.<br><br>However, what we do want is synchronous multimaster replication, which gives one HA clustering. Last I checked, "slony" does not do that, unless there have been changes since.<br><br>My understanding of "slony" is that it is basically a standby replicator like Oracle DataGuard sans automatic failover. What we want is a grid of database nodes which all participate in UPDATE and DELETE statements, so that the load is spread across the entire cluster, and nodes may fail arbitrarily but the database is still up and running without skipping a single transaction.<br><br>Now, there have been patches that a few guys from Japan have done to PostgreSQL itself which make it have synchronous multimaster replication, essentially enabling HA clustering with PostgreSQL, but as our resources are limited, we haven't gotten to that yet.<br></div> </div></body>
</html>