<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>2ndQuadrant &#187; Jaime&#8217;s PlanetPostgreSQL</title>
	<atom:link href="http://blog.2ndquadrant.com/jaimes-planetpostgresql/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.2ndquadrant.com</link>
	<description>PostgreSQL expertise from specialists with a source code level understanding of RDBMS</description>
	<lastBuildDate>Sun, 19 May 2013 09:09:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Managing useful clusters with repmgr</title>
		<link>http://blog.2ndquadrant.com/managing-useful-clusters-repmgr/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=managing-useful-clusters-repmgr</link>
		<comments>http://blog.2ndquadrant.com/managing-useful-clusters-repmgr/#comments</comments>
		<pubDate>Wed, 29 Aug 2012 22:22:46 +0000</pubDate>
		<dc:creator>Jaime Casanova</dc:creator>
				<category><![CDATA[Jaime's PlanetPostgreSQL]]></category>
		<category><![CDATA[clustering]]></category>
		<category><![CDATA[failover]]></category>
		<category><![CDATA[postgresql repmgr]]></category>
		<category><![CDATA[tools]]></category>

		<guid isPermaLink="false">http://blog.2ndquadrant.com/?p=343</guid>
		<description><![CDATA[To create a standby in PostgreSQL is relatively easy, and because of the hot standby feature, that...]]></description>
			<content:encoded><![CDATA[<p align="LEFT"><span style="color: #000000"><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">To create a standby in PostgreSQL is relatively easy</span></span></span><span style="color: #000000"><span style="font-family: 'Times New Roman', serif"><span style="font-size: small">,</span></span></span><span style="color: #000000"><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small"> and because of the hot standby feature</span></span></span><span style="font-family: 'Times New Roman', serif"><span style="font-size: small">,</span></span><span style="color: #000000"><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small"> that alone is certainly very useful.</span></span></span></p>
<p lang="en-US" align="LEFT"><span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">But creating a useful cluster that give</span></span></span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">s</span></span><span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small"> us real HA</span></span></span><span><span style="font-family: 'Times New Roman', serif"><span style="font-size: small">&#8230;</span></span></span><span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small"> that&#8217;s another story. The complexities added by failure detection, STONITH rules and choosing a new master could be overwhelming. But still, it is an important part of maintaining a healthy PostgreSQL environment.</span></span></span></p>
<p lang="en-US" align="LEFT"><span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">Repmgr 2.0 gives you the opportunity to configure a more </span></span></span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">streamlined</span></span><span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small"> failover process for when you need it.</span></span></span></p>
<p lang="en-US" align="LEFT"><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">Repmgr 2.0 was released</span></span><span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small"> as a beta</span></span></span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small"> about a month ago, and we incorporated many feature requests received from the community. If you requested something of the tool which didn’t make it into this release, keep on us, as we’ve been working hard to insure we a had release out prior to 9.2 launch.</span></span></p>
<p lang="en-US" align="LEFT"><span style="font-size: small;font-family: 'Lucida Grande', serif">For those of you familiar with our initial version, repmgr 2.0 contains some functionality updates to make the tool more useful.</span></p>
<p lang="en-US" align="LEFT"><span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">Because of the </span></span></span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">auto failover</span></span><span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small"> functionalit</span></span></span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">y</span></span><span style="font-family: 'Times New Roman', serif"><span style="font-size: small">,</span></span><span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">we</span></span></span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small"> no longer have the need for history logging</span></span><span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small"> to choose the best candidate to promote as new master</span></span></span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small"> saving precious IO bandwidth. The script accomplishes this by auto detecting which node is most up to date and failing over to that one. We also added a node_name in repl_nodes table, so we can identify servers better, because this name is used as application_name in the replica</span></span><span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">tion</span></span></span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small"> connection to the server</span></span><span style="font-family: 'Times New Roman', serif"><span style="font-size: small">,</span></span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small"> when we see pg_stat_replication we can better identify every connection</span></span><span style="font-family: 'Times New Roman', serif"><span style="font-size: small">.</span></span></p>
<p lang="en-US" align="LEFT"><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">Subsequent to that there is also CLUSTER SHOW command (thanks to our friends in Italy), allowing the user to query and see what nodes are part of </span></span><span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">our </span></span></span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">cluster</span></span><span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small"> if it&#8217;s working (we can connect to it) and its role on the cluster: primary, standby or witness</span></span></span><span style="font-family: 'Times New Roman', serif"><span style="font-size: small">.</span></span></p>
<p align="LEFT"><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">The CLUSTER_CLEANUP command (we heard from many users on this) is also important as it negates the task of manually cleaning up repl_monitor table, saving time and accidental deletion of a live node from the table.</span></span></p>
<p align="LEFT"><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">My personal favorite segment of the tool update is the autofailover. </span></span><span style="color: #000000"><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">It&#8217;s </span></span></span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">so flexible that we </span></span><span style="color: #000000"><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small">allow the user to supply a customized script</span></span></span><span style="font-family: 'Lucida Grande', serif"><span style="font-size: small"> to execute several commands at failover time. For example it could be combined with pgbouncer to make a simple failover setup that did not require root privileges. </span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.2ndquadrant.com/managing-useful-clusters-repmgr/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
	</channel>
</rss>
