<?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; postgresql</title>
	<atom:link href="http://www.wetware.co.nz/tag/postgresql/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>ERROR: new encoding (UTF8) is incompatible with the encoding of the template database (SQL_ASCII)</title>
		<link>http://www.wetware.co.nz/2010/07/error-new-encoding-utf8-is-incompatible-with-the-encoding-of-the-template-database-sql_ascii/</link>
		<comments>http://www.wetware.co.nz/2010/07/error-new-encoding-utf8-is-incompatible-with-the-encoding-of-the-template-database-sql_ascii/#comments</comments>
		<pubDate>Tue, 27 Jul 2010 00:11:53 +0000</pubDate>
		<dc:creator>Jordan Carter</dc:creator>
				<category><![CDATA[Server Config]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[utf8]]></category>

		<guid isPermaLink="false">http://www.wetware.co.nz/blog/?p=754</guid>
		<description><![CDATA[createdb: database creation failed: ERROR:  new encoding (UTF8) is incompatible with the encoding of the template database (SQL_ASCII) HINT:  Use the same encoding as in the template database, or use template0 as template. createdb: database creation failed: ERROR:  new encoding (UTF8) is incompatible with the encoding of the template database (SQL_ASCII)HINT:  Use the same encoding [...]]]></description>
		<wfw:commentRss>http://www.wetware.co.nz/2010/07/error-new-encoding-utf8-is-incompatible-with-the-encoding-of-the-template-database-sql_ascii/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>PostGIS psqlostgis ERROR could not load library /usr/lib/postgresql/8.4/lib/postgis-1.5.so</title>
		<link>http://www.wetware.co.nz/2010/03/postgis-psqlostgis-error-could-not-load-library-usrlibpostgresql8-4libpostgis-1-5-so/</link>
		<comments>http://www.wetware.co.nz/2010/03/postgis-psqlostgis-error-could-not-load-library-usrlibpostgresql8-4libpostgis-1-5-so/#comments</comments>
		<pubDate>Wed, 10 Mar 2010 00:44:57 +0000</pubDate>
		<dc:creator>Jordan Carter</dc:creator>
				<category><![CDATA[Ruby on Rails]]></category>
		<category><![CDATA[Server Config]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[ldconfig]]></category>
		<category><![CDATA[PostGIS]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[problem]]></category>

		<guid isPermaLink="false">http://www.wetware.co.nz/blog/?p=656</guid>
		<description><![CDATA[Trying to install PostGIS and you can&#8217;t get past this error? psqlostgis.sql:57: NOTICE:  type &#8220;spheroid&#8221; is not yet defined DETAIL:  Creating a shell type definition. psqlostgis.sql:57: ERROR:  could not load library &#8220;/usr/lib/postgresql/8.4/lib/postgis-1.5.so&#8221;: /usr/lib/postgresql/8.4/lib/postgis-1.5.so: undefined symbol: GEOSHausdorffDistance psqlostgis.sql:63: ERROR:  current transaction is aborted, commands ignored until end of transaction block psqlostgis.sql:68: ERROR:  current transaction is aborted, [...]]]></description>
		<wfw:commentRss>http://www.wetware.co.nz/2010/03/postgis-psqlostgis-error-could-not-load-library-usrlibpostgresql8-4libpostgis-1-5-so/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<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 vs MySQL</title>
		<link>http://www.wetware.co.nz/2009/06/postgres-vs-mysql/</link>
		<comments>http://www.wetware.co.nz/2009/06/postgres-vs-mysql/#comments</comments>
		<pubDate>Sat, 13 Jun 2009 11:29:08 +0000</pubDate>
		<dc:creator>Jordan Carter</dc:creator>
				<category><![CDATA[Server Config]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.wetware.co.nz/blog/?p=368</guid>
		<description><![CDATA[or I have used both MySQL and Postgres and if I was starting a project right now I would probably use Postgres. I have read the wikivs MySQL vs Postgres and there is a lot in there that I understand and a lot that I don&#8217;t. What I like about Postgres is that it uses [...]]]></description>
		<wfw:commentRss>http://www.wetware.co.nz/2009/06/postgres-vs-mysql/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Rails Migration Data Types &#8211; MySql &#8211; Postgresql &#8211; SQLite</title>
		<link>http://www.wetware.co.nz/2009/04/rails-migration-data-types-mysql-postgresql-sqlite/</link>
		<comments>http://www.wetware.co.nz/2009/04/rails-migration-data-types-mysql-postgresql-sqlite/#comments</comments>
		<pubDate>Sun, 19 Apr 2009 02:39:18 +0000</pubDate>
		<dc:creator>Jordan Carter</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[migrations]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[sqlite]]></category>

		<guid isPermaLink="false">http://www.wetware.co.nz/blog/?p=210</guid>
		<description><![CDATA[Rails mysql postgresql sqlite :binary blob bytea blob :boolean tinyint(1) boolean boolean :date date date date :datetime datetime timestamp datetime :decimal decimal decimal decimal :float float float float :integer int(11) integer integer :string varchar(255) * varchar(255) :text text text text :time time time datetime :timestamp datetime timestamp datetime]]></description>
		<wfw:commentRss>http://www.wetware.co.nz/2009/04/rails-migration-data-types-mysql-postgresql-sqlite/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

