<?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>Wetware &#187; pg_dump</title>
	<atom:link href="http://www.wetware.co.nz/tag/pg_dump/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wetware.co.nz</link>
	<description>Getting computers to do stuff so we don&#039;t have too</description>
	<lastBuildDate>Thu, 01 Sep 2011 09:25:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>PG_Dump PG_Restore</title>
		<link>http://www.wetware.co.nz/2009/09/pg_dump-pg_restore/</link>
		<comments>http://www.wetware.co.nz/2009/09/pg_dump-pg_restore/#comments</comments>
		<pubDate>Thu, 24 Sep 2009 22:21:33 +0000</pubDate>
		<dc:creator>Jordan Carter</dc:creator>
				<category><![CDATA[Server Config]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[pg_dump]]></category>
		<category><![CDATA[pg_restore]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>
		<category><![CDATA[remote server]]></category>

		<guid isPermaLink="false">http://www.wetware.co.nz/blog/?p=482</guid>
		<description><![CDATA[Dump a remote postgres database and restore it into a local postgres database.  This method dumps first into a local file, then restores into the database.  The reason for doing it this way over piping the data straight into the database locally is that if there is an error in the import you don&#8217;t have [...]]]></description>
		<wfw:commentRss>http://www.wetware.co.nz/2009/09/pg_dump-pg_restore/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Postgres pg_dump straight into another database for backup or development</title>
		<link>http://www.wetware.co.nz/2009/05/postgres-pg_dump-straight-into-another-database-for-backup-or-development/</link>
		<comments>http://www.wetware.co.nz/2009/05/postgres-pg_dump-straight-into-another-database-for-backup-or-development/#comments</comments>
		<pubDate>Tue, 12 May 2009 00:28:48 +0000</pubDate>
		<dc:creator>Jordan Carter</dc:creator>
				<category><![CDATA[Server Config]]></category>
		<category><![CDATA[database backup]]></category>
		<category><![CDATA[pg_dump]]></category>
		<category><![CDATA[psql]]></category>

		<guid isPermaLink="false">http://www.wetware.co.nz/blog/?p=216</guid>
		<description><![CDATA[I frequently use a dump of the live database data to test new migrations, new features. I used to pg_dump on the remote live server to a file, then scp it across to my local server, psql it back to life in a new database. I have wondered if it was possible to do it [...]]]></description>
		<wfw:commentRss>http://www.wetware.co.nz/2009/05/postgres-pg_dump-straight-into-another-database-for-backup-or-development/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

