<?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; context</title>
	<atom:link href="http://www.depesz.com/tag/context/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 9.2 &#8211; Stacked Diagnostics in PL/pgSQL</title>
		<link>http://www.depesz.com/2011/07/20/waiting-for-9-2-stacked-diagnostics-in-plpgsql/</link>
		<comments>http://www.depesz.com/2011/07/20/waiting-for-9-2-stacked-diagnostics-in-plpgsql/#comments</comments>
		<pubDate>Tue, 19 Jul 2011 23:47:45 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[context]]></category>
		<category><![CDATA[detail]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[exception]]></category>
		<category><![CDATA[hint]]></category>
		<category><![CDATA[pg92]]></category>
		<category><![CDATA[plpgsql]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[raise]]></category>
		<category><![CDATA[stack trace]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=2262</guid>
		<description><![CDATA[On 18th of July, Tom Lane committed patch: Add GET STACKED DIAGNOSTICS plpgsql command to retrieve exception info. &#160; This is more SQL-spec-compliant, more easily extensible, and better performing than the old method of inventing special variables. &#160; Pavel Stehule, reviewed by Shigeru Hanada and David Wheeler The problem that it solves is not very [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2011/07/20/waiting-for-9-2-stacked-diagnostics-in-plpgsql/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Suppressing CONTEXT lines in psql</title>
		<link>http://www.depesz.com/2008/07/12/suppressing-context-lines-in-psql/</link>
		<comments>http://www.depesz.com/2008/07/12/suppressing-context-lines-in-psql/#comments</comments>
		<pubDate>Sat, 12 Jul 2008 12:40:56 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[context]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>
		<category><![CDATA[psqlrc]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1219</guid>
		<description><![CDATA[CONTEXT messages are quite informative, but when you don&#8217;t need them, they can be real pain in the eyes: psql:trees.sql:68: NOTICE: Adding tree structures to table public.testit. CONTEXT: SQL function "add_tree_structure" statement 1 psql:trees.sql:68: NOTICE: Tree table will be public.testit_tree. CONTEXT: SQL function "add_tree_structure" statement 1 psql:trees.sql:68: NOTICE: Primary key in source table is: id [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/07/12/suppressing-context-lines-in-psql/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

