<?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; pg84</title>
	<atom:link href="http://www.depesz.com/tag/pg84/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.depesz.com</link>
	<description></description>
	<lastBuildDate>Tue, 07 Feb 2012 13:35:12 +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 8.4 &#8211; final post (?)</title>
		<link>http://www.depesz.com/2009/04/10/waiting-for-84-final-post/</link>
		<comments>http://www.depesz.com/2009/04/10/waiting-for-84-final-post/#comments</comments>
		<pubDate>Fri, 10 Apr 2009 20:54:15 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[beta]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[rc]]></category>
		<category><![CDATA[release]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1410</guid>
		<description><![CDATA[For quite some time I&#8217;ve been posting about new features in 8.4. First post was over a year ago, on 16th of February 2008. Now, we just (yesterday) got nice surprise: beta is here: (depesz@[local]:5840) 12:39:15 [depesz] # select version(); version ----------------------------------------------------------------------------------------------------------- PostgreSQL 8.4beta1 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 4.2.4 (Ubuntu 4.2.4-1ubuntu3), 32-bit [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2009/04/10/waiting-for-84-final-post/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; no more -d in pg_dump!</title>
		<link>http://www.depesz.com/2009/03/22/waiting-for-84-no-more-d-in-pg_dump/</link>
		<comments>http://www.depesz.com/2009/03/22/waiting-for-84-no-more-d-in-pg_dump/#comments</comments>
		<pubDate>Sun, 22 Mar 2009 19:06:58 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[pg_dump]]></category>
		<category><![CDATA[pg_dumpall]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1394</guid>
		<description><![CDATA[Usually I write about new features in 8.4, but this time I&#8217;d like to write about feature that will be actually missing in 8.4. And thank God, it will be missing. On Mon, 09 Mar 2009 11:22:47 -0400 Greg Sabino Mullane wrote mail to pgsql-hackers list with his patch that removes -d switch from pg_dump. [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2009/03/22/waiting-for-84-no-more-d-in-pg_dump/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; parallel restoration of dumps</title>
		<link>http://www.depesz.com/2009/02/09/waiting-for-84-parallel-restoration-of-dumps/</link>
		<comments>http://www.depesz.com/2009/02/09/waiting-for-84-parallel-restoration-of-dumps/#comments</comments>
		<pubDate>Mon, 09 Feb 2009 12:27:46 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[parallel]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[pg_dump]]></category>
		<category><![CDATA[pg_restore]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[restore]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1377</guid>
		<description><![CDATA[On 2nd of February Andrew Dunstan committed his patch (with editing by Tom Lane) that: Log Message: ----------- Provide for parallel restoration from a custom format archive. Each data and post-data step is run in a separate worker child (a thread on Windows, a child process elsewhere) up to the concurrent number specified by the [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2009/02/09/waiting-for-84-parallel-restoration-of-dumps/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; column level privileges.</title>
		<link>http://www.depesz.com/2009/01/31/waiting-for-84-column-level-privileges/</link>
		<comments>http://www.depesz.com/2009/01/31/waiting-for-84-column-level-privileges/#comments</comments>
		<pubDate>Sat, 31 Jan 2009 16:09:06 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[columns]]></category>
		<category><![CDATA[grant]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[privileges]]></category>
		<category><![CDATA[revoke]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1375</guid>
		<description><![CDATA[On 22nd of January, Tom Lane committed patch by Stephen Frost, which adds column level privileges: Log Message: ----------- Support column-level privileges, as required by SQL standard. &#160; Stephen Frost, with help from KaiGai Kohei and others In case you don&#8217;t understand &#8211; it means that you can now grant/revoke privileges to specific columns of [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2009/01/31/waiting-for-84-column-level-privileges/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; window functions</title>
		<link>http://www.depesz.com/2009/01/21/waiting-for-84-window-functions/</link>
		<comments>http://www.depesz.com/2009/01/21/waiting-for-84-window-functions/#comments</comments>
		<pubDate>Wed, 21 Jan 2009 17:06:25 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[aggregate]]></category>
		<category><![CDATA[avg]]></category>
		<category><![CDATA[cumulative sum]]></category>
		<category><![CDATA[groups]]></category>
		<category><![CDATA[partitions]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[rownum]]></category>
		<category><![CDATA[sum]]></category>
		<category><![CDATA[window functions]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1369</guid>
		<description><![CDATA[A long overdue post about new functionality. At this moment it is no longer such new, as it was committed on 28th of December (yes, I know, I should have written it earlier, Sorry). On this day Tom Lane committed patch by Hitoshi Harada which adds support for so called window functions: Support window functions [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2009/01/21/waiting-for-84-window-functions/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; pg_stat_statements</title>
		<link>http://www.depesz.com/2009/01/13/waiting-for-84-pg_stat_statements/</link>
		<comments>http://www.depesz.com/2009/01/13/waiting-for-84-pg_stat_statements/#comments</comments>
		<pubDate>Tue, 13 Jan 2009 15:37:26 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[analysis]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[pgfouine]]></category>
		<category><![CDATA[pg_stat_statements]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[stats]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1366</guid>
		<description><![CDATA[On 4th of January, Tom Lane committed patch by Takahiro Itagaki, which adds new contrib module &#8211; pg_stat_statements: Log Message: ----------- Add contrib/pg_stat_statements for server-wide tracking of statement execution statistics. &#160; Takahiro Itagaki What is it for? Well, actually, it takes some work away from projects like pgFouine or my own analyze.pgsql.logs.pl. To this day, [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2009/01/13/waiting-for-84-pg_stat_statements/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; remove system objects from \dX</title>
		<link>http://www.depesz.com/2009/01/08/waiting-for-84-remove-system-objects-from-dx/</link>
		<comments>http://www.depesz.com/2009/01/08/waiting-for-84-remove-system-objects-from-dx/#comments</comments>
		<pubDate>Thu, 08 Jan 2009 19:12:05 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1364</guid>
		<description><![CDATA[On 6th of January Bruce Momjian committed patch by Greg Sabino Mulane, which fixes one of a very long standing annoyances in PostgreSQL &#8211; removes system objects from \dX commands in psql. Commit message: This makes all the \dX commands (most importantly to most: \df) work like \dt does, in that it requires a \dXS [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2009/01/08/waiting-for-84-remove-system-objects-from-dx/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; Window Functions &#8211; teaser</title>
		<link>http://www.depesz.com/2008/12/29/waiting-for-84-window-functions-teaser/</link>
		<comments>http://www.depesz.com/2008/12/29/waiting-for-84-window-functions-teaser/#comments</comments>
		<pubDate>Mon, 29 Dec 2008 18:51:16 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[window functions]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1359</guid>
		<description><![CDATA[Yesterday Tom Lane committed enormous patch, which had commit log: Support window functions a la SQL:2008. &#160; Hitoshi Harada, with some kibitzing from Heikki and Tom. &#8230; and that would be all. I will write more about it, its use cases, and some detailed examples but now I&#8217;m on vacation, and will stay here for [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/12/29/waiting-for-84-window-functions-teaser/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; Default values for function arguments + integer in any base</title>
		<link>http://www.depesz.com/2008/12/09/waiting-for-84-default-values-for-function-arguments-integer-in-any-base/</link>
		<comments>http://www.depesz.com/2008/12/09/waiting-for-84-default-values-for-function-arguments-integer-in-any-base/#comments</comments>
		<pubDate>Tue, 09 Dec 2008 12:31:36 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[base]]></category>
		<category><![CDATA[conversion]]></category>
		<category><![CDATA[default]]></category>
		<category><![CDATA[functions]]></category>
		<category><![CDATA[integer]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1355</guid>
		<description><![CDATA[On 4th of December Peter Eisentraut committed patch by Pavel Stehule (with Peters tweaks) which adds default values for function arguments: Default values for function arguments &#160; Pavel Stehule, with some tweaks by Peter Eisentraut Well, the functionality is pretty obvious, so let&#8217;s see how to use it in real code. To do so I&#8217;ll [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/12/09/waiting-for-84-default-values-for-function-arguments-integer-in-any-base/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; Visibility maps</title>
		<link>http://www.depesz.com/2008/12/08/waiting-for-84-visibility-maps/</link>
		<comments>http://www.depesz.com/2008/12/08/waiting-for-84-visibility-maps/#comments</comments>
		<pubDate>Mon, 08 Dec 2008 12:37:19 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[vacuum]]></category>
		<category><![CDATA[visibility]]></category>
		<category><![CDATA[visibility maps]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1336</guid>
		<description><![CDATA[Yeah. This one patch alone is worth upgrading to 8.4. On 3rd of December Heikki Linnakangas committed his patch. Commit message: Introduce visibility map. The visibility map is a bitmap with one bit per heap page, where a set bit indicates that all tuples on the page are visible to all transactions, and the page [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/12/08/waiting-for-84-visibility-maps/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; TABLE</title>
		<link>http://www.depesz.com/2008/11/23/waiting-for-84-table/</link>
		<comments>http://www.depesz.com/2008/11/23/waiting-for-84-table/#comments</comments>
		<pubDate>Sun, 23 Nov 2008 14:19:19 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[select]]></category>
		<category><![CDATA[table]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1320</guid>
		<description><![CDATA[On Thursday, 20th of November, Peter Eisentraut committed his own patch, which adds new command to PostgreSQL: TABLE. While this command doesn&#8217;t do anything that wasn&#8217;t available earlier, it&#8217;s worth mentioning, as it&#8217;s one of patches that make PostgreSQL compatible with SQL:2008. Basically new command &#8220;TABLE&#8221; acts like an alias to &#8216;SELECT * FROM&#8217;: MORE [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/11/23/waiting-for-84-table/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; auto-explain</title>
		<link>http://www.depesz.com/2008/11/23/waiting-for-84-auto-explain/</link>
		<comments>http://www.depesz.com/2008/11/23/waiting-for-84-auto-explain/#comments</comments>
		<pubDate>Sun, 23 Nov 2008 14:03:22 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[explain]]></category>
		<category><![CDATA[guc]]></category>
		<category><![CDATA[logs]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1318</guid>
		<description><![CDATA[On 19th of November Tom Lane committed patch by Takahiro Itagaki which does: Add auto-explain contrib module for automatic logging of the plans of slow-running queries. What exactly does it do? Before I will go into more details &#8211; side note &#8211; this is the first extension to PostgreSQL (that I&#8217;ve seen) that uses custom_variable_classes [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/11/23/waiting-for-84-auto-explain/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; array aggregate and array unpacker</title>
		<link>http://www.depesz.com/2008/11/14/waiting-for-84-array-aggregate-and-array-unpacker/</link>
		<comments>http://www.depesz.com/2008/11/14/waiting-for-84-array-aggregate-and-array-unpacker/#comments</comments>
		<pubDate>Fri, 14 Nov 2008 16:15:24 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[aggregate]]></category>
		<category><![CDATA[arrays]]></category>
		<category><![CDATA[array_agg]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[unnest]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1314</guid>
		<description><![CDATA[Finally, we got very important addons to PostgreSQL, which help with dealing with arrays. It solves a lot of problems, which were usually solved with standard cookbook code, which was in faqs, blog posts and number of examples on irc. First, there is a function to build array as aggregate. It was committed by Peter [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/11/14/waiting-for-84-array-aggregate-and-array-unpacker/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; suppress_redundant_updates_trigger</title>
		<link>http://www.depesz.com/2008/11/05/waiting-for-84-suppress_redundant_updates_trigger/</link>
		<comments>http://www.depesz.com/2008/11/05/waiting-for-84-suppress_redundant_updates_trigger/#comments</comments>
		<pubDate>Wed, 05 Nov 2008 19:49:38 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[trigger]]></category>
		<category><![CDATA[update]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1311</guid>
		<description><![CDATA[On 3rd of November Andrew Dunstan committed his patch which adds new function to PostgreSQL &#8211; suppress_redundant_updates_trigger(). This function is not for using in selects, but it can help you tremendously if your database access matches certain pattern. To be more precise &#8211; if you have a lot of updates that don&#8217;t really update anything [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/11/05/waiting-for-84-suppress_redundant_updates_trigger/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; sql-wrappable RETURNING</title>
		<link>http://www.depesz.com/2008/11/03/waiting-for-84-sql-wrappable-returning/</link>
		<comments>http://www.depesz.com/2008/11/03/waiting-for-84-sql-wrappable-returning/#comments</comments>
		<pubDate>Mon, 03 Nov 2008 12:37:16 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[functions]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[returning]]></category>
		<category><![CDATA[sql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1307</guid>
		<description><![CDATA[In PostgreSQL 8.2, we got &#8220;RETURNING&#8221; clause in INSERT/UPDATE/DELETE queries. Unfortunately it could not be used as source of rows for anything in sql. insert into table_backup delete from table where ... returning *; Well, it&#8217;s still not possible, but it is a one step closer, thanks to patch written and committed by Tom Lane [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/11/03/waiting-for-84-sql-wrappable-returning/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; pl/* srf functions in selects</title>
		<link>http://www.depesz.com/2008/11/03/waiting-for-84-pl-srf-functions-in-selects/</link>
		<comments>http://www.depesz.com/2008/11/03/waiting-for-84-pl-srf-functions-in-selects/#comments</comments>
		<pubDate>Mon, 03 Nov 2008 12:03:01 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[functions]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[pl/*]]></category>
		<category><![CDATA[plpgsql]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[select]]></category>
		<category><![CDATA[srf]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1305</guid>
		<description><![CDATA[On 28th of October Tom Lane committed his patch that changes some internals of functions, but it also adds interesting capability. Commit message: Extend ExecMakeFunctionResult() to support set-returning functions that return via a tuplestore instead of value-per-call. Refactor a few things to reduce ensuing code duplication with nodeFunctionscan.c. This represents the reasonably noncontroversial part of [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/11/03/waiting-for-84-pl-srf-functions-in-selects/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; Common Table Expressions (WITH queries)</title>
		<link>http://www.depesz.com/2008/10/07/waiting-for-84-common-table-expressions-with-queries/</link>
		<comments>http://www.depesz.com/2008/10/07/waiting-for-84-common-table-expressions-with-queries/#comments</comments>
		<pubDate>Mon, 06 Oct 2008 22:14:35 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[cte]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[with]]></category>
		<category><![CDATA[with recursive]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1287</guid>
		<description><![CDATA[On 4th of September Tom Lane committed another great patch. This one is very large, and even after applying &#8211; it&#8217;s has some rough edges. There will be need for additional patches to make the functionality fully robust, but the fact that it got committed means that it will be available in final 8.4. What [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/10/07/waiting-for-84-common-table-expressions-with-queries/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; new FSM (Free Space Map)</title>
		<link>http://www.depesz.com/2008/10/04/waiting-for-84-new-fsm-free-space-map/</link>
		<comments>http://www.depesz.com/2008/10/04/waiting-for-84-new-fsm-free-space-map/#comments</comments>
		<pubDate>Sat, 04 Oct 2008 11:25:22 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[fsm]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[vacuum]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1282</guid>
		<description><![CDATA[On 30th of September, Heikki Linnakangas committed his patch that changes FSM: Rewrite the FSM. Instead of relying on a fixed-size shared memory segment, the free space information is stored in a dedicated FSM relation fork, with each relation (except for hash indexes; they don't use FSM). &#160; This eliminates the max_fsm_relations and max_fsm_pages GUC [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/10/04/waiting-for-84-new-fsm-free-space-map/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; database-level lc_collation and lc_ctype</title>
		<link>http://www.depesz.com/2008/09/28/waiting-for-84-database-level-lc_collation-and-lc_ctype/</link>
		<comments>http://www.depesz.com/2008/09/28/waiting-for-84-database-level-lc_collation-and-lc_ctype/#comments</comments>
		<pubDate>Sun, 28 Sep 2008 20:26:49 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[collate]]></category>
		<category><![CDATA[ctype]]></category>
		<category><![CDATA[initdb]]></category>
		<category><![CDATA[locale]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1278</guid>
		<description><![CDATA[On 23rd of September, Heikki Linnakangas committed patch that was written by Radek Strnad (actually committed patch is a stripped-down version of original). What it does? It adds ability to have (finally!) different collation order and character categories for different databases. Up until now, you had to set LC_COLLATE and LC_CTYPE when doing initdb, and [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/09/28/waiting-for-84-database-level-lc_collation-and-lc_ctype/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; pgbench with timed execution</title>
		<link>http://www.depesz.com/2008/09/13/waiting-for-84-pgbench-with-timed-execution/</link>
		<comments>http://www.depesz.com/2008/09/13/waiting-for-84-pgbench-with-timed-execution/#comments</comments>
		<pubDate>Sat, 13 Sep 2008 13:33:06 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[pgbench]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1261</guid>
		<description><![CDATA[Takahiro Itagaki wrote, and Tom Lane committed nice patch, which I personally find really helpful: Add a duration option to pgbench, so that test length can be specified in seconds instead of by number of transactions to run. Takahiro Itagaki You might wonder what&#8217;s so great nice about it. Well, during my years as dba [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/09/13/waiting-for-84-pgbench-with-timed-execution/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; ordered data loading in pg_dump</title>
		<link>http://www.depesz.com/2008/09/08/waiting-for-84-ordered-data-loading-in-pg_dump/</link>
		<comments>http://www.depesz.com/2008/09/08/waiting-for-84-ordered-data-loading-in-pg_dump/#comments</comments>
		<pubDate>Mon, 08 Sep 2008 18:55:45 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[pg_dump]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1255</guid>
		<description><![CDATA[Great (and admittedly long overdue) patch by Tom Lane: Make pg_dump --data-only try to order the table dumps so that foreign keys' referenced tables are dumped before the referencing tables. This avoids failures when the data is loaded with the FK constraints already active. If no such ordering is possible because of circular or self-referential [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/09/08/waiting-for-84-ordered-data-loading-in-pg_dump/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; \ef in psql</title>
		<link>http://www.depesz.com/2008/09/06/waiting-for-84-ef-in-psql/</link>
		<comments>http://www.depesz.com/2008/09/06/waiting-for-84-ef-in-psql/#comments</comments>
		<pubDate>Sat, 06 Sep 2008 19:45:46 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[editor]]></category>
		<category><![CDATA[functions]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1251</guid>
		<description><![CDATA[Today, Tom Lane committed patch, written by Abhijit Menon-Sen, which adds interesting feature to psql. Namely &#8211; it simplifies changing definition of functions. Commit message pretty much explains everything: Implement a psql command "\ef" to edit the definition of a function. In support of that, create a backend function pg_get_functiondef(). The psql command is functional [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/09/06/waiting-for-84-ef-in-psql/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; case insensitive text ( citext )</title>
		<link>http://www.depesz.com/2008/08/10/waiting-for-84-case-insensitive-text-citext/</link>
		<comments>http://www.depesz.com/2008/08/10/waiting-for-84-case-insensitive-text-citext/#comments</comments>
		<pubDate>Sun, 10 Aug 2008 16:40:48 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[case]]></category>
		<category><![CDATA[citext]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[lower]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1242</guid>
		<description><![CDATA[On 29th of July, Tom Lane committed patch written by David E. Wheeler, which added new contrib module: citext. Log message is rather laconic: Add a new, improved version of citext as a contrib module. &#160; David E. Wheeler So, let&#8217;s look into details. First, let&#8217;s imagine a use case. You have web system, which [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/08/10/waiting-for-84-case-insensitive-text-citext/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; UNION / INTERSECT / EXCEPT</title>
		<link>http://www.depesz.com/2008/08/10/waiting-for-84-union-intersect-except/</link>
		<comments>http://www.depesz.com/2008/08/10/waiting-for-84-union-intersect-except/#comments</comments>
		<pubDate>Sun, 10 Aug 2008 15:04:57 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[except]]></category>
		<category><![CDATA[intersect]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[speedup]]></category>
		<category><![CDATA[union]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1236</guid>
		<description><![CDATA[During last month or so, Tom Lane commited changes in PostgreSQL, which were foundations for adding hash-based versions of popular features. I already described first such feature &#8211; DISTINCT. Now, there were 3 more commits which were related to this: All 3 were committed by Tom, on 7th of August. Commit messages: Teach the system [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/08/10/waiting-for-84-union-intersect-except/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; hash based DISTINCT</title>
		<link>http://www.depesz.com/2008/08/05/waiting-for-84-hash-based-distinct/</link>
		<comments>http://www.depesz.com/2008/08/05/waiting-for-84-hash-based-distinct/#comments</comments>
		<pubDate>Tue, 05 Aug 2008 09:39:20 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[distinct]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1231</guid>
		<description><![CDATA[Today Tom Lane committed patch which gives DISTINCT ability to use hash aggregate &#8211; just like GROUP BY. Log message: Improve SELECT DISTINCT to consider hash aggregation, as well as sort/uniq, as methods for implementing the DISTINCT step. This eliminates the former performance gap between DISTINCT and GROUP BY, and also makes it possible to [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/08/05/waiting-for-84-hash-based-distinct/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; RETURNS TABLE</title>
		<link>http://www.depesz.com/2008/08/04/waiting-for-84-returns-table/</link>
		<comments>http://www.depesz.com/2008/08/04/waiting-for-84-returns-table/#comments</comments>
		<pubDate>Mon, 04 Aug 2008 12:21:53 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[functions]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[returns]]></category>
		<category><![CDATA[srf]]></category>
		<category><![CDATA[table]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1229</guid>
		<description><![CDATA[Pavel Stehule wrote, and Tom Lane committed patch which ads new syntax for set-returning functions: &#8220;RETURNS TABLE&#8221;. Commit was on 18th of July, and the message was: Implement SQL-spec RETURNS TABLE syntax for functions. &#160; (Unlike the original submission, this patch treats TABLE output parameters as being entirely equivalent to OUT parameters -- tgl) &#160; [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/08/04/waiting-for-84-returns-table/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; variadic functions</title>
		<link>http://www.depesz.com/2008/07/31/waiting-for-84-variadic-functions/</link>
		<comments>http://www.depesz.com/2008/07/31/waiting-for-84-variadic-functions/#comments</comments>
		<pubDate>Thu, 31 Jul 2008 13:14:15 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[functions]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[variadic]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1223</guid>
		<description><![CDATA[Pavel Stehule wrote, and then Tom Lane committed (on 16th of July), patch which adds to PostgreSQL support for functions with variable number of arguments. These function are called &#8220;VARIADIC&#8221;, and up until now writing such a function was impossible. You could overcome this limitation by: defining a lot of functions with the same name, [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/07/31/waiting-for-84-variadic-functions/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; storage types for table columns</title>
		<link>http://www.depesz.com/2008/07/30/waiting-for-84-storage-types-for-table-columns/</link>
		<comments>http://www.depesz.com/2008/07/30/waiting-for-84-storage-types-for-table-columns/#comments</comments>
		<pubDate>Wed, 30 Jul 2008 13:28:58 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[compression]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>
		<category><![CDATA[storage]]></category>
		<category><![CDATA[toast]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1222</guid>
		<description><![CDATA[Gregory Stark wrote, and Bruce Momjian committed (on 14th of July) patch which shows storage type in psql. Log Message: ----------- Add column storage type to psql \d+ display. &#160; Gregory Stark How does it work? It&#8217;s pretty simple. Let&#8217;s create new table: # create table testit (i int4, ts timestamp, t text, z varchar(10), [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/07/30/waiting-for-84-storage-types-for-table-columns/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; sequence details</title>
		<link>http://www.depesz.com/2008/07/30/waiting-for-84-sequence-details/</link>
		<comments>http://www.depesz.com/2008/07/30/waiting-for-84-sequence-details/#comments</comments>
		<pubDate>Wed, 30 Jul 2008 13:17:20 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>
		<category><![CDATA[sequence]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1221</guid>
		<description><![CDATA[On 15th of July, Bruce Momjian commited patch written by Dickson S. Guedes, which: Have psql \d show the value of sequence columns. before it, output of \d of sequence was like this: # \d some_sequence Sequence "public.some_sequence" Column &#124; Type ---------------+--------- sequence_name &#124; name last_value &#124; bigint increment_by &#124; bigint max_value &#124; bigint min_value [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/07/30/waiting-for-84-sequence-details/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.4 &#8211; timing on/off</title>
		<link>http://www.depesz.com/2008/06/11/waiting-for-84-waiting-onoff/</link>
		<comments>http://www.depesz.com/2008/06/11/waiting-for-84-waiting-onoff/#comments</comments>
		<pubDate>Wed, 11 Jun 2008 20:33:39 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>
		<category><![CDATA[waiting]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1215</guid>
		<description><![CDATA[Yes, finally! David Fetter wrote, and Heikki Linnakangas committed patch which adds on/off arguments to \timing: Before you could simply do: \timing to switch timing information: # select 1; ?column? ---------- 1 (1 row) # \timing Timing is on. # select 1; ?column? ---------- 1 (1 row) Time: 0.364 ms # \timing Timing is off. [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/06/11/waiting-for-84-waiting-onoff/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
	</channel>
</rss>

