<?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/tag/postgresql/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.depesz.com</link>
	<description></description>
	<lastBuildDate>Sun, 19 May 2013 14:56:36 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Explaining the unexplainable – part 4</title>
		<link>http://www.depesz.com/2013/05/19/explaining-the-unexplainable-part-4/</link>
		<comments>http://www.depesz.com/2013/05/19/explaining-the-unexplainable-part-4/#comments</comments>
		<pubDate>Sun, 19 May 2013 14:56:36 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[append]]></category>
		<category><![CDATA[cte]]></category>
		<category><![CDATA[explain]]></category>
		<category><![CDATA[groupaggregate]]></category>
		<category><![CDATA[hashsetop]]></category>
		<category><![CDATA[initplan]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[result]]></category>
		<category><![CDATA[setop]]></category>
		<category><![CDATA[subplan]]></category>
		<category><![CDATA[unexplainable]]></category>
		<category><![CDATA[unique]]></category>
		<category><![CDATA[values]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2709</guid>
		<description><![CDATA[In this, hopefully 2nd to last, post in the series, I will cover the rest of usually happening operations that you can see in your explain outputs. Unique Name seems to be clear about what's going on here &#8211; it removes duplicate data. This might happen, for example, when you're doing: SELECT DISTINCT FIELD FROM [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/05/19/explaining-the-unexplainable-part-4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A tale of automating tests of Pg with Bash</title>
		<link>http://www.depesz.com/2013/05/16/a-tale-of-automating-tests-of-pg-with-bash/</link>
		<comments>http://www.depesz.com/2013/05/16/a-tale-of-automating-tests-of-pg-with-bash/#comments</comments>
		<pubDate>Wed, 15 May 2013 23:03:25 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[ctrl-c]]></category>
		<category><![CDATA[int]]></category>
		<category><![CDATA[monitor]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[sigint]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2707</guid>
		<description><![CDATA[Word of warning: this blogpost is about thing related to Bash (well, maybe other shells too, didn't really test), but since I found it while doing Pg work, and it might bite someone else doing Pg related work, I decided to add it to &#8220;postgresql" tag. So, due to some work I had to do, [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/05/16/a-tale-of-automating-tests-of-pg-with-bash/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Explaining the unexplainable – part 3</title>
		<link>http://www.depesz.com/2013/05/09/explaining-the-unexplainable-part-3/</link>
		<comments>http://www.depesz.com/2013/05/09/explaining-the-unexplainable-part-3/#comments</comments>
		<pubDate>Thu, 09 May 2013 13:11:00 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[aggregate]]></category>
		<category><![CDATA[explain]]></category>
		<category><![CDATA[function]]></category>
		<category><![CDATA[hash]]></category>
		<category><![CDATA[join]]></category>
		<category><![CDATA[limit]]></category>
		<category><![CDATA[loop]]></category>
		<category><![CDATA[materialize]]></category>
		<category><![CDATA[merge]]></category>
		<category><![CDATA[nested]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[scan]]></category>
		<category><![CDATA[sort]]></category>
		<category><![CDATA[unexplainable]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2703</guid>
		<description><![CDATA[In previous post in the series I wrote about how to interpret single line in explain analyze output, it's structure, and later on described all basic data-getting operations (nodes in explain tree). Today, we'll move towards more complicated operations. Function Scan Example: $ EXPLAIN analyze SELECT * FROM generate_Series&#40;1,10&#41; i; QUERY PLAN --------------------------------------------------------------------------------------------------------------------- FUNCTION Scan [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/05/09/explaining-the-unexplainable-part-3/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Explaining the unexplainable &#8211; part 2</title>
		<link>http://www.depesz.com/2013/04/27/explaining-the-unexplainable-part-2/</link>
		<comments>http://www.depesz.com/2013/04/27/explaining-the-unexplainable-part-2/#comments</comments>
		<pubDate>Sat, 27 Apr 2013 16:23:53 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[bitmap]]></category>
		<category><![CDATA[explain]]></category>
		<category><![CDATA[heap]]></category>
		<category><![CDATA[index]]></category>
		<category><![CDATA[only]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[scan]]></category>
		<category><![CDATA[seq]]></category>
		<category><![CDATA[unexplainable]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2700</guid>
		<description><![CDATA[Last time I wrote about what explain output shows. Now I'd like to talk more about various types of &#8220;nodes" / operations that you might see in explain plans. The most basic one is Seq Scan. It looks like this: EXPLAIN analyze SELECT * FROM pg_class; QUERY PLAN --------------------------------------------------------------------------------------------------------- Seq Scan ON pg_class &#40;cost=0.00..10.92 ROWS=292 [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/04/27/explaining-the-unexplainable-part-2/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Win a book contest &#8211; PostgreSQL Backup and Restore How-to</title>
		<link>http://www.depesz.com/2013/04/25/win-a-book-contest-postgresql-backup-and-restore-how-to/</link>
		<comments>http://www.depesz.com/2013/04/25/win-a-book-contest-postgresql-backup-and-restore-how-to/#comments</comments>
		<pubDate>Thu, 25 Apr 2013 11:11:58 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[backups]]></category>
		<category><![CDATA[book]]></category>
		<category><![CDATA[contest]]></category>
		<category><![CDATA[giveaway]]></category>
		<category><![CDATA[packt]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[restore]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2689</guid>
		<description><![CDATA[Around the time that Xzilla wrote about the book, Packt contacted me and asked for a review. Since I generally don't really read technical books, I declined the offer, but Sandy from Packt was very persistent, and asked if I could inform about book giveaway contest. The book is definitely PostgreSQL related, and Xzilla suggested [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/04/25/win-a-book-contest-postgresql-backup-and-restore-how-to/feed/</wfw:commentRss>
		<slash:comments>20</slash:comments>
		</item>
		<item>
		<title>Explaining the unexplainable</title>
		<link>http://www.depesz.com/2013/04/16/explaining-the-unexplainable/</link>
		<comments>http://www.depesz.com/2013/04/16/explaining-the-unexplainable/#comments</comments>
		<pubDate>Tue, 16 Apr 2013 11:53:24 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[explain]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[unexplainable]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2684</guid>
		<description><![CDATA[One of the first things new DBA hears is &#8220;Use the EXPLAIN". And upon first try he/she is greeted with incomprehensible: QUERY PLAN --------------------------------------------------------------------------------------------------------------------------- Sort &#40;cost=146.63..148.65 ROWS=808 width=138&#41; &#40;actual TIME=55.009..55.012 ROWS=71 loops=1&#41; Sort KEY: n.nspname, p.proname, &#40;pg_get_function_arguments&#40;p.oid&#41;&#41; Sort Method: quicksort Memory: 43kB -&#62; Hash JOIN &#40;cost=1.14..107.61 ROWS=808 width=138&#41; &#40;actual TIME=42.495..54.854 ROWS=71 loops=1&#41; Hash Cond: &#40;p.pronamespace [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/04/16/explaining-the-unexplainable/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.3 &#8211; Support indexing of regular-expression searches in contrib/pg_trgm.</title>
		<link>http://www.depesz.com/2013/04/10/waiting-for-9-3-support-indexing-of-regular-expression-searches-in-contribpg_trgm/</link>
		<comments>http://www.depesz.com/2013/04/10/waiting-for-9-3-support-indexing-of-regular-expression-searches-in-contribpg_trgm/#comments</comments>
		<pubDate>Wed, 10 Apr 2013 11:55:23 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[expression]]></category>
		<category><![CDATA[index]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[pg93]]></category>
		<category><![CDATA[pg_trgm]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[regexp]]></category>
		<category><![CDATA[regular]]></category>
		<category><![CDATA[trgm]]></category>
		<category><![CDATA[trigram]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2672</guid>
		<description><![CDATA[On 9th of April, Tom Lane committed patch: Support indexing of regular-expression searches in contrib/pg_trgm. &#160; This works by extracting trigrams from the given regular expression, in generally the same spirit as the previously-existing support for LIKE searches, though of course the details are far more complicated. &#160; Currently, only GIN indexes are supported. We [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/04/10/waiting-for-9-3-support-indexing-of-regular-expression-searches-in-contribpg_trgm/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.3 &#8211; Add \watch [SEC] command to psql.</title>
		<link>http://www.depesz.com/2013/04/07/waiting-for-9-3-add-watch-sec-command-to-psql/</link>
		<comments>http://www.depesz.com/2013/04/07/waiting-for-9-3-add-watch-sec-command-to-psql/#comments</comments>
		<pubDate>Sun, 07 Apr 2013 10:17:16 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[administration]]></category>
		<category><![CDATA[monitoring]]></category>
		<category><![CDATA[pg93]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>
		<category><![CDATA[watch]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2662</guid>
		<description><![CDATA[On 4th of April, Tom Lane committed patch: Add \watch [SEC] command to psql. &#160; This allows convenient re-execution of commands. &#160; Will Leinweber, reviewed by Peter Eisentraut, Daniel Farina, and Tom Lane Psql is the best client for PostgreSQL (in my not so humble opinion). It can do many cool stuff, and with some [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/04/07/waiting-for-9-3-add-watch-sec-command-to-psql/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>New OmniPITR release</title>
		<link>http://www.depesz.com/2013/04/02/new-omnipitr-release/</link>
		<comments>http://www.depesz.com/2013/04/02/new-omnipitr-release/#comments</comments>
		<pubDate>Tue, 02 Apr 2013 15:53:16 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[announce]]></category>
		<category><![CDATA[announcements]]></category>
		<category><![CDATA[omnipitr]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2660</guid>
		<description><![CDATA[Yesterday, I did release new version of OmniPITR &#8211; 1.1.0. You can get it from github or from PgXN. What's new? Couple of things: Fix: omnipitr-monitor had a bug with parsing timestamps from logs (in cases of &#8220;negative" timezones) Fix: sanity-check.sh now returns correct status when exiting, so you can verify if everything is OK [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/04/02/new-omnipitr-release/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Changes on explain.depesz.com</title>
		<link>http://www.depesz.com/2013/03/30/changes-on-explain-depesz-com-3/</link>
		<comments>http://www.depesz.com/2013/03/30/changes-on-explain-depesz-com-3/#comments</comments>
		<pubDate>Sat, 30 Mar 2013 19:44:32 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[explain]]></category>
		<category><![CDATA[explain.depesz.com]]></category>
		<category><![CDATA[mojolicious]]></category>
		<category><![CDATA[perl]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2653</guid>
		<description><![CDATA[So, I made some changes to explain.depesz.com, and while informing about it, I'd like to brag a bit about numbers, again First, the changes: About two weeks ago xocolatl found a bug in anonymization code: 16:46 &#60; xocolatl&#62; there's a bug in the anonymization at line 12 16:47 &#60; xocolatl&#62; depesz: look at line 12 [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/03/30/changes-on-explain-depesz-com-3/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.3 &#8211; Add new JSON processing functions and parser API.</title>
		<link>http://www.depesz.com/2013/03/30/waiting-for-9-3-add-new-json-processing-functions-and-parser-api/</link>
		<comments>http://www.depesz.com/2013/03/30/waiting-for-9-3-add-new-json-processing-functions-and-parser-api/#comments</comments>
		<pubDate>Sat, 30 Mar 2013 16:26:18 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[json]]></category>
		<category><![CDATA[pg93]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2651</guid>
		<description><![CDATA[On 29th of March, Andrew Dunstan committed patch: Add new JSON processing functions and parser API. &#160; The JSON parser is converted into a recursive descent parser, and exposed for use by other modules such as extensions. The API provides hooks for all the significant parser event such as the beginning and end of objects [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/03/30/waiting-for-9-3-add-new-json-processing-functions-and-parser-api/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.3 &#8211; Add parallel pg_dump option.</title>
		<link>http://www.depesz.com/2013/03/26/2646/</link>
		<comments>http://www.depesz.com/2013/03/26/2646/#comments</comments>
		<pubDate>Tue, 26 Mar 2013 21:13:02 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[parallel]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[pg93]]></category>
		<category><![CDATA[pg_dump]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2646</guid>
		<description><![CDATA[On 24th of March, Andrew Dunstan committed patch: Add parallel pg_dump option. &#160; New infrastructure is added which creates a set number of workers (threads on Windows, forked processes on Unix). Jobs are then handed out to these workers by the master process as needed. pg_restore is adjusted to use this new infrastructure in place [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/03/26/2646/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.3 &#8211; Support writable foreign tables.</title>
		<link>http://www.depesz.com/2013/03/17/waiting-for-9-3-support-writable-foreign-tables/</link>
		<comments>http://www.depesz.com/2013/03/17/waiting-for-9-3-support-writable-foreign-tables/#comments</comments>
		<pubDate>Sun, 17 Mar 2013 21:40:41 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[data]]></category>
		<category><![CDATA[fdw]]></category>
		<category><![CDATA[foreign]]></category>
		<category><![CDATA[pg93]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[wfdw]]></category>
		<category><![CDATA[wrapper]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2638</guid>
		<description><![CDATA[On 10th of March, Tom Lane committed patch: Support writable foreign tables. &#160; This patch adds the core-system infrastructure needed to support updates on foreign tables, and extends contrib/postgres_fdw to allow updates against remote Postgres servers. There's still a great deal of room for improvement in optimization of remote updates, but at least there's basic [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/03/17/waiting-for-9-3-support-writable-foreign-tables/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.3 &#8211; Report pg_hba line number and contents when users fail to log in</title>
		<link>http://www.depesz.com/2013/03/12/waiting-for-9-3-report-pg_hba-line-number-and-contents-when-users-fail-to-log-in/</link>
		<comments>http://www.depesz.com/2013/03/12/waiting-for-9-3-report-pg_hba-line-number-and-contents-when-users-fail-to-log-in/#comments</comments>
		<pubDate>Tue, 12 Mar 2013 08:59:34 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[authentication]]></category>
		<category><![CDATA[fail]]></category>
		<category><![CDATA[ident]]></category>
		<category><![CDATA[logs]]></category>
		<category><![CDATA[md5]]></category>
		<category><![CDATA[peer]]></category>
		<category><![CDATA[pg93]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2635</guid>
		<description><![CDATA[On 10th of March, Magnus Hagander committed patch: Report pg_hba line number and contents when users fail to log in &#160; Instead of just reporting which user failed to log in, log both the line number in the active pg_hba.conf file (which may not match reality in case the file has been edited and not [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/03/12/waiting-for-9-3-report-pg_hba-line-number-and-contents-when-users-fail-to-log-in/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.3 &#8211; JSON generation improvements.</title>
		<link>http://www.depesz.com/2013/03/11/waiting-for-9-3-json-generation-improvements/</link>
		<comments>http://www.depesz.com/2013/03/11/waiting-for-9-3-json-generation-improvements/#comments</comments>
		<pubDate>Mon, 11 Mar 2013 12:17:56 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[aggregate]]></category>
		<category><![CDATA[hstore]]></category>
		<category><![CDATA[json]]></category>
		<category><![CDATA[pg93]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2632</guid>
		<description><![CDATA[On 10th of March, Andrew Dunstan committed patch: JSON generation improvements. &#160; This adds the following: &#160; json_agg(anyrecord) -&#62; json to_json(any) -&#62; json hstore_to_json(hstore) -&#62; json (also used as a cast) hstore_to_json_loose(hstore) -&#62; json &#160; The last provides heuristic treatment of numbers and booleans. &#160; Also, in json generation, if any non-builtin type has a [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/03/11/waiting-for-9-3-json-generation-improvements/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.3 &#8211; Provide database object names as separate fields in error messages.</title>
		<link>http://www.depesz.com/2013/03/07/waiting-for-9-3-provide-database-object-names-as-separate-fields-in-error-messages/</link>
		<comments>http://www.depesz.com/2013/03/07/waiting-for-9-3-provide-database-object-names-as-separate-fields-in-error-messages/#comments</comments>
		<pubDate>Thu, 07 Mar 2013 13:03:22 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[constraint]]></category>
		<category><![CDATA[context]]></category>
		<category><![CDATA[debugging]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[field]]></category>
		<category><![CDATA[pg93]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2630</guid>
		<description><![CDATA[Yet another missed thing for &#8220;Waiting for 9.3&#8243;. Sorry about that. On 29th of January, Tom Lane committed patch: Provide database object names as separate fields in error messages. &#160; This patch addresses the problem that applications currently have to extract object names from possibly-localized textual error messages, if they want to know for example [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/03/07/waiting-for-9-3-provide-database-object-names-as-separate-fields-in-error-messages/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Parallel dumping of databases</title>
		<link>http://www.depesz.com/2013/03/05/parallel-dumping-of-databases/</link>
		<comments>http://www.depesz.com/2013/03/05/parallel-dumping-of-databases/#comments</comments>
		<pubDate>Tue, 05 Mar 2013 14:45:08 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[cloning]]></category>
		<category><![CDATA[fast dump]]></category>
		<category><![CDATA[parallel]]></category>
		<category><![CDATA[pg_dump]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[snapshot]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2627</guid>
		<description><![CDATA[Some time ago I wrote a piece on speeding up dump/restore process using custom solution that was parallelizing process. Later on I wrote some tools (&#8220;fast dump and restore") to do it in more general way. But all of them had a problem &#8211; to get consistent dump you need to stop all concurrent access [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/03/05/parallel-dumping-of-databases/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.3 &#8211; Add a materialized view relations.</title>
		<link>http://www.depesz.com/2013/03/04/waiting-for-9-3-add-a-materialized-view-relations/</link>
		<comments>http://www.depesz.com/2013/03/04/waiting-for-9-3-add-a-materialized-view-relations/#comments</comments>
		<pubDate>Mon, 04 Mar 2013 14:33:02 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[materialized]]></category>
		<category><![CDATA[pg93]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[refresh]]></category>
		<category><![CDATA[view]]></category>
		<category><![CDATA[views]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2625</guid>
		<description><![CDATA[On 4th of March, Kevin Grittner committed patch: Add a materialized view relations. &#160; A materialized view has a rule just like a view and a heap and other physical properties like a table. The rule is only used to populate the table, references in queries refer to the materialized data. &#160; This is a [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/03/04/waiting-for-9-3-add-a-materialized-view-relations/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.3 &#8211; Add CREATE RECURSIVE VIEW syntax</title>
		<link>http://www.depesz.com/2013/03/04/waiting-for-9-3-add-create-recursive-view-syntax/</link>
		<comments>http://www.depesz.com/2013/03/04/waiting-for-9-3-add-create-recursive-view-syntax/#comments</comments>
		<pubDate>Mon, 04 Mar 2013 13:36:41 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[cte]]></category>
		<category><![CDATA[pg93]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[recursive]]></category>
		<category><![CDATA[view]]></category>
		<category><![CDATA[views]]></category>
		<category><![CDATA[with recursive]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2623</guid>
		<description><![CDATA[On 1st of February, Peter Eisentraut committed patch: Add CREATE RECURSIVE VIEW syntax &#160; This is specified in the SQL standard. The CREATE RECURSIVE VIEW specification is transformed into a normal CREATE VIEW statement with a WITH RECURSIVE clause. &#160; reviewed by Abhijit Menon-Sen and Stephen Frost It was committed quite some time ago, but [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/03/04/waiting-for-9-3-add-create-recursive-view-syntax/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.3 &#8211; Add support for piping COPY to/from an external program.</title>
		<link>http://www.depesz.com/2013/02/28/waiting-for-9-3-add-support-for-piping-copy-tofrom-an-external-program/</link>
		<comments>http://www.depesz.com/2013/02/28/waiting-for-9-3-add-support-for-piping-copy-tofrom-an-external-program/#comments</comments>
		<pubDate>Thu, 28 Feb 2013 13:30:43 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[copy]]></category>
		<category><![CDATA[pg93]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[program]]></category>
		<category><![CDATA[shell]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2621</guid>
		<description><![CDATA[On 27th of February, Heikki Linnakangas committed patch: Add support for piping COPY to/from an external program. &#160; This includes backend &#34;COPY TO/FROM PROGRAM '...'&#34; syntax, and corresponding psql \copy syntax. Like with reading/writing files, the backend version is superuser-only, and in the psql version, the program is run in the client. &#160; In the [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/02/28/waiting-for-9-3-add-support-for-piping-copy-tofrom-an-external-program/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Variables in SQL, what, how, when?</title>
		<link>http://www.depesz.com/2013/02/25/variables-in-sql-what-how-when/</link>
		<comments>http://www.depesz.com/2013/02/25/variables-in-sql-what-how-when/#comments</comments>
		<pubDate>Mon, 25 Feb 2013 15:04:11 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[global]]></category>
		<category><![CDATA[plperl]]></category>
		<category><![CDATA[plpgsql]]></category>
		<category><![CDATA[plpython]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>
		<category><![CDATA[session]]></category>
		<category><![CDATA[variable]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2608</guid>
		<description><![CDATA[One of the questions that gets asked quite a lot, is: how can you use variables in your queries? Other databases have them, does PostgreSQL? Actually the answer is &#8220;no". But, it is actually very easy to work around, and what's more important &#8211; quite often, what you need are not variables in queries, but [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/02/25/variables-in-sql-what-how-when/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.3 &#8211; Create a psql command \gset to store query results into psql variables</title>
		<link>http://www.depesz.com/2013/02/03/waiting-for-9-3-create-a-psql-command-gset-to-store-query-results-into-psql-variables/</link>
		<comments>http://www.depesz.com/2013/02/03/waiting-for-9-3-create-a-psql-command-gset-to-store-query-results-into-psql-variables/#comments</comments>
		<pubDate>Sun, 03 Feb 2013 14:38:03 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[gset]]></category>
		<category><![CDATA[pg93]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>
		<category><![CDATA[variables]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2605</guid>
		<description><![CDATA[On 2nd of February, Tom Lane committed patch: Create a psql command \gset to store query results into psql variables. &#160; This eases manipulation of query results in psql scripts. &#160; Pavel Stehule, reviewed by Piyush Newe, Shigeru Hanada, and Tom Lane psql is the basic client application / query tool for PostgreSQL. As such, [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/02/03/waiting-for-9-3-create-a-psql-command-gset-to-store-query-results-into-psql-variables/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Adding plans to explain.depesz.com from your psql</title>
		<link>http://www.depesz.com/2013/01/30/adding-plans-to-explain-depesz-com-from-your-psql/</link>
		<comments>http://www.depesz.com/2013/01/30/adding-plans-to-explain-depesz-com-from-your-psql/#comments</comments>
		<pubDate>Wed, 30 Jan 2013 15:04:52 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[explain.depesz.com]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2596</guid>
		<description><![CDATA[So, lately I have been thinking about integrating explain.depesz.com with psql. Currently, you have to run explain, copy the output, switch to webbrowser, go to explain.depesz.coma> site, paste output, click submit. It's not that it's a lot of work, but it can be simplified. To simplify it, we need just 2 minutes. First, you need [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/01/30/adding-plans-to-explain-depesz-com-from-your-psql/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Index on (a,b) vs. (b,a)?</title>
		<link>http://www.depesz.com/2013/01/28/index-on-ab-vs-ba/</link>
		<comments>http://www.depesz.com/2013/01/28/index-on-ab-vs-ba/#comments</comments>
		<pubDate>Mon, 28 Jan 2013 12:29:56 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[comparison]]></category>
		<category><![CDATA[index]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[selectivity]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2594</guid>
		<description><![CDATA[Whenever you are considering creation of multicolumn index, there is a question what should be the order of columns in this index. I'll try to analyze various cases of this situation. We need to consider two separate issues: what operators are you going to use What is selectivity of the fields First, let's consider that [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/01/28/index-on-ab-vs-ba/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.3 &#8211; pg_isready</title>
		<link>http://www.depesz.com/2013/01/26/waiting-for-9-3-pg_isready/</link>
		<comments>http://www.depesz.com/2013/01/26/waiting-for-9-3-pg_isready/#comments</comments>
		<pubDate>Sat, 26 Jan 2013 15:13:10 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[omniti]]></category>
		<category><![CDATA[pg93]]></category>
		<category><![CDATA[pgisready]]></category>
		<category><![CDATA[pgping]]></category>
		<category><![CDATA[pg_isready]]></category>
		<category><![CDATA[pg_ping]]></category>
		<category><![CDATA[phil]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[pqping]]></category>
		<category><![CDATA[pq_ping]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2592</guid>
		<description><![CDATA[On 23rd of January, Robert Haas committed patch: pg_isready &#160; New command-line utility to test whether a server is ready to accept connections. &#160; Phil Sorber, reviewed by Michael Paquier and Peter Eisentraut Disclaimer: Phil is my colleague in OmniTI In October 2012, Phil posted mail to pgsql-hackers mailing list where he attached first version [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2013/01/26/waiting-for-9-3-pg_isready/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Command line tools? In XXI century? No way! Yes way!</title>
		<link>http://www.depesz.com/2012/12/31/command-line-tools-in-xxi-century-no-way-yes-way/</link>
		<comments>http://www.depesz.com/2012/12/31/command-line-tools-in-xxi-century-no-way-yes-way/#comments</comments>
		<pubDate>Mon, 31 Dec 2012 16:34:54 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[cli]]></category>
		<category><![CDATA[console]]></category>
		<category><![CDATA[less]]></category>
		<category><![CDATA[pg_dump]]></category>
		<category><![CDATA[pg_restore]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>
		<category><![CDATA[terminal]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2589</guid>
		<description><![CDATA[So, you just installed your PostgreSQL, and you have no idea how to use it &#8211; there is no icon in the menu of your OS, so how can you use it? Well, with the dreadful command line. Of course &#8211; some people will never get used to textual programs. They need a GUI. That's [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2012/12/31/command-line-tools-in-xxi-century-no-way-yes-way/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.3 &#8211; Allow a streaming replication standby to follow a timeline switch.</title>
		<link>http://www.depesz.com/2012/12/22/waiting-for-9-3-allow-a-streaming-replication-standby-to-follow-a-timeline-switch/</link>
		<comments>http://www.depesz.com/2012/12/22/waiting-for-9-3-allow-a-streaming-replication-standby-to-follow-a-timeline-switch/#comments</comments>
		<pubDate>Sat, 22 Dec 2012 13:18:22 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[failover]]></category>
		<category><![CDATA[pg93]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[replication]]></category>
		<category><![CDATA[standby]]></category>
		<category><![CDATA[streaming]]></category>
		<category><![CDATA[timeline]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2587</guid>
		<description><![CDATA[On 13th of December, Heikki Linnakangas committed patch: Allow a streaming replication standby to follow a timeline switch. &#160; Before this patch, streaming replication would refuse to start replicating if the timeline in the primary doesn't exactly match the standby. The situation where it doesn't match is when you have a master, and two standbys, [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2012/12/22/waiting-for-9-3-allow-a-streaming-replication-standby-to-follow-a-timeline-switch/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.3 &#8211; Support automatically-updatable views.</title>
		<link>http://www.depesz.com/2012/12/11/waiting-for-9-3-support-automatically-updatable-views/</link>
		<comments>http://www.depesz.com/2012/12/11/waiting-for-9-3-support-automatically-updatable-views/#comments</comments>
		<pubDate>Tue, 11 Dec 2012 12:39:02 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[automatic]]></category>
		<category><![CDATA[delete]]></category>
		<category><![CDATA[insert]]></category>
		<category><![CDATA[pg93]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[rule]]></category>
		<category><![CDATA[rules]]></category>
		<category><![CDATA[update]]></category>
		<category><![CDATA[view]]></category>
		<category><![CDATA[views]]></category>
		<category><![CDATA[writable]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2585</guid>
		<description><![CDATA[On 8th of December, Tom Lane committed patch: Support automatically-updatable views. &#160; This patch makes &#34;simple&#34; views automatically updatable, without the need to create either INSTEAD OF triggers or INSTEAD rules. &#34;Simple&#34; views are those classified as updatable according to SQL-92 rules. The rewriter transforms INSERT/UPDATE/DELETE commands on such views directly into an equivalent command [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2012/12/11/waiting-for-9-3-support-automatically-updatable-views/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>CuTE overload</title>
		<link>http://www.depesz.com/2012/12/09/cute-overload/</link>
		<comments>http://www.depesz.com/2012/12/09/cute-overload/#comments</comments>
		<pubDate>Sun, 09 Dec 2012 19:11:33 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[cte]]></category>
		<category><![CDATA[cute]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[primer]]></category>
		<category><![CDATA[recursive]]></category>
		<category><![CDATA[wcte]]></category>
		<category><![CDATA[with]]></category>
		<category><![CDATA[with recursive]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2576</guid>
		<description><![CDATA[In PostgreSQL 8.4 we got CTE &#8211; Common Table Expressions. Since then we have this great tool available, but apparently for some people it's still black magic. CuTE, but still magic. I'll try to make it a bit less magical, and more understandable. The very basic way you can use CTE, is with query like: [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2012/12/09/cute-overload/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Waiting for 9.3 &#8211; Background worker processes</title>
		<link>http://www.depesz.com/2012/12/07/waiting-for-9-3-background-worker-processes/</link>
		<comments>http://www.depesz.com/2012/12/07/waiting-for-9-3-background-worker-processes/#comments</comments>
		<pubDate>Fri, 07 Dec 2012 13:34:06 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[asynchronous]]></category>
		<category><![CDATA[background]]></category>
		<category><![CDATA[pg93]]></category>
		<category><![CDATA[pgagent]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[worker_spi]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2580</guid>
		<description><![CDATA[On 6th of December, Alvaro Herrera committed patch: Background worker processes &#160; Background workers are postmaster subprocesses that run arbitrary user-specified code. They can request shared memory access as well as backend database connections; or they can just use plain libpq frontend database connections. &#160; Modules listed in shared_preload_libraries can register background workers in their [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2012/12/07/waiting-for-9-3-background-worker-processes/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
