<?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; pg83</title>
	<atom:link href="http://www.depesz.com/tag/pg83/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>&#8220;ERROR:  operator does not exist: integer = text&#8221; how to fix it?</title>
		<link>http://www.depesz.com/2008/05/05/error-operator-does-not-exist-integer-text-how-to-fix-it/</link>
		<comments>http://www.depesz.com/2008/05/05/error-operator-does-not-exist-integer-text-how-to-fix-it/#comments</comments>
		<pubDate>Mon, 05 May 2008 11:11:31 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[cast]]></category>
		<category><![CDATA[implicit]]></category>
		<category><![CDATA[pg83]]></category>
		<category><![CDATA[postgresql]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1201</guid>
		<description><![CDATA[PostgreSQL 8.3 brought us many great new features. Among them were concurrent autovacuum, enums, tsearch in core. On of the changes though made a lot of people dislike 8.3. It was removal of implicit casts. What do I mean? In PostgreSQL 8.2, You could easily do something like this: # select 1::int4 = '1'::text; ?column? [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/05/05/error-operator-does-not-exist-integer-text-how-to-fix-it/feed/</wfw:commentRss>
		<slash:comments>15</slash:comments>
		</item>
		<item>
		<title>Polish TSearch in 8.3 (polski tsearch w postgresie 8.3)</title>
		<link>http://www.depesz.com/2008/04/22/polish-tsearch-in-83-polski-tsearch-w-postgresie-83/</link>
		<comments>http://www.depesz.com/2008/04/22/polish-tsearch-in-83-polski-tsearch-w-postgresie-83/#comments</comments>
		<pubDate>Tue, 22 Apr 2008 16:30:44 +0000</pubDate>
		<dc:creator>depesz</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[pg83]]></category>
		<category><![CDATA[polish]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[tsearch]]></category>

		<guid isPermaLink="false">http://www.depesz.com/?p=1195</guid>
		<description><![CDATA[English disclaimer: this post will be in Polish only, as it&#8217;s use for other nationalities is somehow limited jakiś czas temu pisałem jak skonfigurować polskiego tsearcha pod postgresem 8.2. od tamtej pory trochę się zmieniło, pojawił się 8.3, w którym tsearch jest wbudowany w bazowego postgresa, więc instalacja jest prostsza. zakładam, że postgres jest skonfigurowany [...]]]></description>
		<wfw:commentRss>http://www.depesz.com/2008/04/22/polish-tsearch-in-83-polski-tsearch-w-postgresie-83/feed/</wfw:commentRss>
		<slash:comments>32</slash:comments>
		</item>
	</channel>
</rss>

