<?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>Michael Paquier &#187; PostgreSQL</title>
	<atom:link href="http://michael.otacoo.com/category/postgresql-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://michael.otacoo.com</link>
	<description>Open source developer based in Japan</description>
	<lastBuildDate>Wed, 22 May 2013 18:28:32 +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>Postgres 9.3 feature highlight: new verbose error fields</title>
		<link>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-new-verbose-error-fields/</link>
		<comments>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-new-verbose-error-fields/#comments</comments>
		<pubDate>Wed, 22 May 2013 18:28:32 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[PostgreSQL]]></category>
		<category><![CDATA[9.3]]></category>
		<category><![CDATA[additional]]></category>
		<category><![CDATA[client]]></category>
		<category><![CDATA[column]]></category>
		<category><![CDATA[constraint]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[feature]]></category>
		<category><![CDATA[field]]></category>
		<category><![CDATA[highlight]]></category>
		<category><![CDATA[improvement]]></category>
		<category><![CDATA[new]]></category>
		<category><![CDATA[number]]></category>
		<category><![CDATA[postgres]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>
		<category><![CDATA[table]]></category>
		<category><![CDATA[type]]></category>

		<guid isPermaLink="false">http://michael.otacoo.com/?p=1904</guid>
		<description><![CDATA[PostgreSQL is already pretty useful for application developers when returning to client error messages by providing a certain level of details with multiple distinct fields like the position of the code where the error occurred. However this was lacking with the database object names, forcing the client application to deparse the error string returned by <a href='http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-new-verbose-error-fields/'>[...]</a>]]></description>
		<wfw:commentRss>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-new-verbose-error-fields/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Postgres 9.3 feature highlight: new flavors of IF EXISTS and IF NOT EXISTS</title>
		<link>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-new-flavors-of-if-exists-and-if-not-exists/</link>
		<comments>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-new-flavors-of-if-exists-and-if-not-exists/#comments</comments>
		<pubDate>Wed, 15 May 2013 11:51:07 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[PostgreSQL]]></category>
		<category><![CDATA[9.3]]></category>
		<category><![CDATA[alter]]></category>
		<category><![CDATA[create]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[DDL]]></category>
		<category><![CDATA[drop]]></category>
		<category><![CDATA[existence]]></category>
		<category><![CDATA[function]]></category>
		<category><![CDATA[if exists]]></category>
		<category><![CDATA[if not exists]]></category>
		<category><![CDATA[language]]></category>
		<category><![CDATA[object]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[operator]]></category>
		<category><![CDATA[postgres]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[role]]></category>
		<category><![CDATA[table]]></category>
		<category><![CDATA[trigger]]></category>
		<category><![CDATA[user]]></category>

		<guid isPermaLink="false">http://michael.otacoo.com/?p=1889</guid>
		<description><![CDATA[IF EXISTS and IF NOT EXISTS are clauses allowing to return a notice message instead of an error if a DDL query running on a given object already exists or not depending on the DDL action done. If a given query tries to create an object when IF NOT EXISTS is specified, a notice message <a href='http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-new-flavors-of-if-exists-and-if-not-exists/'>[...]</a>]]></description>
		<wfw:commentRss>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-new-flavors-of-if-exists-and-if-not-exists/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Looking at the roots of Postgres: configure processing</title>
		<link>http://michael.otacoo.com/postgresql-2/looking-at-the-roots-of-postgres-configure-processing/</link>
		<comments>http://michael.otacoo.com/postgresql-2/looking-at-the-roots-of-postgres-configure-processing/#comments</comments>
		<pubDate>Thu, 09 May 2013 06:14:47 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[PostgreSQL]]></category>
		<category><![CDATA[autoconf]]></category>
		<category><![CDATA[basic]]></category>
		<category><![CDATA[configure]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[db]]></category>
		<category><![CDATA[dependency]]></category>
		<category><![CDATA[environment]]></category>
		<category><![CDATA[library]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[operating system]]></category>
		<category><![CDATA[os]]></category>
		<category><![CDATA[package]]></category>
		<category><![CDATA[postgres]]></category>
		<category><![CDATA[processing]]></category>
		<category><![CDATA[root]]></category>

		<guid isPermaLink="false">http://michael.otacoo.com/?p=1882</guid>
		<description><![CDATA[Before launching make for a raw build, Postgres does some preprocessing with configure to setup the installation based on the environment and the different options given by user. If you don&#8217;t do that before trying a make, your build will fail with a critical hit of this type: $ make You need to run the <a href='http://michael.otacoo.com/postgresql-2/looking-at-the-roots-of-postgres-configure-processing/'>[...]</a>]]></description>
		<wfw:commentRss>http://michael.otacoo.com/postgresql-2/looking-at-the-roots-of-postgres-configure-processing/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Postgres 9.3 feature highlight: \watch in psql</title>
		<link>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-watch-in-psql/</link>
		<comments>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-watch-in-psql/#comments</comments>
		<pubDate>Thu, 02 May 2013 05:01:04 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[PostgreSQL]]></category>
		<category><![CDATA[9.3]]></category>
		<category><![CDATA[client]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[interval]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[postgres]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[psql]]></category>
		<category><![CDATA[query]]></category>
		<category><![CDATA[relational]]></category>
		<category><![CDATA[repeat]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[watch]]></category>

		<guid isPermaLink="false">http://michael.otacoo.com/?p=1870</guid>
		<description><![CDATA[psql is the native client of PostgreSQL widely used by application developers and database administrators on a daily-basis for common operations when interacting with a PostgreSQL server. With a full set of integrated functionalities, it is among the most popular (if not the number one) client applications in the Postgres community. If you are a <a href='http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-watch-in-psql/'>[...]</a>]]></description>
		<wfw:commentRss>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-watch-in-psql/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Postgres 9.3 feature highlight: parallel pg_dump</title>
		<link>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-parallel-pg_dump/</link>
		<comments>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-parallel-pg_dump/#comments</comments>
		<pubDate>Thu, 25 Apr 2013 00:01:43 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[PostgreSQL]]></category>
		<category><![CDATA[9.3]]></category>
		<category><![CDATA[compression]]></category>
		<category><![CDATA[data]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[dump]]></category>
		<category><![CDATA[folder]]></category>
		<category><![CDATA[job]]></category>
		<category><![CDATA[object]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[parallel]]></category>
		<category><![CDATA[pg_dump]]></category>
		<category><![CDATA[postgres]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[restore]]></category>
		<category><![CDATA[table]]></category>

		<guid isPermaLink="false">http://michael.otacoo.com/?p=1849</guid>
		<description><![CDATA[Among one of the many new features implemented in 9.3, pg_dump now offers the possibility to perform parallel dumps. This feature has been introduced by the commit below. commit 9e257a181cc1dc5e19eb5d770ce09cc98f470f5f Author: Andrew Dunstan Date: Sun Mar 24 11:27:20 2013 -0400 　 Add parallel pg_dump option. 　 New infrastructure is added which creates a set number <a href='http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-parallel-pg_dump/'>[...]</a>]]></description>
		<wfw:commentRss>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-parallel-pg_dump/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Postgres 9.3 feature highlight: JSON parsing functions</title>
		<link>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-json-parsing-functions/</link>
		<comments>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-json-parsing-functions/#comments</comments>
		<pubDate>Wed, 17 Apr 2013 16:30:29 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[PostgreSQL]]></category>
		<category><![CDATA[9.3]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[array]]></category>
		<category><![CDATA[cut]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[deparsing]]></category>
		<category><![CDATA[function]]></category>
		<category><![CDATA[json]]></category>
		<category><![CDATA[key]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[parsing]]></category>
		<category><![CDATA[postgres]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[record]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[set]]></category>
		<category><![CDATA[side]]></category>
		<category><![CDATA[value]]></category>

		<guid isPermaLink="false">http://michael.otacoo.com/?p=1836</guid>
		<description><![CDATA[Continuing on the coverage of new JSON features added in Postgres 9.3, and after writing about JSON data generation and JSON operators, let&#8217;s now focus on some new functions that can be used for the parsing of JSON data. The are many new functions introduced: json_each, json_each_text json_extract_path, json_extract_path_text json_object_keys json_populate_record, json_populate_recordset json_array_length json_array_elements The <a href='http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-json-parsing-functions/'>[...]</a>]]></description>
		<wfw:commentRss>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-json-parsing-functions/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Postgres 9.3 feature highlight: JSON operators</title>
		<link>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-json-operators/</link>
		<comments>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-json-operators/#comments</comments>
		<pubDate>Thu, 11 Apr 2013 05:52:51 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[PostgreSQL]]></category>
		<category><![CDATA[9.3]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[data]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[feature]]></category>
		<category><![CDATA[function]]></category>
		<category><![CDATA[json]]></category>
		<category><![CDATA[manipulation]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[operator]]></category>
		<category><![CDATA[postgres]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[read]]></category>
		<category><![CDATA[write]]></category>

		<guid isPermaLink="false">http://michael.otacoo.com/?p=1812</guid>
		<description><![CDATA[Postgres 9.3 is going to be a great release for JSON data type. After having a look at the new functions for data generation, let&#8217;s look at the new JSON features that the commit below brings. commit a570c98d7fa0841f17bbf51d62d02d9e493c7fcc Author: Andrew Dunstan Date: Fri Mar 29 14:12:13 2013 -0400 　 Add new JSON processing functions and <a href='http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-json-operators/'>[...]</a>]]></description>
		<wfw:commentRss>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-json-operators/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Postgres 9.3 feature highlight: JSON data generation</title>
		<link>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-json-data-generation/</link>
		<comments>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-json-data-generation/#comments</comments>
		<pubDate>Wed, 03 Apr 2013 14:29:21 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[PostgreSQL]]></category>
		<category><![CDATA[9.3]]></category>
		<category><![CDATA[data]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[enhancement]]></category>
		<category><![CDATA[feature]]></category>
		<category><![CDATA[function]]></category>
		<category><![CDATA[improvement]]></category>
		<category><![CDATA[json]]></category>
		<category><![CDATA[leverage]]></category>
		<category><![CDATA[light]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[operation]]></category>
		<category><![CDATA[operator]]></category>
		<category><![CDATA[postgres]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[site]]></category>
		<category><![CDATA[store]]></category>
		<category><![CDATA[type]]></category>
		<category><![CDATA[value]]></category>
		<category><![CDATA[web]]></category>
		<category><![CDATA[website]]></category>

		<guid isPermaLink="false">http://michael.otacoo.com/?p=1799</guid>
		<description><![CDATA[Postgres 9.2 has introduced JSON as a server data type. At this point, the data was simply stored on server side with integrated wrappers checking that data had a correct JSON format. It was a good first step in order to store directly JSON data on server side but core features in 9.2 have its <a href='http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-json-data-generation/'>[...]</a>]]></description>
		<wfw:commentRss>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-json-data-generation/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Postgres 9.3 feature highlight: handling signals with custom bgworkers</title>
		<link>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-handling-signals-with-custom-bgworkers/</link>
		<comments>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-handling-signals-with-custom-bgworkers/#comments</comments>
		<pubDate>Thu, 28 Mar 2013 03:13:01 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[PostgreSQL]]></category>
		<category><![CDATA[9.3]]></category>
		<category><![CDATA[background]]></category>
		<category><![CDATA[bgworker]]></category>
		<category><![CDATA[control]]></category>
		<category><![CDATA[custom]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[example]]></category>
		<category><![CDATA[github]]></category>
		<category><![CDATA[handling]]></category>
		<category><![CDATA[latch]]></category>
		<category><![CDATA[latency]]></category>
		<category><![CDATA[log]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[pg_workers]]></category>
		<category><![CDATA[postgres]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[postmaster]]></category>
		<category><![CDATA[project]]></category>
		<category><![CDATA[shared memory]]></category>
		<category><![CDATA[sighup]]></category>
		<category><![CDATA[signal]]></category>
		<category><![CDATA[sigterm]]></category>
		<category><![CDATA[worker]]></category>

		<guid isPermaLink="false">http://michael.otacoo.com/?p=1787</guid>
		<description><![CDATA[Similarly to a normal PostgreSQL child process, a custom background worker should be running using a loop that can be interrupted with signals to update a given status or simply exit the process. Two types of signals are handled by custom background workers in the PostgreSQL architecture: SIGHUP and SIGTERM. When such signals are received <a href='http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-handling-signals-with-custom-bgworkers/'>[...]</a>]]></description>
		<wfw:commentRss>http://michael.otacoo.com/postgresql-2/postgres-9-3-feature-highlight-handling-signals-with-custom-bgworkers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hooks in Postgres: super-superuser restrictions</title>
		<link>http://michael.otacoo.com/postgresql-2/hooks-in-postgres-super-superuser-restrictions/</link>
		<comments>http://michael.otacoo.com/postgresql-2/hooks-in-postgres-super-superuser-restrictions/#comments</comments>
		<pubDate>Thu, 21 Mar 2013 03:05:27 +0000</pubDate>
		<dc:creator>Michael</dc:creator>
				<category><![CDATA[PostgreSQL]]></category>
		<category><![CDATA[awesome]]></category>
		<category><![CDATA[background]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[executor]]></category>
		<category><![CDATA[extension]]></category>
		<category><![CDATA[hook]]></category>
		<category><![CDATA[module]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[postgres]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[tool]]></category>
		<category><![CDATA[utility]]></category>
		<category><![CDATA[worker]]></category>

		<guid isPermaLink="false">http://michael.otacoo.com/?p=1761</guid>
		<description><![CDATA[PostgreSQL extensibility is awesome. With things like extensions or custom worker backgrounds, there are many ways for a PostgreSQL developer to create modules without having to touch a single line of the core code at all. Among those tools, PostgreSQL contains a set of hooks that can be used to plug customized code at certain <a href='http://michael.otacoo.com/postgresql-2/hooks-in-postgres-super-superuser-restrictions/'>[...]</a>]]></description>
		<wfw:commentRss>http://michael.otacoo.com/postgresql-2/hooks-in-postgres-super-superuser-restrictions/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
