<?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>select * from depesz; &#187; postgresql</title>
	<atom:link href="http://www.depesz.com/index.php/tag/postgresql/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.depesz.com</link>
	<description></description>
	<lastBuildDate>Fri, 03 Feb 2012 14:27: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>Waiting for 9.2 &#8211; pg_basebackup from slave</title>
		<link>http://www.depesz.com/index.php/2012/02/03/waiting-for-9-2-pg_basebackup-from-slave/</link>
		<comments>http://www.depesz.com/index.php/2012/02/03/waiting-for-9-2-pg_basebackup-from-slave/#comments</comments>
		<pubDate>Fri, 03 Feb 2012 14:08:48 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[omnipitr]]></category>
		<category><![CDATA[pg92]]></category>
		<category><![CDATA[pg_basebackup]]></category>
		<category><![CDATA[pitr]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[replication]]></category>
		<category><![CDATA[slave]]></category>
		<category><![CDATA[wal]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2399</guid>
		<description><![CDATA[On 25th of January, Simon Riggs committed patch: Allow pg_basebackup from standby node with safety checking. Base backup follows recommended procedure, plus goes to great lengths to ensure that partial page writes are avoided. &#160; Jun Ishizuka and Fujii Masao, with minor modifications In PostgreSQL 9.1 we got pg_basebackup &#8211; it is a tool to [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2012/02/03/waiting-for-9-2-pg_basebackup-from-slave/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.2 &#8211; Trigger Depth</title>
		<link>http://www.depesz.com/index.php/2012/02/01/waiting-for-9-2-trigger-depth/</link>
		<comments>http://www.depesz.com/index.php/2012/02/01/waiting-for-9-2-trigger-depth/#comments</comments>
		<pubDate>Wed, 01 Feb 2012 17:36:50 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[depth]]></category>
		<category><![CDATA[pg92]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[trigger]]></category>
		<category><![CDATA[triggers]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2396</guid>
		<description><![CDATA[On 25th of January, Alvaro Herrera committed patch: Add pg_trigger_depth() function &#160; This reports the depth level of triggers currently in execution, or zero if not called from inside a trigger. &#160; No catversion bump in this patch, but you have to initdb if you want access to the new function. &#160; Author: Kevin Grittner [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2012/02/01/waiting-for-9-2-trigger-depth/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.2 &#8211; ALTER IF EXISTS</title>
		<link>http://www.depesz.com/index.php/2012/02/01/waiting-for-9-2-alter-if-exists/</link>
		<comments>http://www.depesz.com/index.php/2012/02/01/waiting-for-9-2-alter-if-exists/#comments</comments>
		<pubDate>Wed, 01 Feb 2012 13:14:11 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[alter]]></category>
		<category><![CDATA[conditional]]></category>
		<category><![CDATA[ddl]]></category>
		<category><![CDATA[if exists]]></category>
		<category><![CDATA[pg92]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2393</guid>
		<description><![CDATA[On 23th of January, Simon Riggs committed patch: ALTER &#60;thing&#62; [IF EXISTS] ... allows silent DDL if required, e.g. ALTER FOREIGN TABLE IF EXISTS foo RENAME TO bar &#160; Pavel Stehule This adds important capability &#8211; change object of it exists, and not raise exception if it doesn&#8217;t. Conditional DDL was always big point on [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2012/02/01/waiting-for-9-2-alter-if-exists/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Change in anonymization of plans on explain.depesz.com</title>
		<link>http://www.depesz.com/index.php/2012/01/31/change-in-anonmymization-of-plans-on-explain-depesz-com/</link>
		<comments>http://www.depesz.com/index.php/2012/01/31/change-in-anonmymization-of-plans-on-explain-depesz-com/#comments</comments>
		<pubDate>Tue, 31 Jan 2012 12:10:56 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[anonymization]]></category>
		<category><![CDATA[explain.depesz.com]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[stats]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2382</guid>
		<description><![CDATA[As you perhaps know, explain.depesz.com has anonymization feature. Couple of days ago Filip contacted me and sent a patch that stopped anonymization of typecasts. I thought about the patch, and what it achieves, changed it&#8217;s internals, but kept the effect. And today, it got released. Normal plan looks like this. But you might want to [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2012/01/31/change-in-anonmymization-of-plans-on-explain-depesz-com/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Some new tools for PostgreSQL or around PostgreSQL</title>
		<link>http://www.depesz.com/index.php/2012/01/23/some-new-tools-for-postgresql-or-around-postgresql/</link>
		<comments>http://www.depesz.com/index.php/2012/01/23/some-new-tools-for-postgresql-or-around-postgresql/#comments</comments>
		<pubDate>Mon, 23 Jan 2012 10:31:41 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[fast dump]]></category>
		<category><![CDATA[fast restore]]></category>
		<category><![CDATA[omniti]]></category>
		<category><![CDATA[pg.grep]]></category>
		<category><![CDATA[pg.logs.tail]]></category>
		<category><![CDATA[pgtreats]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[system_monitoring]]></category>
		<category><![CDATA[tools]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2366</guid>
		<description><![CDATA[During last months I wrote some tools to help me with my daily duties. I&#8217;d like to let you know you about them, as you might find them useful. So, here we go: pg.logs.tail Available from OmniTI SVN. It&#8217;s a smarter &#8220;tail -f&#8221; for PostgreSQL logs. Smarter in a way, that it knows that PostgreSQL [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2012/01/23/some-new-tools-for-postgresql-or-around-postgresql/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.2 &#8211; split of current_query in pg_stat_activity</title>
		<link>http://www.depesz.com/index.php/2012/01/23/waiting-for-9-2-split-of-current_query-in-pg_stat_activity/</link>
		<comments>http://www.depesz.com/index.php/2012/01/23/waiting-for-9-2-split-of-current_query-in-pg_stat_activity/#comments</comments>
		<pubDate>Sun, 22 Jan 2012 23:14:57 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[current_query]]></category>
		<category><![CDATA[idle in transaction]]></category>
		<category><![CDATA[iit]]></category>
		<category><![CDATA[pg92]]></category>
		<category><![CDATA[pg_stat_activity]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[state]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2364</guid>
		<description><![CDATA[On 19t of January, Magnus Hagander committed patch: Separate state from query string in pg_stat_activity &#160; This separates the state (running/idle/idleintransaction etc) into it's own field (&#34;state&#34;), and leaves the query field containing just query text. &#160; The query text will now mean &#34;current query&#34; when a query is running and &#34;last query&#34; in other [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2012/01/23/waiting-for-9-2-split-of-current_query-in-pg_stat_activity/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.2 &#8211; NULLS from pg_*_size() functions</title>
		<link>http://www.depesz.com/index.php/2012/01/22/waiting-for-9-2-nulls-from-pg__size-functions/</link>
		<comments>http://www.depesz.com/index.php/2012/01/22/waiting-for-9-2-nulls-from-pg__size-functions/#comments</comments>
		<pubDate>Sun, 22 Jan 2012 15:51:23 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[exception]]></category>
		<category><![CDATA[pg92]]></category>
		<category><![CDATA[pg_relation_size]]></category>
		<category><![CDATA[pg_stat_user_functions]]></category>
		<category><![CDATA[pg_table_size]]></category>
		<category><![CDATA[pg_total_relation_size]]></category>
		<category><![CDATA[plpgsql]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2361</guid>
		<description><![CDATA[On 19t of January, Heikki Linnakangas committed patch: Make pg_relation_size() and friends return NULL if the object doesn't exist. &#160; That avoids errors when the functions are used in queries like &#34;SELECT pg_relation_size(oid) FROM pg_class&#34;, and a table is dropped concurrently. &#160; Phil Sorber This patch on its own is not very visible, but it [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2012/01/22/waiting-for-9-2-nulls-from-pg__size-functions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OmniPITR 0.3.0</title>
		<link>http://www.depesz.com/index.php/2012/01/04/omnipitr-0-3-0/</link>
		<comments>http://www.depesz.com/index.php/2012/01/04/omnipitr-0-3-0/#comments</comments>
		<pubDate>Wed, 04 Jan 2012 20:44:42 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[announcements]]></category>
		<category><![CDATA[omnipitr]]></category>
		<category><![CDATA[omniti]]></category>
		<category><![CDATA[perl]]></category>
		<category><![CDATA[pitr]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[replication]]></category>
		<category><![CDATA[wal]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2355</guid>
		<description><![CDATA[Just released version 0.3.0 of our tool for handling WAL based replication in PostgreSQL &#8211; OmniPITR. Version jump is related to addition of another tool &#8211; omnipitr-synch. This tool is used to copy PostgreSQL data dir (including all tablespaces of course) to remote location(s). While this process is usually simple (call pg_start_backup(), transfer data, call [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2012/01/04/omnipitr-0-3-0/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tips N&#8217; Tricks &#8211; getting sizes of relations without locks</title>
		<link>http://www.depesz.com/index.php/2011/12/20/tips-n-tricks-getting-sizes-of-relations-without-locks/</link>
		<comments>http://www.depesz.com/index.php/2011/12/20/tips-n-tricks-getting-sizes-of-relations-without-locks/#comments</comments>
		<pubDate>Tue, 20 Dec 2011 16:23:02 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[locks]]></category>
		<category><![CDATA[pg_relation_size]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[size]]></category>
		<category><![CDATA[tnt]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2353</guid>
		<description><![CDATA[If you have production DB servers, chances are you&#8217;re running variant of these queries: SELECT SUM&#40;pg_relation_size&#40;oid&#41;&#41; FROM pg_class WHERE relkind = 'i' SELECT SUM&#40;pg_relation_size&#40;oid&#41;&#41; FROM pg_class WHERE relkind = 'r' To get summarized size of tables and/or indexes in your database (for example for graphing purposes). This (getting pg_relation_size for rows in pg_class) has one [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/12/20/tips-n-tricks-getting-sizes-of-relations-without-locks/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>r/trees ( recursive trees, what did you think about? )</title>
		<link>http://www.depesz.com/index.php/2011/12/16/rtrees-recursive-trees-what-did-you-think-about/</link>
		<comments>http://www.depesz.com/index.php/2011/12/16/rtrees-recursive-trees-what-did-you-think-about/#comments</comments>
		<pubDate>Fri, 16 Dec 2011 13:39:14 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[cte]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[recursive]]></category>
		<category><![CDATA[tree]]></category>
		<category><![CDATA[with recursive]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2348</guid>
		<description><![CDATA[I got asked on irc to show some examples how to use recursive CTE. Apparently my previous post wasn&#8217;t good enough I think that most of the users will use recursive cte to deal with trees I decided to show how to use it, even though it&#8217;s not my favorite approach to dealing with trees [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/12/16/rtrees-recursive-trees-what-did-you-think-about/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.2 &#8211; excluding data of table from dump</title>
		<link>http://www.depesz.com/index.php/2011/12/15/waiting-for-9-2-excluding-data-of-table-from-dump/</link>
		<comments>http://www.depesz.com/index.php/2011/12/15/waiting-for-9-2-excluding-data-of-table-from-dump/#comments</comments>
		<pubDate>Thu, 15 Dec 2011 13:24:50 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[data]]></category>
		<category><![CDATA[exclude]]></category>
		<category><![CDATA[pg92]]></category>
		<category><![CDATA[pg_dump]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[table]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2344</guid>
		<description><![CDATA[On 14h of December, Andrew Dunstan committed patch: Add --exclude-table-data option to pg_dump. &#160; Andrew Dunstan, reviewed by Josh Berkus, Robert Haas and Peter Geoghegan. &#160; This allows dumping of a table definition but not its data, on a per table basis. Table name patterns are supported just as for --exclude-table. This patch gives me [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/12/15/waiting-for-9-2-excluding-data-of-table-from-dump/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>The secret ingredient in the webscale sauce</title>
		<link>http://www.depesz.com/index.php/2011/12/02/the-secret-ingredient-in-the-webscale-sauce/</link>
		<comments>http://www.depesz.com/index.php/2011/12/02/the-secret-ingredient-in-the-webscale-sauce/#comments</comments>
		<pubDate>Fri, 02 Dec 2011 14:20:08 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[plproxy]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[proxy]]></category>
		<category><![CDATA[scalability]]></category>
		<category><![CDATA[sharding]]></category>
		<category><![CDATA[skype]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2332</guid>
		<description><![CDATA[( title, in case you don&#8217;t know, comes from excellent &#8220;movie&#8221; about databases ) The secret ingredient is of course sharding. Can we do sharding in PostgreSQL? First, let&#8217;s define what sharding is: Wikipedia shows nice, correct, and absolutely unhelpful answer: A database shard is a horizontal partition in a database or search engine. But [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/12/02/the-secret-ingredient-in-the-webscale-sauce/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>OmniPITR 0.2.0</title>
		<link>http://www.depesz.com/index.php/2011/11/10/omnipitr-0-2-0/</link>
		<comments>http://www.depesz.com/index.php/2011/11/10/omnipitr-0-2-0/#comments</comments>
		<pubDate>Thu, 10 Nov 2011 19:01:53 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[md5]]></category>
		<category><![CDATA[omnipitr]]></category>
		<category><![CDATA[phil]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[sha-1]]></category>
		<category><![CDATA[sha-2]]></category>
		<category><![CDATA[sha-256]]></category>
		<category><![CDATA[sha-384]]></category>
		<category><![CDATA[sha-512]]></category>
		<category><![CDATA[sha1]]></category>
		<category><![CDATA[sha2]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2325</guid>
		<description><![CDATA[Just released version 0.2.0 of OmniPITR. There is one important change &#8211; that is OmniPITR backup programs can now create checksum files for backups. Details in docs, but the basic idea is that to all the other options to omnipitr-backup-{master,slave} we added (Phil Sorber to be exact) &#8211;digest option, which lets you specify that you [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/11/10/omnipitr-0-2-0/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.2 &#8211; Range data types</title>
		<link>http://www.depesz.com/index.php/2011/11/07/waiting-for-9-2-range-data-types/</link>
		<comments>http://www.depesz.com/index.php/2011/11/07/waiting-for-9-2-range-data-types/#comments</comments>
		<pubDate>Mon, 07 Nov 2011 14:39:09 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[constraint]]></category>
		<category><![CDATA[exclude]]></category>
		<category><![CDATA[gist]]></category>
		<category><![CDATA[pg92]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[range]]></category>
		<category><![CDATA[unique]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2320</guid>
		<description><![CDATA[On 3rd of November, Heikki Linnakangas committed patch: Support range DATA types. &#160; Selectivity estimation functions are missing FOR SOME range TYPE operators, which IS a TODO. &#160; Jeff Davis Well, the commit log is quite laconic. So let&#8217;s dig a bit deeper. Every once in a while you need to represent range of values. [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/11/07/waiting-for-9-2-range-data-types/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.2 &#8211; Index only scans</title>
		<link>http://www.depesz.com/index.php/2011/10/08/waiting-for-9-2-index-only-scans/</link>
		<comments>http://www.depesz.com/index.php/2011/10/08/waiting-for-9-2-index-only-scans/#comments</comments>
		<pubDate>Sat, 08 Oct 2011 15:28:13 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[covering]]></category>
		<category><![CDATA[index]]></category>
		<category><![CDATA[pg92]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[scan]]></category>
		<category><![CDATA[visibility]]></category>
		<category><![CDATA[visibility maps]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2308</guid>
		<description><![CDATA[On 8th of October, Tom Lane committed patch: Support index-only scans using the visibility map to avoid heap fetches. &#160; When a btree index contains all columns required by the query, and the visibility map shows that all tuples on a target heap page are visible-to-all, we don't need to fetch that heap page. This [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/10/08/waiting-for-9-2-index-only-scans/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>What index to create?</title>
		<link>http://www.depesz.com/index.php/2011/09/28/what-index-to-create/</link>
		<comments>http://www.depesz.com/index.php/2011/09/28/what-index-to-create/#comments</comments>
		<pubDate>Wed, 28 Sep 2011 12:18:58 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[index]]></category>
		<category><![CDATA[multicolumn]]></category>
		<category><![CDATA[partial index]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[tutorial]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2302</guid>
		<description><![CDATA[Some time ago I wrote a blogpost about why index might not be used. While this post seemed to be well received (top link from depesz.com on reddit), it doesn&#8217;t answer another question &#8211; what index to create for given situation. I&#8217;ll try to cover this question now. First of all, before we can even [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/09/28/what-index-to-create/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.2 &#8211; filtered info in explain analyze</title>
		<link>http://www.depesz.com/index.php/2011/09/25/waiting-for-9-2-filtered-info-in-explain-analyze/</link>
		<comments>http://www.depesz.com/index.php/2011/09/25/waiting-for-9-2-filtered-info-in-explain-analyze/#comments</comments>
		<pubDate>Sun, 25 Sep 2011 13:57:34 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[analyze]]></category>
		<category><![CDATA[explain]]></category>
		<category><![CDATA[explain.depesz.com]]></category>
		<category><![CDATA[filtered]]></category>
		<category><![CDATA[nfiltered]]></category>
		<category><![CDATA[pg92]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2298</guid>
		<description><![CDATA[On 22nd of September, Tom Lane committed patch: Make EXPLAIN ANALYZE report the numbers of rows rejected by filter steps. &#160; This provides information about the numbers of tuples that were visited but not returned by table scans, as well as the numbers of join tuples that were considered and discarded within a join plan [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/09/25/waiting-for-9-2-filtered-info-in-explain-analyze/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New project &#8211; Curo</title>
		<link>http://www.depesz.com/index.php/2011/09/06/new-project-curo/</link>
		<comments>http://www.depesz.com/index.php/2011/09/06/new-project-curo/#comments</comments>
		<pubDate>Tue, 06 Sep 2011 11:39:45 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[curo]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2279</guid>
		<description><![CDATA[I&#8217;d like to announce start of new project for PostgreSQL admins &#8211; Curo. Some time ago, we talked with my colleagues at OmniTI about administration of PostgreSQL, and how nicer it would be if we&#8217;d have some common tool that shows important info at will. The thing is, that when you have PostgreSQL installed, you [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/09/06/new-project-curo/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.2 &#8211; cascading streaming replication</title>
		<link>http://www.depesz.com/index.php/2011/07/26/waiting-for-9-2-cascading-streaming-replication/</link>
		<comments>http://www.depesz.com/index.php/2011/07/26/waiting-for-9-2-cascading-streaming-replication/#comments</comments>
		<pubDate>Tue, 26 Jul 2011 11:30:14 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[cascade]]></category>
		<category><![CDATA[pg92]]></category>
		<category><![CDATA[pitr]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[replication]]></category>
		<category><![CDATA[slave]]></category>
		<category><![CDATA[streaming]]></category>
		<category><![CDATA[wal]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2268</guid>
		<description><![CDATA[On 19th of July, Simon Riggs committed patch: Cascading replication feature FOR streaming log-based replication. Standby servers can now have WALSender processes, which can WORK WITH either WALReceiver OR archive_commands TO pass DATA. Fully updated docs, including NEW conceptual terms OF sending server, upstream AND downstream servers. WALSenders TERMINATED WHEN promote TO master. &#160; Fujii [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/07/26/waiting-for-9-2-cascading-streaming-replication/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.2 &#8211; Stacked Diagnostics in PL/pgSQL</title>
		<link>http://www.depesz.com/index.php/2011/07/20/waiting-for-9-2-stacked-diagnostics-in-plpgsql/</link>
		<comments>http://www.depesz.com/index.php/2011/07/20/waiting-for-9-2-stacked-diagnostics-in-plpgsql/#comments</comments>
		<pubDate>Tue, 19 Jul 2011 23:47:45 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[context]]></category>
		<category><![CDATA[detail]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[exception]]></category>
		<category><![CDATA[hint]]></category>
		<category><![CDATA[pg92]]></category>
		<category><![CDATA[plpgsql]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[raise]]></category>
		<category><![CDATA[stack trace]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2262</guid>
		<description><![CDATA[On 18th of July, Tom Lane committed patch: Add GET STACKED DIAGNOSTICS plpgsql command to retrieve exception info. &#160; This is more SQL-spec-compliant, more easily extensible, and better performing than the old method of inventing special variables. &#160; Pavel Stehule, reviewed by Shigeru Hanada and David Wheeler The problem that it solves is not very [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/07/20/waiting-for-9-2-stacked-diagnostics-in-plpgsql/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.2 &#8211; Avoiding reindexing on alter type of indexed column</title>
		<link>http://www.depesz.com/index.php/2011/07/19/waiting-for-9-2-avoiding-reindexing-on-alter-type-of-indexed-column/</link>
		<comments>http://www.depesz.com/index.php/2011/07/19/waiting-for-9-2-avoiding-reindexing-on-alter-type-of-indexed-column/#comments</comments>
		<pubDate>Tue, 19 Jul 2011 11:02:17 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[alter]]></category>
		<category><![CDATA[alter table]]></category>
		<category><![CDATA[alter type]]></category>
		<category><![CDATA[pg92]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[reindex]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2259</guid>
		<description><![CDATA[On 18th of July, Robert Haas committed patch: Avoid index rebuild for no-rewrite ALTER TABLE .. ALTER TYPE. &#160; Noah Misch. Review and minor cosmetic changes by me. Some time ago, I wrote about new feature in PostgreSQL 9.1 &#8211; changing datatypes without rewrite of table. This worked pretty good, but I didn&#8217;t test, and [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/07/19/waiting-for-9-2-avoiding-reindexing-on-alter-type-of-indexed-column/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Write Ahead Log + Understanding postgresql.conf: checkpoint_segments, checkpoint_timeout, checkpoint_warning</title>
		<link>http://www.depesz.com/index.php/2011/07/14/write-ahead-log-understanding-postgresql-conf-checkpoint_segments-checkpoint_timeout-checkpoint_warning/</link>
		<comments>http://www.depesz.com/index.php/2011/07/14/write-ahead-log-understanding-postgresql-conf-checkpoint_segments-checkpoint_timeout-checkpoint_warning/#comments</comments>
		<pubDate>Thu, 14 Jul 2011 00:46:49 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[checkpoint]]></category>
		<category><![CDATA[checkpoint_segments]]></category>
		<category><![CDATA[checkpoint_timeout]]></category>
		<category><![CDATA[checkpoint_warning]]></category>
		<category><![CDATA[configuration]]></category>
		<category><![CDATA[guc]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[understanding]]></category>
		<category><![CDATA[wal]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2249</guid>
		<description><![CDATA[While there are some docs on it, I decided to write about it, in perhaps more accessible language &#8211; not as a developer, but as PostgreSQL user. Some parts (quite large parts) were described in one of my earlier posts, but I&#8217;ll try to concentrate on WAL itself, and show a bit more in here. [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/07/14/write-ahead-log-understanding-postgresql-conf-checkpoint_segments-checkpoint_timeout-checkpoint_warning/feed/</wfw:commentRss>
		<slash:comments>21</slash:comments>
		</item>
		<item>
		<title>explain.depesz.com update</title>
		<link>http://www.depesz.com/index.php/2011/07/13/explain-depesz-com-update-2/</link>
		<comments>http://www.depesz.com/index.php/2011/07/13/explain-depesz-com-update-2/#comments</comments>
		<pubDate>Wed, 13 Jul 2011 11:43:03 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[explain]]></category>
		<category><![CDATA[explain.depesz.com]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2246</guid>
		<description><![CDATA[Just updated explain.depesz.com site with new functionality &#8211; when showing parsed plan, there is new tab &#8220;stats&#8221;. In there you can see some basic statistics of the query, used types of nodes, and tables that were used by it. There are probably some problems with stats (it&#8217;s new functionality, so bugs are imminent), but As [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/07/13/explain-depesz-com-update-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Wish list for psql</title>
		<link>http://www.depesz.com/index.php/2011/07/08/wish-list-for-psql/</link>
		<comments>http://www.depesz.com/index.php/2011/07/08/wish-list-for-psql/#comments</comments>
		<pubDate>Fri, 08 Jul 2011 13:53:51 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>
		<category><![CDATA[wishlist]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2240</guid>
		<description><![CDATA[Yesterday I talked a bit with David Fetter about improvements in psql. We both would like to get proper stored procedures (with multiple result sets, and transaction control), but since this seems to be too complicated, I thought about what I&#8217;d like to have added to psql. Ability to assign values to psql variables from [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/07/08/wish-list-for-psql/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.2 &#8211; relative paths in psql</title>
		<link>http://www.depesz.com/index.php/2011/07/08/waiting-for-9-2-relative-paths-in-psql/</link>
		<comments>http://www.depesz.com/index.php/2011/07/08/waiting-for-9-2-relative-paths-in-psql/#comments</comments>
		<pubDate>Fri, 08 Jul 2011 13:09:41 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[pg92]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2238</guid>
		<description><![CDATA[On 6th of July, Robert Haas committed patch: Add \ir command to psql. &#160; \ir is short for &#34;include relative&#34;; when used from a script, the supplied pathname will be interpreted relative to the input file, rather than to the current working directory. &#160; Gurjeet Singh, reviewed by Josh Kupershmidt, with substantial further cleanup by [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/07/08/waiting-for-9-2-relative-paths-in-psql/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bloat happens</title>
		<link>http://www.depesz.com/index.php/2011/07/06/bloat-happens/</link>
		<comments>http://www.depesz.com/index.php/2011/07/06/bloat-happens/#comments</comments>
		<pubDate>Wed, 06 Jul 2011 14:33:21 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[bloat]]></category>
		<category><![CDATA[cluster]]></category>
		<category><![CDATA[lock]]></category>
		<category><![CDATA[locks]]></category>
		<category><![CDATA[pg_reorg]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[vacuum]]></category>
		<category><![CDATA[waiting]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2231</guid>
		<description><![CDATA[For various reasons, and in various cases, bloat happens. Theoretically autovacuum protects us all, but sometimes it doesn&#8217;t. Sometimes someone disables it, or mis-configures, or bad planet alignment happens, and we end up in deep bloat. What to do then? Vacuum? Vacuum Full? Cluster? No. pg_reorg! Before I will go to describe what pg_reorg is, [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/07/06/bloat-happens/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Understanding postgresql.conf : work_mem</title>
		<link>http://www.depesz.com/index.php/2011/07/03/understanding-postgresql-conf-work_mem/</link>
		<comments>http://www.depesz.com/index.php/2011/07/03/understanding-postgresql-conf-work_mem/#comments</comments>
		<pubDate>Sun, 03 Jul 2011 20:40:29 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[configuration]]></category>
		<category><![CDATA[gin]]></category>
		<category><![CDATA[guc]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[understanding]]></category>
		<category><![CDATA[work_mem]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2218</guid>
		<description><![CDATA[For todays post in Understanding postgresql.conf series, I chose work_mem parameter. Documentation describes it as: Specifies the amount of memory to be used by internal sort operations and hash tables before writing to temporary disk files. The value defaults to one megabyte (1MB). Note that for a complex query, several sort or hash operations might [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/07/03/understanding-postgresql-conf-work_mem/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.2 &#8211; NOT VALID CHECKS</title>
		<link>http://www.depesz.com/index.php/2011/07/01/waiting-for-9-2-not-valid-checks/</link>
		<comments>http://www.depesz.com/index.php/2011/07/01/waiting-for-9-2-not-valid-checks/#comments</comments>
		<pubDate>Thu, 30 Jun 2011 22:16:23 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[check]]></category>
		<category><![CDATA[constraint]]></category>
		<category><![CDATA[nextval]]></category>
		<category><![CDATA[not valid]]></category>
		<category><![CDATA[pg92]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[valid]]></category>
		<category><![CDATA[validate]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2213</guid>
		<description><![CDATA[On 30th of June, Alvaro Herrera committed patch: Enable CHECK constraints to be declared NOT VALID &#160; This means that they can initially be added to a large existing table without checking its initial contents, but new tuples must comply to them; a separate pass invoked by ALTER TABLE / VALIDATE can verify existing data [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/07/01/waiting-for-9-2-not-valid-checks/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Why is &#8220;depesz&#8221; between &#8220;de luca&#8221; and &#8220;de vil&#8221;?</title>
		<link>http://www.depesz.com/index.php/2011/06/30/why-is-depesz-between-de-luca-and-de-vil/</link>
		<comments>http://www.depesz.com/index.php/2011/06/30/why-is-depesz-between-de-luca-and-de-vil/#comments</comments>
		<pubDate>Thu, 30 Jun 2011 12:28:39 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[collate]]></category>
		<category><![CDATA[collation]]></category>
		<category><![CDATA[locale]]></category>
		<category><![CDATA[order]]></category>
		<category><![CDATA[order by]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[sort]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2206</guid>
		<description><![CDATA[Every so often someone asks why sorting behaves irrational. Like here: $ SELECT string FROM test ORDER BY string; string ---------- dean deer de luca depesz de vil dyslexia &#40;6 ROWS&#41; Why aren&#8217;t &#8220;de luca&#8221; and &#8220;de vil&#8221; together? The exact and quick answer is: because characters with unknown location in alphabet are ignored when [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/06/30/why-is-depesz-between-de-luca-and-de-vil/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How to let clients to create new users?</title>
		<link>http://www.depesz.com/index.php/2011/06/26/how-to-let-clients-to-create-new-users/</link>
		<comments>http://www.depesz.com/index.php/2011/06/26/how-to-let-clients-to-create-new-users/#comments</comments>
		<pubDate>Sun, 26 Jun 2011 15:13:34 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[administration]]></category>
		<category><![CDATA[clients]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[shared]]></category>
		<category><![CDATA[users]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2202</guid>
		<description><![CDATA[Some (quite long) time ago, someone, somewhere (my memory is pretty fragile) asked a question. I don&#8217;t have it exact, but the gist was: is it possible to give some users rights to create new users, without making them superusers, and forcing new users to have access only to one particular database. After some discussion [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/index.php/2011/06/26/how-to-let-clients-to-create-new-users/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

