<?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; raise</title>
	<atom:link href="http://www.depesz.com/tag/raise/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>Waiting for 8.4 &#8211; pl/PgSQL RAISE</title>
		<link>http://www.depesz.com/2008/05/14/waiting-for-84-plpgsql-raise/</link>
		<comments>http://www.depesz.com/2008/05/14/waiting-for-84-plpgsql-raise/#comments</comments>
		<pubDate>Wed, 14 May 2008 16:01:20 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[pg84]]></category>
		<category><![CDATA[plpgsql]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[raise]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1205</guid>
		<description><![CDATA[Today we have one new feature &#8211; extension of plpgsql&#8217;s RAISE command. Patch was written by Pavel Stehule and Tom Lane, and committed by Tom. Commit log: Improve plpgsql's RAISE command. It is now possible to attach DETAIL and HINT fields to a user-thrown error message, and to specify the SQLSTATE error code to use. [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/05/14/waiting-for-84-plpgsql-raise/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

