<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: One Of PostgreSQL&#8217;s Biggest Weaknesses</title>
	<link>http://blog.charcoalphile.com/2008/04/13/one-of-postgresqls-biggest-weaknesses/</link>
	<description>On Databases, Recovery, Tech</description>
	<pubDate>Mon, 06 Sep 2010 10:04:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: admin</title>
		<link>http://blog.charcoalphile.com/2008/04/13/one-of-postgresqls-biggest-weaknesses/#comment-344</link>
		<author>admin</author>
		<pubDate>Wed, 16 Apr 2008 19:50:00 +0000</pubDate>
		<guid>http://blog.charcoalphile.com/2008/04/13/one-of-postgresqls-biggest-weaknesses/#comment-344</guid>
		<description>Joseph,

You can use tools such as pgAdmin3 to setup Slony-I replication, fairly easily, but Slony-I has several weaknesses that make it unsuitable for many situations. You would still have to setup failover manually, as well.
</description>
		<content:encoded><![CDATA[<p>Joseph,</p>
<p>You can use tools such as pgAdmin3 to setup Slony-I replication, fairly easily, but Slony-I has several weaknesses that make it unsuitable for many situations. You would still have to setup failover manually, as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Scott</title>
		<link>http://blog.charcoalphile.com/2008/04/13/one-of-postgresqls-biggest-weaknesses/#comment-343</link>
		<author>Joseph Scott</author>
		<pubDate>Wed, 16 Apr 2008 19:45:51 +0000</pubDate>
		<guid>http://blog.charcoalphile.com/2008/04/13/one-of-postgresqls-biggest-weaknesses/#comment-343</guid>
		<description>Agreed, having a reasonable &#38; easy way to setup replication in PostgreSQL would go a long way towards making it more useful.</description>
		<content:encoded><![CDATA[<p>Agreed, having a reasonable &amp; easy way to setup replication in PostgreSQL would go a long way towards making it more useful.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
