<?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>Data Warehouse Performance Tuning &#187; PostgreSQL</title>
	<atom:link href="http://www.atlogic.com/blog/index.php/category/postgresql/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.atlogic.com/blog</link>
	<description>Searching for profound knowledge</description>
	<lastBuildDate>Tue, 27 Jan 2009 16:02:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>MySQL vs. PostgreSQL for Data Warehouses that use Views</title>
		<link>http://www.atlogic.com/blog/index.php/2006/11/07/mysql-vs-postgresql-for-data-warehouses-that-use-views/</link>
		<comments>http://www.atlogic.com/blog/index.php/2006/11/07/mysql-vs-postgresql-for-data-warehouses-that-use-views/#comments</comments>
		<pubDate>Tue, 07 Nov 2006 19:25:55 +0000</pubDate>
		<dc:creator>Miguel Barrientos</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[PostgreSQL]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://www.atlogic.com/blog/index.php/2006/11/07/mysql-vs-postgresql-for-data-warehouses-that-use-views/</guid>
		<description><![CDATA[As part of the Netezza replacement project I&#8217;ve been working on, I ran a quick evaluation of MySQL 5.x. before testing PostgreSQL. I didn&#8217;t have time to conduct a thorough evaluation, but I quickly found out that MySQL does not handle queries ran against views very well. I ran some tests by creating simple views [...]]]></description>
			<content:encoded><![CDATA[<p>As part of the Netezza replacement project I&#8217;ve been working on, I ran a quick evaluation of MySQL 5.x. before testing PostgreSQL. I didn&#8217;t have time to conduct a thorough evaluation, but I quickly found out that MySQL does not handle queries ran against views very well. I ran some tests by creating simple views against some very large tables (40+ million rows). Running a query against the base table was many times faster than running the same query against a view which did not even contain a WHERE clause. I&#8217;ll need to do some additional research, but it seems that the implementation of views in MySQL lags far behind the PostgreSQL implementation. It&#8217;s obviously not very surprising, since support for views was added to MySQL only in version 5.0.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.atlogic.com/blog/index.php/2006/11/07/mysql-vs-postgresql-for-data-warehouses-that-use-views/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PostgreSQL Performance Checklist</title>
		<link>http://www.atlogic.com/blog/index.php/2006/11/07/postgresql-performance-checklist/</link>
		<comments>http://www.atlogic.com/blog/index.php/2006/11/07/postgresql-performance-checklist/#comments</comments>
		<pubDate>Tue, 07 Nov 2006 19:13:16 +0000</pubDate>
		<dc:creator>Miguel Barrientos</dc:creator>
				<category><![CDATA[PostgreSQL]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://www.atlogic.com/blog/index.php/2006/11/07/postgresql-performance-checklist/</guid>
		<description><![CDATA[I found some very valuable tips in the web site of an unpublished book: Power PostgreSQL by Josh Berkus and Joe Conway. If you are working with large data sets and complex queries, pay special attention to the section that discusses work_mem.
]]></description>
			<content:encoded><![CDATA[<p>I found some very valuable tips in the web site of an unpublished book: <a title="PostgreSQL Performance Checklist" href="http://www.powerpostgresql.com/PerfList/">Power PostgreSQL</a> by Josh Berkus and Joe Conway. If you are working with large data sets and complex queries, pay special attention to the section that discusses work_mem.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.atlogic.com/blog/index.php/2006/11/07/postgresql-performance-checklist/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tuning PostgreSQL for Data Warehousing</title>
		<link>http://www.atlogic.com/blog/index.php/2006/10/26/tuning-postgresql-for-data-warehousing/</link>
		<comments>http://www.atlogic.com/blog/index.php/2006/10/26/tuning-postgresql-for-data-warehousing/#comments</comments>
		<pubDate>Thu, 26 Oct 2006 18:15:37 +0000</pubDate>
		<dc:creator>Miguel Barrientos</dc:creator>
				<category><![CDATA[PostgreSQL]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://www.atlogic.com/blog/?p=30</guid>
		<description><![CDATA[I&#8217;m currently working in a project that will replace a Netezza database with PostgreSQL 8.1. Early test results have been very encouraging, even though I haven&#8217;t found much information online about how to best tune PostgreSQL when dealing with complex queries running against very large tables. I will share what I learned in future posts.
]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m currently working in a project that will replace a Netezza database with PostgreSQL 8.1. Early test results have been very encouraging, even though I haven&#8217;t found much information online about how to best tune PostgreSQL when dealing with complex queries running against very large tables. I will share what I learned in future posts.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.atlogic.com/blog/index.php/2006/10/26/tuning-postgresql-for-data-warehousing/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
