<?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>Cybertec - The PostgreSQL Database Company &#187; Hans-Juergen Schoenig</title>
	<atom:link href="http://www.cybertec.at/category/hans-juergen-schoenig/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cybertec.at</link>
	<description>Alle Services, Support, Schulungen und Trainings rund um PostgreSQL Datenbanken und Linux</description>
	<lastBuildDate>Tue, 11 Jun 2013 08:18:42 +0000</lastBuildDate>
	<language>de-DE</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>PostgreSQL block sizes: Getting started &#8230;</title>
		<link>http://www.cybertec.at/postgresql-block-sizes-getting-started/</link>
		<comments>http://www.cybertec.at/postgresql-block-sizes-getting-started/#comments</comments>
		<pubDate>Tue, 11 Jun 2013 08:18:42 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Hans-Juergen Schoenig]]></category>

		<guid isPermaLink="false">http://www.cybertec.at/?p=2331</guid>
		<description><![CDATA[I have been wondering a while about the optimal block size in PostgreSQL. Usually the default value of 8kb has proven to be beneficial for most applications. However, after listening to some talk about MonetDB, I got interested in testing various workloads for different blocksizes – especially with blocksizes larger than PostgreSQL’s current maximum of [...]]]></description>
		<wfw:commentRss>http://www.cybertec.at/postgresql-block-sizes-getting-started/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Transactional DDLs – a message to non-PostgreSQL users</title>
		<link>http://www.cybertec.at/transactional-ddls-a-message-to-non-postgresql-users/</link>
		<comments>http://www.cybertec.at/transactional-ddls-a-message-to-non-postgresql-users/#comments</comments>
		<pubDate>Sat, 01 Jun 2013 09:51:05 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Hans-Juergen Schoenig]]></category>

		<guid isPermaLink="false">http://www.cybertec.at/?p=2324</guid>
		<description><![CDATA[Sometimes it is astonishing to see, which basic functionality commercial vendors are lacking. One of the things which strikes me most is the fact that many expensive relational database systems are simply not capable of handling transactional DDLs (such as CREATE TABLE, CREATE INDEX, and so on). How can you ever deploy software in a [...]]]></description>
		<wfw:commentRss>http://www.cybertec.at/transactional-ddls-a-message-to-non-postgresql-users/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Functions: The most widely ignored performance tweak</title>
		<link>http://www.cybertec.at/functions-the-most-widely-ignored-performance-tweak/</link>
		<comments>http://www.cybertec.at/functions-the-most-widely-ignored-performance-tweak/#comments</comments>
		<pubDate>Wed, 29 May 2013 09:50:07 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Hans-Juergen Schoenig]]></category>

		<guid isPermaLink="false">http://www.cybertec.at/?p=2309</guid>
		<description><![CDATA[It happens quite frequently that people complain about stored procedure performance in PostgreSQL. In many cases the reason for bad performance can be explained quite nicely when looking at the definition of a function. In general, a PostgreSQL function can be marked as follows: VOLATILE, STABLE, IMMUTABLE or [NOT] LEAKPROOF. What does this actually mean? [...]]]></description>
		<wfw:commentRss>http://www.cybertec.at/functions-the-most-widely-ignored-performance-tweak/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CREATE TABLE – the fancy way</title>
		<link>http://www.cybertec.at/create-table-the-fancy-way/</link>
		<comments>http://www.cybertec.at/create-table-the-fancy-way/#comments</comments>
		<pubDate>Sat, 25 May 2013 09:54:58 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Hans-Juergen Schoenig]]></category>

		<guid isPermaLink="false">http://www.cybertec.at/?p=2320</guid>
		<description><![CDATA[One tiny little feature many users of PostgreSQL have often forgotten is the ability to create similar tables. It happens quite frequently that you want to create a table, which is just like some other one. To achieve that most people will do &#8230; CREATE TABLE x AS SELECT &#8230; LIMIT 0; This works nicely, [...]]]></description>
		<wfw:commentRss>http://www.cybertec.at/create-table-the-fancy-way/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Kostal Pico to PostgreSQL</title>
		<link>http://www.cybertec.at/kostal-pico-to-postgresql/</link>
		<comments>http://www.cybertec.at/kostal-pico-to-postgresql/#comments</comments>
		<pubDate>Wed, 22 May 2013 10:10:57 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Hans-Juergen Schoenig]]></category>

		<guid isPermaLink="false">http://www.cybertec.at/?p=2303</guid>
		<description><![CDATA[Everybody needs a little toy to play with, so I thought: Why not buy a toy helping me to get rid of my energy bill? So, I ordered a 10.5 kwp photovoltaic system for my house. The system was shipped with a Kostal Pico inverted to make sure electricity can be used directly by the [...]]]></description>
		<wfw:commentRss>http://www.cybertec.at/kostal-pico-to-postgresql/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

 Served from: www.cybertec.at @ 2013-06-20 02:22:26 by W3 Total Cache -->