<?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>Open Enterprise: The PostgreSQL Open Source Database Blog from EnterpriseDB &#187; pg_migrator 8.4</title>
	<atom:link href="http://blogs.enterprisedb.com/tag/pg_migrator-84/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.enterprisedb.com</link>
	<description>Commentary, tutorials, and announcements surrounding PostgreSQL, Postgres Plus, and open source.</description>
	<lastBuildDate>Tue, 24 Aug 2010 16:21:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Development Developments</title>
		<link>http://blogs.enterprisedb.com/2009/07/26/development-developments/</link>
		<comments>http://blogs.enterprisedb.com/2009/07/26/development-developments/#comments</comments>
		<pubDate>Mon, 27 Jul 2009 00:15:08 +0000</pubDate>
		<dc:creator>Bruce Momjian</dc:creator>
				<category><![CDATA[postgresql]]></category>
		<category><![CDATA[pg_migrator 8.4]]></category>
		<category><![CDATA[postgresql development]]></category>
		<category><![CDATA[robert haas]]></category>

		<guid isPermaLink="false">http://blogs.enterprisedb.com/?p=71</guid>
		<description><![CDATA[You might have noticed that patch processing has changed in recent Postgres development cycles. For 8.4 development, we used wiki-based commit fests with the goal of getting more people involved in patch approval, and speeding patch application.  For 8.5, Robert Haas has written a patch management application that automates much of the manual adjustment [...]]]></description>
			<content:encoded><![CDATA[<p>You might have noticed that patch processing has changed in recent Postgres development cycles. For 8.4 development, we used wiki-based <a style="text-decoration: none;" href="http://wiki.postgresql.org/wiki/PostgreSQL_8.4_Development_Plan">commit fests</a> with the goal of getting more people involved in patch approval, and speeding patch application.  For 8.5, Robert Haas has written a patch management <a style="text-decoration: underline;" href="https://commitfest.postgresql.org/action/commitfest_view/inprogress">application</a> that automates much of the manual adjustment required when using the wiki;  many thanks to him.</p>
<p>I used to manage most of the independent patches myself, but patch volume now far exceeds my ability to process them. Patch application is now managed by a capable team, and my involvement is less critical. This will allow me to get involved in other projects, such as <a style="text-decoration: none;" href="http://pgfoundry.org/projects/pg-migrator/">pg_migrator</a>, which I just <a style="text-decoration: none;" href="http://momjian.us/main/blogs/pgblog.html#July_20_2009">finished</a>.</p>
<a href='http://blogs.enterprisedb.com/2009/07/26/development-developments/' class='retweet vert' >Development Developments</a>]]></content:encoded>
			<wfw:commentRss>http://blogs.enterprisedb.com/2009/07/26/development-developments/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Pg_Migrator 8.4.1 Released</title>
		<link>http://blogs.enterprisedb.com/2009/07/20/pg_migrator-841-released/</link>
		<comments>http://blogs.enterprisedb.com/2009/07/20/pg_migrator-841-released/#comments</comments>
		<pubDate>Mon, 20 Jul 2009 19:21:42 +0000</pubDate>
		<dc:creator>Bruce Momjian</dc:creator>
				<category><![CDATA[Technical Alerts]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[pg_migrator 8.4]]></category>

		<guid isPermaLink="false">http://blogs.enterprisedb.com/?p=65</guid>
		<description><![CDATA[I have released pg_migrator 8.4.1, which fixes all known bugs.
Pg_Migrator 8.4.1 Released]]></description>
			<content:encoded><![CDATA[<p>I have released <a style="text-decoration: none;" href="http://pgfoundry.org/projects/pg-migrator/">pg_migrator</a> 8.4.1, which fixes all known bugs.</p>
<a href='http://blogs.enterprisedb.com/2009/07/20/pg_migrator-841-released/' class='retweet vert' >Pg_Migrator 8.4.1 Released</a>]]></content:encoded>
			<wfw:commentRss>http://blogs.enterprisedb.com/2009/07/20/pg_migrator-841-released/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Setback for Pg_Migrator</title>
		<link>http://blogs.enterprisedb.com/2009/07/19/setback-for-pg_migrator/</link>
		<comments>http://blogs.enterprisedb.com/2009/07/19/setback-for-pg_migrator/#comments</comments>
		<pubDate>Sun, 19 Jul 2009 20:19:20 +0000</pubDate>
		<dc:creator>Bruce Momjian</dc:creator>
				<category><![CDATA[Technical Alerts]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[pg_migrator 8.4]]></category>

		<guid isPermaLink="false">http://blogs.enterprisedb.com/?p=63</guid>
		<description><![CDATA[This past week two bugs were found in pg_migrator:  one related to the handling of large objects, and a second related to migrating sequences. I have removed pg_migrator 8.4 from the web site, and posted an 8.4.1 Alpha 1 release with a clear mention of the two known bugs that exist. I hope to [...]]]></description>
			<content:encoded><![CDATA[<p>This past week two bugs were found in <a style="text-decoration: none;" href="http://pgfoundry.org/projects/pg-migrator/">pg_migrator</a>:  one related to the handling of <a style="text-decoration: underline;" href="http://archives.postgresql.org/pgsql-hackers/2009-07/msg00740.php">large objects</a>, and a second related to migrating <a style="text-decoration: underline;" href="http://archives.postgresql.org/pgsql-hackers/2009-07/msg00742.php">sequences</a>. I have removed pg_migrator 8.4 from the web site, and posted an 8.4.1 Alpha 1 release with a clear mention of the two known bugs that exist. I hope to have these bugs fixed in the next few weeks.</p>
<a href='http://blogs.enterprisedb.com/2009/07/19/setback-for-pg_migrator/' class='retweet vert' >Setback for Pg_Migrator</a>]]></content:encoded>
			<wfw:commentRss>http://blogs.enterprisedb.com/2009/07/19/setback-for-pg_migrator/feed/</wfw:commentRss>
		<slash:comments>21</slash:comments>
		</item>
		<item>
		<title>Pg_Migrator 8.4 Final Released Last Week</title>
		<link>http://blogs.enterprisedb.com/2009/07/13/pg_migrator-84-final-released-last-week/</link>
		<comments>http://blogs.enterprisedb.com/2009/07/13/pg_migrator-84-final-released-last-week/#comments</comments>
		<pubDate>Mon, 13 Jul 2009 14:18:09 +0000</pubDate>
		<dc:creator>Bruce Momjian</dc:creator>
				<category><![CDATA[Technical Alerts]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[pg_migrator 8.4]]></category>

		<guid isPermaLink="false">http://blogs.enterprisedb.com/?p=58</guid>
		<description><![CDATA[After a great amount of testing, pg_migrator 8.4 final was released last week. I have received some successful usage reports, and no bug reports so far, so it seems all the testing paid off. Thanks to the many testers that made pg_migrator 8.4 possible.
Pg_Migrator 8.4 Final Released Last Week]]></description>
			<content:encoded><![CDATA[<p>After a great amount of testing, <a style="text-decoration: underline;" href="http://pgfoundry.org/projects/pg-migrator/">pg_migrator</a> 8.4 final was released last week. I have received some successful usage reports, and no bug reports so far, so it seems all the testing paid off. Thanks to the many testers that made pg_migrator 8.4 possible.</p>
<a href='http://blogs.enterprisedb.com/2009/07/13/pg_migrator-84-final-released-last-week/' class='retweet vert' >Pg_Migrator 8.4 Final Released Last Week</a>]]></content:encoded>
			<wfw:commentRss>http://blogs.enterprisedb.com/2009/07/13/pg_migrator-84-final-released-last-week/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
	</channel>
</rss>
