<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" version="2.0">

<channel>
	<title>select * from depesz;</title>
	
	<link>http://www.depesz.com</link>
	<description />
	<lastBuildDate>Sat, 07 Nov 2009 11:54:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/depesz" type="application/rss+xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
		<title>Waiting for 8.5 – “GRANT ALL”</title>
		<link>http://www.depesz.com/index.php/2009/11/07/waiting-for-8-5-grant-all/</link>
		<comments>http://www.depesz.com/index.php/2009/11/07/waiting-for-8-5-grant-all/#comments</comments>
		<pubDate>Sat, 07 Nov 2009 11:54:43 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[grant]]></category>
		<category><![CDATA[grantall]]></category>
		<category><![CDATA[pg85]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[privileges]]></category>
		<category><![CDATA[revoke]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1541</guid>
		<description>One of the most common (or perhaps even the most common) question people have regarding PostgreSQL, is how to change privileges for all tables.
Usually they want something like MySQL&amp;#8217;s:
GRANT ... ON database.* TO ...
Which is interesting as it is actually 2 distinct features in one:

grant privileges on all existing tables
automatically grant privileges on all tables [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/Xf-TB2syL_k" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/11/07/waiting-for-8-5-grant-all/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.5 – ’samehost’ and ’samenet’ in pg_hba.conf</title>
		<link>http://www.depesz.com/index.php/2009/11/02/waiting-for-8-5-samehost-and-samenet-in-pg_hba-conf/</link>
		<comments>http://www.depesz.com/index.php/2009/11/02/waiting-for-8-5-samehost-and-samenet-in-pg_hba-conf/#comments</comments>
		<pubDate>Mon, 02 Nov 2009 00:45:14 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[pg85]]></category>
		<category><![CDATA[pg_hba]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[samehost]]></category>
		<category><![CDATA[samenet]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1537</guid>
		<description>October, finally. &amp;#8220;Only&amp;#8221; 1 month of backlog in new features in 8.5, but I&amp;#8217;m getting there  
So, on 1st of October Tom Lane committed patch by Stef Walter:
Log Message:
-----------
Support &amp;#34;samehost&amp;#34; and &amp;#34;samenet&amp;#34; specifications in pg_hba.conf,
by enumerating the machine's IP interfaces to look for a match.
&amp;#160;
Stef Walter
For some reason I cannot find it in mailing [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/dvJada7QYlk" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/11/02/waiting-for-8-5-samehost-and-samenet-in-pg_hba-conf/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.5 – DO</title>
		<link>http://www.depesz.com/index.php/2009/11/01/waiting-for-8-5-do/</link>
		<comments>http://www.depesz.com/index.php/2009/11/01/waiting-for-8-5-do/#comments</comments>
		<pubDate>Sun, 01 Nov 2009 16:09:24 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[do]]></category>
		<category><![CDATA[pg85]]></category>
		<category><![CDATA[plpgsql]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[sql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1535</guid>
		<description>On 22nd of September, Tom Lane committed a patch by Petr Jelinek:
Log Message:
-----------
Implement the DO statement to support execution of PL code without having
to create a function for it.
&amp;#160;
Procedural languages now have an additional entry point, namely a function
to execute an inline code block.  This seemed a better design than trying
to hide the transient-ness [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/u695taRk-5s" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/11/01/waiting-for-8-5-do/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Czemu jestem taki ułomny? (wylgaryzmy, polish only)</title>
		<link>http://www.depesz.com/index.php/2009/10/30/czemu-jestem-taki-ulomny-wylgaryzmy-polish-only/</link>
		<comments>http://www.depesz.com/index.php/2009/10/30/czemu-jestem-taki-ulomny-wylgaryzmy-polish-only/#comments</comments>
		<pubDate>Fri, 30 Oct 2009 15:07:43 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[wkurw]]></category>
		<category><![CDATA[życie]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1532</guid>
		<description>Kurde. Mam w piwnicy żarówkę, ale zapala się ją jedynie kontaktem na dole. Czyli, jak wieczorem schodzę do piwnicy, to muszę zejść po ciemnych schodach i dopiero wtedy mogę zapalić światło.
Dodatkowo &amp;#8211; dzieciaki się boją chodzić do piwnicy bo ciemno. Moja pani, marudziła kilka razy, że trzeba coś z tym zrobić. No więc zrobiłem. Pojechałem [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/0id4vEh7F0I" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/10/30/czemu-jestem-taki-ulomny-wylgaryzmy-polish-only/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>Calculating backlog of events to handle</title>
		<link>http://www.depesz.com/index.php/2009/10/29/calculating-backlog-of-events-to-handle/</link>
		<comments>http://www.depesz.com/index.php/2009/10/29/calculating-backlog-of-events-to-handle/#comments</comments>
		<pubDate>Thu, 29 Oct 2009 13:37:04 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[backlog]]></category>
		<category><![CDATA[cte]]></category>
		<category><![CDATA[plpgsql]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[with]]></category>
		<category><![CDATA[with recursive]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1530</guid>
		<description>Yesterday on my favorite IRC channel fooqux asked interesting question. I took some more questions, and here is problem description:
We have a system which, every 5 minutes, takes a number of tasks to be done. Tasks are uniform. Within 5 minutes we can handle at most 100 tasks. Given the history of number of tasks [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/fLinAbhyEmk" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/10/29/calculating-backlog-of-events-to-handle/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Koniec romansu ( polish only )</title>
		<link>http://www.depesz.com/index.php/2009/10/29/koniec-romansu-polish-only/</link>
		<comments>http://www.depesz.com/index.php/2009/10/29/koniec-romansu-polish-only/#comments</comments>
		<pubDate>Thu, 29 Oct 2009 09:24:03 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[mitsubishi]]></category>
		<category><![CDATA[samochody]]></category>
		<category><![CDATA[życie]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1528</guid>
		<description>Parę lat temu, gdy kupowałem swój pierwszy samochód, poszukałem i znalazłem Mitsubishi Space Star. Fajne autko, niedrogie, wygodne.
Kupiłem. I byłem zadowolony. Potem Space Star poszedł do ludzi a ja kupiłem Lancera Kombi. Potem dokupiłem sobie zabawkę &amp;#8211; Colta CZC.
I byłem cały czas zadowolony. Mitsubishi jeździły dobrze, miały genialny Assisstance, a drobne problemy w rodzaju ludzi [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/UjRCA0HoP0k" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/10/29/koniec-romansu-polish-only/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.5 – changes in hstore</title>
		<link>http://www.depesz.com/index.php/2009/10/15/waiting-for-8-5-changes-in-hstore/</link>
		<comments>http://www.depesz.com/index.php/2009/10/15/waiting-for-8-5-changes-in-hstore/#comments</comments>
		<pubDate>Thu, 15 Oct 2009 12:18:53 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[contrib]]></category>
		<category><![CDATA[hstore]]></category>
		<category><![CDATA[pg85]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1517</guid>
		<description>Andrew Gierth (RhodiumToad on irc) wrote, and Tom Lane committed:
Assorted improvements in contrib/hstore.
&amp;#160;
Remove the 64K limit on the lengths of keys and values within an hstore.
(This changes the on-disk format, but the old format can still be read.)
Add support for btree/hash opclasses for hstore --- this is not so much
for actual indexing purposes as to [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/Z23igX7M8Co" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/10/15/waiting-for-8-5-changes-in-hstore/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.5 – MOVE {FORWARD,BACKWARD} X</title>
		<link>http://www.depesz.com/index.php/2009/10/15/waiting-for-8-5-move-forwardbackward-x/</link>
		<comments>http://www.depesz.com/index.php/2009/10/15/waiting-for-8-5-move-forwardbackward-x/#comments</comments>
		<pubDate>Thu, 15 Oct 2009 11:18:25 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[cursor]]></category>
		<category><![CDATA[cursors]]></category>
		<category><![CDATA[move]]></category>
		<category><![CDATA[pg85]]></category>
		<category><![CDATA[plpgsql]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1513</guid>
		<description>On 29th of September (I know, there is a backlog &amp;#8211; I&amp;#8217;ll work on it, I promise), Tom Lane committed another patch from Pavel Stehule:
Allow MOVE FORWARD n, MOVE BACKWARD n, MOVE FORWARD ALL, MOVE BACKWARD ALL
in plpgsql.  Clean up a couple of corner cases in the MOVE/FETCH syntax.
&amp;#160;
Pavel Stehule

Description is pretty obvious, but [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/vZn1w5K3Q-c" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/10/15/waiting-for-8-5-move-forwardbackward-x/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Weather where I live</title>
		<link>http://www.depesz.com/index.php/2009/10/14/weather-where-i-live/</link>
		<comments>http://www.depesz.com/index.php/2009/10/14/weather-where-i-live/#comments</comments>
		<pubDate>Wed, 14 Oct 2009 07:53:24 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[life]]></category>
		<category><![CDATA[photo]]></category>
		<category><![CDATA[weather]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1509</guid>
		<description>Total surprise. Couple of days ago my wife was driving open convertible, and today we have around 0° (celsius) and snow. And it looks rather nice.
View from my home entrance:

and from my office in basement:&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/Q4XLkwBIaWY" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/10/14/weather-where-i-live/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Speeding up dump/restore process</title>
		<link>http://www.depesz.com/index.php/2009/09/19/speeding-up-dumprestore-process/</link>
		<comments>http://www.depesz.com/index.php/2009/09/19/speeding-up-dumprestore-process/#comments</comments>
		<pubDate>Sat, 19 Sep 2009 17:27:53 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[dump]]></category>
		<category><![CDATA[pg_dump]]></category>
		<category><![CDATA[pg_restore]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[rsync]]></category>
		<category><![CDATA[usecase]]></category>
		<category><![CDATA[xargs]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1502</guid>
		<description>As some of you know, I&amp;#8217;ve been working lately for OmniTI company. When doing things for them (PostgreSQL related of course  , I stumbled on very interesting problem.
One of our clients is working on PostgreSQL 8.2, and wants to upgrade to 8.3. This is generally trivial &amp;#8211; pg_dump, pg_restore/psql, and you&amp;#8217;re done.
But, this situation [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/4d-NhlR39CE" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/09/19/speeding-up-dumprestore-process/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
		<item>
		<title>[polish only] Historia ku pamięci … – aktualizacja</title>
		<link>http://www.depesz.com/index.php/2009/09/16/polish-only-historia-ku-pamieci/</link>
		<comments>http://www.depesz.com/index.php/2009/09/16/polish-only-historia-ku-pamieci/#comments</comments>
		<pubDate>Wed, 16 Sep 2009 08:57:46 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[luxmed]]></category>
		<category><![CDATA[praca]]></category>
		<category><![CDATA[życie]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1497</guid>
		<description>W piątek, 14 sierpnia, jakoś tak wieczorkiem dostałem maila od bliżej mi nie znanej osoby z firmy Luxmed.
Osoba ta, poprosiła o &amp;#8220;pilny kontakt (niezależnie od godziny)&amp;#8221;, w sprawie &amp;#8220;optymalizacji baz PostgreSQL&amp;#8221;.
Zadzwoniłem.
Okazało się, że potrzebują pomocy, i uważają, że dam radę jakoś &amp;#8220;stuningować&amp;#8221; Postgresa tak by działał szybciej. I że chodzi o pomoc w dniu jutrzejszym [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/eezavLgUb-E" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/09/16/polish-only-historia-ku-pamieci/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>CREATE ROLE privilege cannot be inherited?!</title>
		<link>http://www.depesz.com/index.php/2009/09/06/create-role-privilege-cannot-be-inherited/</link>
		<comments>http://www.depesz.com/index.php/2009/09/06/create-role-privilege-cannot-be-inherited/#comments</comments>
		<pubDate>Sun, 06 Sep 2009 20:07:03 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[createrole]]></category>
		<category><![CDATA[grant]]></category>
		<category><![CDATA[inheritance]]></category>
		<category><![CDATA[plpgsql]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[roles]]></category>
		<category><![CDATA[workaround]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1494</guid>
		<description>One of my clients hit a strange limitation &amp;#8211; apparently you cannot inherit CREATE ROLE privilege.
First, let&amp;#8217;s test if it&amp;#8217;s really true:

First, let&amp;#8217;s create role which will have CREATE ROLE privilege:
create role test1 with login createrole;
Now, let&amp;#8217;s create new role, make it inherit privileges, and grant it test1 role:
# create role test2 with login inherit;
CREATE [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/2r8M45pduII" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/09/06/create-role-privilege-cannot-be-inherited/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Getting random interfacelift wallpaper</title>
		<link>http://www.depesz.com/index.php/2009/09/04/getting-random-interfacelift-wallpaper/</link>
		<comments>http://www.depesz.com/index.php/2009/09/04/getting-random-interfacelift-wallpaper/#comments</comments>
		<pubDate>Fri, 04 Sep 2009 12:32:06 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[dcop]]></category>
		<category><![CDATA[example]]></category>
		<category><![CDATA[interfacelift]]></category>
		<category><![CDATA[kde]]></category>
		<category><![CDATA[perl]]></category>
		<category><![CDATA[wallpaper]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1491</guid>
		<description>Just thought I&amp;#8217;ll share it &amp;#8211; maybe somebody else will use it.
I&amp;#8217;m using KDE 3.5, so the final &amp;#8220;dcop &amp;#8230;&amp;#8221; command, simply sets the file as current wallpaper.
I also use 1680&amp;#215;1050 resolution &amp;#8211; which you can probably guess from the code  
#!/usr/bin/perl -w
use strict;
use English qw( -no_match_vars );
use WWW::Mechanize;
&amp;#160;
my $agent = WWW::Mechanize-&amp;#62;new();
&amp;#160;
$agent-&amp;#62;get(&amp;#34;http://interfacelift.com/wallpaper_beta/downloads/random/widescreen/1680x1050/&amp;#34;);
exit unless 200 [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/szoE3RuWeLg" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/09/04/getting-random-interfacelift-wallpaper/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.5 – Machine readable EXPLAIN</title>
		<link>http://www.depesz.com/index.php/2009/08/28/waiting-for-8-5-machine-readable-explain/</link>
		<comments>http://www.depesz.com/index.php/2009/08/28/waiting-for-8-5-machine-readable-explain/#comments</comments>
		<pubDate>Fri, 28 Aug 2009 09:11:00 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[explain]]></category>
		<category><![CDATA[parsing]]></category>
		<category><![CDATA[pg85]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1488</guid>
		<description>After very long discussions, on 10th of August, Tom Lane committed patch by Robert Haas:
Log Message:
-----------
Extend EXPLAIN to support output in XML or JSON format.
&amp;#160;
There are probably still some adjustments to be made in the details
of the output, but this gets the basic structure in place.
&amp;#160;
Robert Haas

This is a very important news. Every once in [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/few4S4PwnIY" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/08/28/waiting-for-8-5-machine-readable-explain/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.5 – Multi-threaded pgbench</title>
		<link>http://www.depesz.com/index.php/2009/08/26/waiting-for-8-5-multi-threaded-pgbench/</link>
		<comments>http://www.depesz.com/index.php/2009/08/26/waiting-for-8-5-multi-threaded-pgbench/#comments</comments>
		<pubDate>Wed, 26 Aug 2009 09:57:28 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[benchmark]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[pg85]]></category>
		<category><![CDATA[pgbench]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[threads]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1486</guid>
		<description>On 3rd of August, Tatsuo Ishii committed patch by ITAGAKI Takahiro:
Log Message:
-----------
Multi-threaded version of pgbench contributed by ITAGAKI Takahiro,
reviewed by Greg Smith and Josh Williams.
&amp;#160;
Following is the proposal from ITAGAKI Takahiro:
&amp;#160;
Pgbench is a famous tool to measure postgres performance, but nowadays
it does not work well because it cannot use multiple CPUs. On the other
hand, postgres [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/KbtNiL1PoaE" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/08/26/waiting-for-8-5-multi-threaded-pgbench/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Getting session variables without touching postgresql.conf</title>
		<link>http://www.depesz.com/index.php/2009/08/20/getting-session-variables-without-touching-postgresql-conf/</link>
		<comments>http://www.depesz.com/index.php/2009/08/20/getting-session-variables-without-touching-postgresql-conf/#comments</comments>
		<pubDate>Thu, 20 Aug 2009 18:41:26 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[configuration]]></category>
		<category><![CDATA[plpgsql]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[sessions]]></category>
		<category><![CDATA[sql]]></category>
		<category><![CDATA[stackoverflow]]></category>
		<category><![CDATA[variables]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1480</guid>
		<description>This post has been updated with new code that uses temporary table &amp;#8211; the code is at the end of post!
There was this question on Stack Overflow.
For future reference: guy asked how to do session variables &amp;#8211; i.e. something he could define once in session, and later reuse in standard sql queries &amp;#8211; without modifying [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/faw_DgtvfNg" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/08/20/getting-session-variables-without-touching-postgresql-conf/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.5 – hinting for number of distinct values</title>
		<link>http://www.depesz.com/index.php/2009/08/12/waiting-for-8-5-hinting-for-number-of-distinct-values/</link>
		<comments>http://www.depesz.com/index.php/2009/08/12/waiting-for-8-5-hinting-for-number-of-distinct-values/#comments</comments>
		<pubDate>Wed, 12 Aug 2009 14:45:28 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[analyze]]></category>
		<category><![CDATA[distinct]]></category>
		<category><![CDATA[pg85]]></category>
		<category><![CDATA[planner]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[statistics]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1477</guid>
		<description>Robert Haas wrote, and Tom Lane committed (on 2nd of August) patch which adds interesting capability:
Log Message:
-----------
Add ALTER TABLE ... ALTER COLUMN ... SET STATISTICS DISTINCT
&amp;#160;
Robert Haas
Log message is rather terse, so what does it exactly do?

To plan query for execution PostgreSQL has to know some basic statistics for table. These are updated whenever you [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/RBf2DS_d-LE" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/08/12/waiting-for-8-5-hinting-for-number-of-distinct-values/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.5 – better messages for unique violation</title>
		<link>http://www.depesz.com/index.php/2009/08/12/waiting-for-8-5-better-messages-for-unique-violation/</link>
		<comments>http://www.depesz.com/index.php/2009/08/12/waiting-for-8-5-better-messages-for-unique-violation/#comments</comments>
		<pubDate>Wed, 12 Aug 2009 09:02:58 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[constraint]]></category>
		<category><![CDATA[index]]></category>
		<category><![CDATA[messages]]></category>
		<category><![CDATA[pg85]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[unique]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1475</guid>
		<description>On 1st of August Tom Lane committed patch from Itagaki Takahiro:
Improve unique-constraint-violation error messages to include the exact
values being complained of.
&amp;#160;
In passing, also remove the arbitrary length limitation in the similar
error detail message for foreign key violations.
&amp;#160;
Itagaki Takahiro
and later added an extension to it:
Department of second thoughts: let's show the exact key during unique index
build [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/Ogi4NcCjFqA" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/08/12/waiting-for-8-5-better-messages-for-unique-violation/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.5 – deferrable uniqueness</title>
		<link>http://www.depesz.com/index.php/2009/08/11/waiting-for-8-5-deferrable-uniqueness/</link>
		<comments>http://www.depesz.com/index.php/2009/08/11/waiting-for-8-5-deferrable-uniqueness/#comments</comments>
		<pubDate>Tue, 11 Aug 2009 11:24:19 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[constraint]]></category>
		<category><![CDATA[deferrable]]></category>
		<category><![CDATA[deferred]]></category>
		<category><![CDATA[pg85]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[primary key]]></category>
		<category><![CDATA[unique]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1473</guid>
		<description>On 29th of July ( I know, there is a long backlog in waiting for 8.5 series. I&amp;#8217;m working on it  , Tom Lane committed patch by Dean Rasheed:
Support deferrable uniqueness constraints.
&amp;#160;
The current implementation fires an AFTER ROW trigger for each tuple that
looks like it might be non-unique according to the index contents at [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/MBHnDUq5PGw" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/08/11/waiting-for-8-5-deferrable-uniqueness/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>1000 posts</title>
		<link>http://www.depesz.com/index.php/2009/07/22/1000-posts/</link>
		<comments>http://www.depesz.com/index.php/2009/07/22/1000-posts/#comments</comments>
		<pubDate>Wed, 22 Jul 2009 09:51:41 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[meta]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1469</guid>
		<description>I just checked my WordPress dashboard, and it says:

1,000	Posts
1,847	Comments

First entry was posted on 13th of May 2006 &amp;#8211; 1166 days ago. 
During this time I had 2 breakdowns when I said that I close the blog, switched language, and moved from &amp;#8220;everything that interests me&amp;#8221; to &amp;#8220;99% PostgreSQL only&amp;#8221;.
Blog helped me get new contacts, contracts [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/1x1GIrFS8aU" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/07/22/1000-posts/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.5 – pgsql: DROP IF EXISTS for columns and constraints.</title>
		<link>http://www.depesz.com/index.php/2009/07/22/waiting-for-8-5-pgsql-drop-if-exists-for-columns-and-constraints/</link>
		<comments>http://www.depesz.com/index.php/2009/07/22/waiting-for-8-5-pgsql-drop-if-exists-for-columns-and-constraints/#comments</comments>
		<pubDate>Wed, 22 Jul 2009 09:41:33 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[column]]></category>
		<category><![CDATA[conditional]]></category>
		<category><![CDATA[constraint]]></category>
		<category><![CDATA[ddl]]></category>
		<category><![CDATA[drop]]></category>
		<category><![CDATA[pg85]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[sql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1467</guid>
		<description>On 205h of July Andrew Dunstan committed patch by Andres Freund :
Log Message:
-----------
DROP IF EXISTS for columns and constraints. Andres Freund.

The functionality is self-explanatory, so let&amp;#8217;s just show some usage examples:
Test table:
# create table test (a int4, b int4);
CREATE TABLE
Drop non-existing column old way:
# alter table test drop column c;
ERROR:  column "c" of relation [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/5DLXBsuE8ig" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/07/22/waiting-for-8-5-pgsql-drop-if-exists-for-columns-and-constraints/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Calculating median</title>
		<link>http://www.depesz.com/index.php/2009/07/13/calculating-median/</link>
		<comments>http://www.depesz.com/index.php/2009/07/13/calculating-median/#comments</comments>
		<pubDate>Mon, 13 Jul 2009 14:13:36 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[aggre]]></category>
		<category><![CDATA[aggregate]]></category>
		<category><![CDATA[dim]]></category>
		<category><![CDATA[irc]]></category>
		<category><![CDATA[plpgsql]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[rhodiumtoad]]></category>
		<category><![CDATA[sql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1463</guid>
		<description>Today, on irc (#postgresql on freenode.net) Dim mentioned about writing median calculation code.
It got me thinking, and consequently writing my version of median calculation code.

Before I will go any further, let me just say &amp;#8211; after I finished, and was quite happy with what I wrote, RhodiumToad showed his approach which is (of course) much [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/YJDSLTHyAX8" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/07/13/calculating-median/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Slow vim startup</title>
		<link>http://www.depesz.com/index.php/2009/07/10/slow-vim-startup/</link>
		<comments>http://www.depesz.com/index.php/2009/07/10/slow-vim-startup/#comments</comments>
		<pubDate>Fri, 10 Jul 2009 21:58:13 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[gotcha]]></category>
		<category><![CDATA[ssh]]></category>
		<category><![CDATA[vim]]></category>
		<category><![CDATA[x11]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1461</guid>
		<description>I had today a very weird situation.
From my laptop, I ssh to another system, and from there to yet another.
On this final system I noticed that vim starts relatively slow. i.e. this command:
time vim -u /dev/null -c &amp;#8220;:q&amp;#8221;
returned time in around 3.5 seconds, while on my laptop (which is much less powerful) it is:
=&amp;#62; time [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/V-arh94w_JU" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/07/10/slow-vim-startup/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Getting list of unique elements</title>
		<link>http://www.depesz.com/index.php/2009/07/10/getting-list-of-unique-elements/</link>
		<comments>http://www.depesz.com/index.php/2009/07/10/getting-list-of-unique-elements/#comments</comments>
		<pubDate>Fri, 10 Jul 2009 09:48:53 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[distinct]]></category>
		<category><![CDATA[plpgsql]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[unique]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1455</guid>
		<description>Every so often you need to get list of unique elements in some column. The standard way to do it is:
select distinct column from table;
or
select column from table group by column;
The only problem is that it&amp;#8217;s slow &amp;#8211; as it has to seq scan whole table. Can it be done faster?

Usually when somebody wants to [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/jfYkuGLLrDo" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/07/10/getting-list-of-unique-elements/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>bf hacking for “fun” and definitely no profit</title>
		<link>http://www.depesz.com/index.php/2009/07/04/bf-hacking-for-fun-and-definitely-no-profit/</link>
		<comments>http://www.depesz.com/index.php/2009/07/04/bf-hacking-for-fun-and-definitely-no-profit/#comments</comments>
		<pubDate>Sat, 04 Jul 2009 19:37:27 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[brainfuck]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1449</guid>
		<description>#!/usr/bin/bf
+++++[&gt;++[&gt;&gt;++++&gt;+++++++&gt;+++&gt;+&gt;++++&gt;
++++&gt;++++&gt;+++++++++.--.+.
.--..+++.---.&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/TjV_TNOF7C8" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/07/04/bf-hacking-for-fun-and-definitely-no-profit/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.5 – Add log_line_prefix placeholder %e to contain the current SQL state</title>
		<link>http://www.depesz.com/index.php/2009/07/04/waiting-for-8-5-add-log_line_prefix-placeholder-e-to-contain-the-current-sql/</link>
		<comments>http://www.depesz.com/index.php/2009/07/04/waiting-for-8-5-add-log_line_prefix-placeholder-e-to-contain-the-current-sql/#comments</comments>
		<pubDate>Sat, 04 Jul 2009 18:26:35 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[configuration]]></category>
		<category><![CDATA[logs]]></category>
		<category><![CDATA[pg85]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1445</guid>
		<description>Also yesterday, and also Peter Eisentraut, committed patch by Guillaume Smet, which:
Add log_line_prefix placeholder %e to contain the current SQL state
&amp;#160;
Author: Guillaume Smet

What exactly does it do, and how the state looks? Let&amp;#8217;s find out.
I defined log_line_prefix to be &amp;#8216;%m %u@%d %p %r {%e} &amp;#8216;.
log_min_duration_statement was set to 0.
Then I issued some queries. Logs looked [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/HOW_1PoM6Ao" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/07/04/waiting-for-8-5-add-log_line_prefix-placeholder-e-to-contain-the-current-sql/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.5 – Have \d show child tables that inherit from the specified parent</title>
		<link>http://www.depesz.com/index.php/2009/07/04/waiting-for-8-5-have-d-show-child-tables-that-inherit-from-the-specified-parent/</link>
		<comments>http://www.depesz.com/index.php/2009/07/04/waiting-for-8-5-have-d-show-child-tables-that-inherit-from-the-specified-parent/#comments</comments>
		<pubDate>Sat, 04 Jul 2009 15:22:42 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[pg85]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1443</guid>
		<description>Yesterday Peter Eisentraut committed a patch, written by Damien Clochard, that modifies \d output in psql:
Have \d show child tables that inherit from the specified parent
&amp;#160;
As per discussion, \d shows only the number of child tables, because that
could be hundreds, when used for partitioning.  \d+ shows the actual list.
&amp;#160;
Author: Damien Clochard 

How does it [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/CqX75j7fM7U" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/07/04/waiting-for-8-5-have-d-show-child-tables-that-inherit-from-the-specified-parent/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Waiting for 8.5 – let’s start</title>
		<link>http://www.depesz.com/index.php/2009/07/03/waiting-for-8-5-lets-start/</link>
		<comments>http://www.depesz.com/index.php/2009/07/03/waiting-for-8-5-lets-start/#comments</comments>
		<pubDate>Fri, 03 Jul 2009 20:08:15 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[pg85]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1439</guid>
		<description>Everybody wrote that 8.4 was released, so it&amp;#8217;s not a news now.
But. Starting from yesterday, my own PostgreSQL reports it&amp;#8217;s version like this:
# select version();
                               [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/u7HNmR1fB6A" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/07/03/waiting-for-8-5-lets-start/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>explain.depesz.com – update</title>
		<link>http://www.depesz.com/index.php/2009/06/25/explain-depesz-com-update/</link>
		<comments>http://www.depesz.com/index.php/2009/06/25/explain-depesz-com-update/#comments</comments>
		<pubDate>Thu, 25 Jun 2009 13:04:44 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[announcements]]></category>
		<category><![CDATA[catalyst]]></category>
		<category><![CDATA[explain]]></category>
		<category><![CDATA[explain.depesz.com]]></category>
		<category><![CDATA[perl]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1437</guid>
		<description>I just updated explain.depesz.com with bugfix, which changes the way Bitmap Index Scan and Bitmap Heap Scan are displayed. Apparently index and table names were not shown previously.
Thanks go to Viktor Rosenfeld for spotting and reporting the bug.&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/6gNXvSvxq0M" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/06/25/explain-depesz-com-update/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tips N’ Tricks – Generating readable reports with plain SQL</title>
		<link>http://www.depesz.com/index.php/2009/06/23/tips-n%e2%80%99-tricks-generating-readable-reports-with-plain-sql/</link>
		<comments>http://www.depesz.com/index.php/2009/06/23/tips-n%e2%80%99-tricks-generating-readable-reports-with-plain-sql/#comments</comments>
		<pubDate>Tue, 23 Jun 2009 11:51:43 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>
		<category><![CDATA[report]]></category>
		<category><![CDATA[sql]]></category>
		<category><![CDATA[tnt]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1434</guid>
		<description>Let&amp;#8217;s say you imported some data, but it contains duplicates. You will have to handle them in some way, but to make sensible choice on how to handle it, you need more information.
So, let&amp;#8217;s start. We have table:
# \d users
                [...]&lt;img src="http://feeds.feedburner.com/~r/depesz/~4/EPdcvezJcLM" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://www.depesz.com/index.php/2009/06/23/tips-n%e2%80%99-tricks-generating-readable-reports-with-plain-sql/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
