<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.postgresql.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Umitanuki</id>
	<title>PostgreSQL wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.postgresql.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Umitanuki"/>
	<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/wiki/Special:Contributions/Umitanuki"/>
	<updated>2026-06-09T17:52:18Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.17</generator>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=PL_Matrix&amp;diff=18700</id>
		<title>PL Matrix</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=PL_Matrix&amp;diff=18700"/>
		<updated>2012-12-12T08:26:32Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is an attempt to document all the available Procedural Language Handlers for PostgreSQL.&lt;br /&gt;
&#039;&#039;WARNING:&#039;&#039; The information presented here is still very much experimental and guaranteed to be out-of-date ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; cellspacing=&amp;quot;0&amp;quot; style=&amp;quot;font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%; table-layout: fixed;&amp;quot; &lt;br /&gt;
|- style=&amp;quot;background: #ececec&amp;quot;&lt;br /&gt;
! style=&amp;quot;width:16em&amp;quot; | Language&lt;br /&gt;
! Status&lt;br /&gt;
! Availability&lt;br /&gt;
! Named Parameters?&lt;br /&gt;
! OUT Parameters?&lt;br /&gt;
! (Un)Trusted&lt;br /&gt;
! Notes&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/pgsql&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | in core&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Trusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | compiled by default&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | sql&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | in core&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | yes (version 9.2+)&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Trusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | available by default&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/perl&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | in core&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Trusted and Untrusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/python&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | in core&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | support for one OUT parameter from 8.4, multiple from 9.1&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Untrusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/tcl&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | in core&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Trusted and Untrusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | PL/sh&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://plsh.projects.postgresql.org/ PL/sh]&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | no (not useful)&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Untrusted necessarily&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; |&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | PL/R&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://joeconway.com/plr/ PL/R]&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Untrusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/java&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://pgfoundry.org/projects/pljava/ pl/java]&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/js&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://xen.samason.me.uk/~sam/repos/pljs/ pl/js]&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/lolcode&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://pllolcode.projects.postgresql.org/ pl/lolcode]&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; |&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/scheme&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://plscheme.projects.postgresql.org/ pl/scheme]&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Trusted and Untrusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/php&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | Beta&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://projects.commandprompt.com/public/plphp pl/php]&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | Yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; |&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/ruby&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://raa.ruby-lang.org/project/pl-ruby pl/ruby]&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; |&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/j&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://plj.codehaus.org/ pl/j]&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; |&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/lua&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | Alpha&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://pllua.projects.postgresql.org/ pl/lua]&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Trusted and Untrusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/pgpsm&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Beta&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://www.pgsql.cz/index.php/SQL/PSM  pl/pgpsm]&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | SQL/PSM implementation based on pl/pgsql runtime&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/v8&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://code.google.com/p/plv8js/  pl/v8js]&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Trusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Note: For all languages, it is allowed to place parameter names in the function parameter list declaration.  What the &#039;&#039;&#039;Named Parameters&#039;&#039;&#039; column is about is whether the body of the function can refer to the parameters by those names, or whether it has to use some other notation, such as &#039;&#039;$1&#039;&#039;, &#039;&#039;$2&#039;&#039;, etc.&lt;br /&gt;
&lt;br /&gt;
Note: All languages support parameters that are explicitly marked as IN parameters.  Those that support OUT parameters also automatically handle INOUT parameters.&lt;br /&gt;
&lt;br /&gt;
[[Category:Languages]]&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=PL_Matrix&amp;diff=18699</id>
		<title>PL Matrix</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=PL_Matrix&amp;diff=18699"/>
		<updated>2012-12-12T08:25:17Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is an attempt to document all the available Procedural Language Handlers for PostgreSQL.&lt;br /&gt;
&#039;&#039;WARNING:&#039;&#039; The information presented here is still very much experimental and guaranteed to be out-of-date ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; cellspacing=&amp;quot;0&amp;quot; style=&amp;quot;font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%; table-layout: fixed;&amp;quot; &lt;br /&gt;
|- style=&amp;quot;background: #ececec&amp;quot;&lt;br /&gt;
! style=&amp;quot;width:16em&amp;quot; | Language&lt;br /&gt;
! Status&lt;br /&gt;
! Availability&lt;br /&gt;
! Named Parameters?&lt;br /&gt;
! OUT Parameters?&lt;br /&gt;
! (Un)Trusted&lt;br /&gt;
! Notes&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/pgsql&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | in core&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Trusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | compiled by default&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | sql&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | in core&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | yes (version 9.2+)&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Trusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | available by default&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/perl&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | in core&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Trusted and Untrusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/python&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | in core&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | support for one OUT parameter from 8.4, multiple from 9.1&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Untrusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/tcl&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | in core&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Trusted and Untrusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | PL/sh&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://plsh.projects.postgresql.org/ PL/sh]&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | no (not useful)&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Untrusted necessarily&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; |&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | PL/R&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://joeconway.com/plr/ PL/R]&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Untrusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/java&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://pgfoundry.org/projects/pljava/ pl/java]&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/js&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://xen.samason.me.uk/~sam/repos/pljs/ pl/js]&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/lolcode&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://pllolcode.projects.postgresql.org/ pl/lolcode]&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; |&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/scheme&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://plscheme.projects.postgresql.org/ pl/scheme]&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Trusted and Untrusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/php&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | Beta&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://projects.commandprompt.com/public/plphp pl/php]&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | Yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; |&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/ruby&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://raa.ruby-lang.org/project/pl-ruby pl/ruby]&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; |&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/j&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://plj.codehaus.org/ pl/j]&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; |&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/lua&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | Alpha&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://pllua.projects.postgresql.org/ pl/lua]&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Trusted and Untrusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/pgpsm&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Beta&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://www.pgsql.cz/index.php/SQL/PSM  pl/pgpsm]&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | SQL/PSM implementation based on pl/pgsql runtime&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/v8&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Beta&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://code.google.com/p/plv8js/  pl/v8js]&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Trusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Note: For all languages, it is allowed to place parameter names in the function parameter list declaration.  What the &#039;&#039;&#039;Named Parameters&#039;&#039;&#039; column is about is whether the body of the function can refer to the parameters by those names, or whether it has to use some other notation, such as &#039;&#039;$1&#039;&#039;, &#039;&#039;$2&#039;&#039;, etc.&lt;br /&gt;
&lt;br /&gt;
Note: All languages support parameters that are explicitly marked as IN parameters.  Those that support OUT parameters also automatically handle INOUT parameters.&lt;br /&gt;
&lt;br /&gt;
[[Category:Languages]]&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=PL_Matrix&amp;diff=16406</id>
		<title>PL Matrix</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=PL_Matrix&amp;diff=16406"/>
		<updated>2012-03-18T05:11:35Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is an attempt to document all the available Procedural Language Handlers for PostgreSQL.&lt;br /&gt;
&#039;&#039;WARNING:&#039;&#039; The information presented here is still very much experimental and guaranteed to be out-of-date ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; cellspacing=&amp;quot;0&amp;quot; style=&amp;quot;font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 100%; table-layout: fixed;&amp;quot; &lt;br /&gt;
|- style=&amp;quot;background: #ececec&amp;quot;&lt;br /&gt;
! style=&amp;quot;width:16em&amp;quot; | Language&lt;br /&gt;
! Status&lt;br /&gt;
! Availability&lt;br /&gt;
! Named Parameters?&lt;br /&gt;
! OUT Parameters?&lt;br /&gt;
! (Un)Trusted&lt;br /&gt;
! Notes&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/pgsql&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | in core&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | compiled by default&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | sql&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | in core&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | available by default&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/perl&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | in core&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Trusted and Untrusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/python&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | in core&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | support for one OUT parameter from 8.4, multiple from 9.1&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Untrusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/tcl&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | in core&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Trusted and Untrusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | PL/sh&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://plsh.projects.postgresql.org/ PL/sh]&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | no (not useful)&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Untrusted necessarily&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; |&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | PL/R&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://joeconway.com/plr/ PL/R]&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffdddd&amp;quot; | no&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Untrusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/java&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://pgfoundry.org/projects/pljava/ pl/java]&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/js&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://xen.samason.me.uk/~sam/repos/pljs/ pl/js]&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/lolcode&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://pllolcode.projects.postgresql.org/ pl/lolcode]&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; |&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/scheme&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Production&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://plscheme.projects.postgresql.org/ pl/scheme]&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Trusted and Untrusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/php&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | Beta&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://projects.commandprompt.com/public/plphp pl/php]&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | Yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; |&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/ruby&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://raa.ruby-lang.org/project/pl-ruby pl/ruby]&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; |&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/j&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://plj.codehaus.org/ pl/j]&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; |&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/lua&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | Alpha&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://pllua.projects.postgresql.org/ pl/lua]&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Trusted and Untrusted&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/pgpsm&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Beta&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://www.pgsql.cz/index.php/SQL/PSM  pl/pgpsm]&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | SQL/PSM implementation based on pl/pgsql runtime&lt;br /&gt;
|-&lt;br /&gt;
! style=&amp;quot;text-align:block;&amp;quot; bgcolor=&amp;quot;#ececec&amp;quot; | pl/v8&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | Beta&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | [http://code.google.com/p/plv8js/  pl/v8js]&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | yes&lt;br /&gt;
| bgcolor=&amp;quot;#ffffaa&amp;quot; | ?&lt;br /&gt;
| bgcolor=&amp;quot;#ddffdd&amp;quot; | &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Note: For all languages, it is allowed to place parameter names in the function parameter list declaration.  What the &#039;&#039;&#039;Named Parameters&#039;&#039;&#039; column is about is whether the body of the function can refer to the parameters by those names, or whether it has to use some other notation, such as &#039;&#039;$1&#039;&#039;, &#039;&#039;$2&#039;&#039;, etc.&lt;br /&gt;
&lt;br /&gt;
Note: All languages support parameters that are explicitly marked as IN parameters.  Those that support OUT parameters also automatically handle INOUT parameters.&lt;br /&gt;
&lt;br /&gt;
[[Category:Languages]]&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=12375</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=12375"/>
		<updated>2010-11-06T12:01:20Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* General Rules */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add &amp;quot;(INSERT | UPDATE | DELETE) .. [RETURNING ..]&amp;quot; to CTEs(Common Table Expressions), both in the WITH clause and the top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH with_query [, ...]&lt;br /&gt;
        plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( plannable_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( select | insert | update | delete )&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;DML&lt;br /&gt;
:An INSERT, DELETE, or UPDATE statement.&lt;br /&gt;
&lt;br /&gt;
;Derived table&lt;br /&gt;
:A temporary table (set of tuples) returned by table expressions.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* Top level DML WITH clauses are executed as written. The snapshot is updated on each execution. Thus, query below returns different numbers.&lt;br /&gt;
    WITH t1 AS (SELECT count(*) FROM x),&lt;br /&gt;
         t2 AS (DELETE FROM x),&lt;br /&gt;
         t3 AS (SELECT count(*) FROM x)&lt;br /&gt;
    SELECT t1.count, t3.count FROM t1, t3;&lt;br /&gt;
* RECURSIVE modifier is not allowed, since forward reference between common table expressions are not allowed to keep execution order.&lt;br /&gt;
* DMLs are executed as separated plans.&lt;br /&gt;
* DMLs in WITH clause can refer to only other table expressions that precedes to it as literally specified. This behavior is the same as normal SELECT CTEs. For example:&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this should work&lt;br /&gt;
    WITH t1 AS(DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this should raise error&lt;br /&gt;
    WITH t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *),&lt;br /&gt;
    t1 AS(DELETE FROM src RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
* Triggers should work in each statement as it does for individual top level statement.&lt;br /&gt;
* You cannot CREATE VIEW on wCTEs query. This restriction may be removed in the future.&lt;br /&gt;
* It is allowed to put DMLs without RETURING clause in WITH, but it is forbidden to refer to that derived table.&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this is ok&lt;br /&gt;
    WITH t1 AS(DELETE FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this raises an error&lt;br /&gt;
    WITH t1 AS(DELETE FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t1;&lt;br /&gt;
* DMLs in WITH clause are allowed only in the top-level WITH.&lt;br /&gt;
    -- raise an error&lt;br /&gt;
    SELECT * FROM(WITH t1 AS(DELETE FROM src) SELECT * FROM t1)s;&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItem|Fix snapshot taking inconsistencies}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow DMLs inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Refactor executors for normal execution, EXPLAIN ANALYZE, SQL language functions and SPI to:|&lt;br /&gt;
* save the results of a certain PlannedStmt&lt;br /&gt;
* maintain a list of those results}}&lt;br /&gt;
{{TodoItemDone|Allow the &amp;quot;main query&amp;quot; to be DMLs|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
* Move rows from src to dest, and return them immediately.&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
&lt;br /&gt;
These are only memoranda or references...&lt;br /&gt;
&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;br /&gt;
&lt;br /&gt;
== Compatibility ==&lt;br /&gt;
&lt;br /&gt;
Because RETURNING clause on DMLs is PostgreSQL&#039;s extension, writeable CTEs is not in the current standard. However, SQL 2011 possibly mentions about Delta Table, which might be similar to Writeable CTEs.&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=12374</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=12374"/>
		<updated>2010-11-06T11:57:23Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add &amp;quot;(INSERT | UPDATE | DELETE) .. [RETURNING ..]&amp;quot; to CTEs(Common Table Expressions), both in the WITH clause and the top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH with_query [, ...]&lt;br /&gt;
        plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( plannable_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( select | insert | update | delete )&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;DML&lt;br /&gt;
:An INSERT, DELETE, or UPDATE statement.&lt;br /&gt;
&lt;br /&gt;
;Derived table&lt;br /&gt;
:A temporary table (set of tuples) returned by table expressions.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* Top level DML WITH clauses are executed as written. The snapshot is updated on each execution. Thus, query below returns different numbers.&lt;br /&gt;
    WITH t1 AS (SELECT count(*) FROM x),&lt;br /&gt;
         t2 AS (DELETE FROM x),&lt;br /&gt;
         t3 AS (SELECT count(*) FROM x)&lt;br /&gt;
    SELECT t1.count, t3.count FROM t1, t3;&lt;br /&gt;
* RECURSIVE modifier is not allowed, since forward reference between common table expressions are not allowed to keep execution order.&lt;br /&gt;
* DMLs are executed as separated plans.&lt;br /&gt;
* DMLs in WITH clause can refer to only other table expressions that precedes to it as literally specified. This behavior is the same as normal SELECT CTEs. For example:&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this should work&lt;br /&gt;
    WITH t1 AS(DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this should raise error&lt;br /&gt;
    WITH t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *),&lt;br /&gt;
    t1 AS(DELETE FROM src RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
* Triggers should work in each statement as it does for individual top level statement.&lt;br /&gt;
* You cannot CREATE VIEW on wCTEs query.&lt;br /&gt;
* It is allowed to put DMLs without RETURING clause in WITH, but it is forbidden to refer to that derived table.&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this is ok&lt;br /&gt;
    WITH t1 AS(DELETE FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this raises an error&lt;br /&gt;
    WITH t1 AS(DELETE FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t1;&lt;br /&gt;
* DMLs in WITH clause are allowed only in the top-level WITH.&lt;br /&gt;
    -- raise an error&lt;br /&gt;
    SELECT * FROM(WITH t1 AS(DELETE FROM src) SELECT * FROM t1)s;&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItem|Fix snapshot taking inconsistencies}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow DMLs inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Refactor executors for normal execution, EXPLAIN ANALYZE, SQL language functions and SPI to:|&lt;br /&gt;
* save the results of a certain PlannedStmt&lt;br /&gt;
* maintain a list of those results}}&lt;br /&gt;
{{TodoItemDone|Allow the &amp;quot;main query&amp;quot; to be DMLs|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
* Move rows from src to dest, and return them immediately.&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
&lt;br /&gt;
These are only memoranda or references...&lt;br /&gt;
&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;br /&gt;
&lt;br /&gt;
== Compatibility ==&lt;br /&gt;
&lt;br /&gt;
Because RETURNING clause on DMLs is PostgreSQL&#039;s extension, writeable CTEs is not in the current standard. However, SQL 2011 possibly mentions about Delta Table, which might be similar to Writeable CTEs.&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=12373</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=12373"/>
		<updated>2010-11-06T11:55:07Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* Overview */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add &amp;quot;(INSERT | UPDATE | DELETE) .. [RETURNING ..]&amp;quot; to CTEs(Common Table Expressions), both in the WITH clause and the top-level statement.&lt;br /&gt;
&lt;br /&gt;
SQL 2011 possibly mentions about Delta Table, which might be similar to Writeable CTEs.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH with_query [, ...]&lt;br /&gt;
        plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( plannable_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( select | insert | update | delete )&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;DML&lt;br /&gt;
:An INSERT, DELETE, or UPDATE statement.&lt;br /&gt;
&lt;br /&gt;
;Derived table&lt;br /&gt;
:A temporary table (set of tuples) returned by table expressions.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* Top level DML WITH clauses are executed as written. The snapshot is updated on each execution. Thus, query below returns different numbers.&lt;br /&gt;
    WITH t1 AS (SELECT count(*) FROM x),&lt;br /&gt;
         t2 AS (DELETE FROM x),&lt;br /&gt;
         t3 AS (SELECT count(*) FROM x)&lt;br /&gt;
    SELECT t1.count, t3.count FROM t1, t3;&lt;br /&gt;
* RECURSIVE modifier is not allowed, since forward reference between common table expressions are not allowed to keep execution order.&lt;br /&gt;
* DMLs are executed as separated plans.&lt;br /&gt;
* DMLs in WITH clause can refer to only other table expressions that precedes to it as literally specified. This behavior is the same as normal SELECT CTEs. For example:&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this should work&lt;br /&gt;
    WITH t1 AS(DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this should raise error&lt;br /&gt;
    WITH t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *),&lt;br /&gt;
    t1 AS(DELETE FROM src RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
* Triggers should work in each statement as it does for individual top level statement.&lt;br /&gt;
* You cannot CREATE VIEW on wCTEs query.&lt;br /&gt;
* It is allowed to put DMLs without RETURING clause in WITH, but it is forbidden to refer to that derived table.&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this is ok&lt;br /&gt;
    WITH t1 AS(DELETE FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this raises an error&lt;br /&gt;
    WITH t1 AS(DELETE FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t1;&lt;br /&gt;
* DMLs in WITH clause are allowed only in the top-level WITH.&lt;br /&gt;
    -- raise an error&lt;br /&gt;
    SELECT * FROM(WITH t1 AS(DELETE FROM src) SELECT * FROM t1)s;&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItem|Fix snapshot taking inconsistencies}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow DMLs inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Refactor executors for normal execution, EXPLAIN ANALYZE, SQL language functions and SPI to:|&lt;br /&gt;
* save the results of a certain PlannedStmt&lt;br /&gt;
* maintain a list of those results}}&lt;br /&gt;
{{TodoItemDone|Allow the &amp;quot;main query&amp;quot; to be DMLs|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
* Move rows from src to dest, and return them immediately.&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
&lt;br /&gt;
These are only memoranda or references...&lt;br /&gt;
&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=12372</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=12372"/>
		<updated>2010-11-06T11:52:53Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add &amp;quot;(INSERT | UPDATE | DELETE) .. [RETURNING ..]&amp;quot; to CTEs(Common Table Expressions), both in the WITH clause and the top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH with_query [, ...]&lt;br /&gt;
        plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( plannable_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( select | insert | update | delete )&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;DML&lt;br /&gt;
:An INSERT, DELETE, or UPDATE statement.&lt;br /&gt;
&lt;br /&gt;
;Derived table&lt;br /&gt;
:A temporary table (set of tuples) returned by table expressions.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* Top level DML WITH clauses are executed as written. The snapshot is updated on each execution. Thus, query below returns different numbers.&lt;br /&gt;
    WITH t1 AS (SELECT count(*) FROM x),&lt;br /&gt;
         t2 AS (DELETE FROM x),&lt;br /&gt;
         t3 AS (SELECT count(*) FROM x)&lt;br /&gt;
    SELECT t1.count, t3.count FROM t1, t3;&lt;br /&gt;
* RECURSIVE modifier is not allowed, since forward reference between common table expressions are not allowed to keep execution order.&lt;br /&gt;
* DMLs are executed as separated plans.&lt;br /&gt;
* DMLs in WITH clause can refer to only other table expressions that precedes to it as literally specified. This behavior is the same as normal SELECT CTEs. For example:&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this should work&lt;br /&gt;
    WITH t1 AS(DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this should raise error&lt;br /&gt;
    WITH t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *),&lt;br /&gt;
    t1 AS(DELETE FROM src RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
* Triggers should work in each statement as it does for individual top level statement.&lt;br /&gt;
* You cannot CREATE VIEW on wCTEs query.&lt;br /&gt;
* It is allowed to put DMLs without RETURING clause in WITH, but it is forbidden to refer to that derived table.&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this is ok&lt;br /&gt;
    WITH t1 AS(DELETE FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this raises an error&lt;br /&gt;
    WITH t1 AS(DELETE FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t1;&lt;br /&gt;
* DMLs in WITH clause are allowed only in the top-level WITH.&lt;br /&gt;
    -- raise an error&lt;br /&gt;
    SELECT * FROM(WITH t1 AS(DELETE FROM src) SELECT * FROM t1)s;&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItem|Fix snapshot taking inconsistencies}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow DMLs inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Refactor executors for normal execution, EXPLAIN ANALYZE, SQL language functions and SPI to:|&lt;br /&gt;
* save the results of a certain PlannedStmt&lt;br /&gt;
* maintain a list of those results}}&lt;br /&gt;
{{TodoItemDone|Allow the &amp;quot;main query&amp;quot; to be DMLs|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
* Move rows from src to dest, and return them immediately.&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
&lt;br /&gt;
These are only memoranda or references...&lt;br /&gt;
&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=12371</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=12371"/>
		<updated>2010-11-06T11:47:29Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add &amp;quot;(INSERT | UPDATE | DELETE) .. [RETURNING ..]&amp;quot; to CTEs(Common Table Expressions), both in the WITH clause and the top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
        plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( plannable_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( select | insert | update | delete )&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;DML&lt;br /&gt;
:An INSERT, DELETE, or UPDATE statement.&lt;br /&gt;
&lt;br /&gt;
;Derived table&lt;br /&gt;
:A temporary table (set of tuples) returned by table expressions.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* DMLs are not allowed in a truly recursive table expression, but you can mix recursive queries and DMLs in a single WITH list.&lt;br /&gt;
* DMLs are executed as the query says, whereas SELECTs may be omitted or its order of execution may be changed for optimization. (How?? may need to specify more precisely...)&lt;br /&gt;
* DMLs are executed exactly once, one by one, before starting to execute the top level query.&lt;br /&gt;
* DMLs are executed as separated plans.&lt;br /&gt;
* DMLs in WITH clause can refer to only other table expressions that precedes to it as literally specified. This behavior is the same as normal SELECT CTEs. For example:&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this should work&lt;br /&gt;
    WITH t1 AS(DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this should raise error&lt;br /&gt;
    WITH t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *),&lt;br /&gt;
    t1 AS(DELETE FROM src RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
* Triggers should work in each statement as it does for individual top level statement.&lt;br /&gt;
* You cannot CREATE VIEW on wCTEs query.&lt;br /&gt;
* It is allowed to put DMLs without RETURING clause in WITH, but it is forbidden to refer to that derived table.&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this is ok&lt;br /&gt;
    WITH t1 AS(DELETE FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this raises an error&lt;br /&gt;
    WITH t1 AS(DELETE FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t1;&lt;br /&gt;
* DMLs in WITH clause are allowed only in the top-level WITH.&lt;br /&gt;
    -- raise an error&lt;br /&gt;
    SELECT * FROM(WITH t1 AS(DELETE FROM src) SELECT * FROM t1)s;&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItem|Fix snapshot taking inconsistencies}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow DMLs inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Refactor executors for normal execution, EXPLAIN ANALYZE, SQL language functions and SPI to:|&lt;br /&gt;
* save the results of a certain PlannedStmt&lt;br /&gt;
* maintain a list of those results}}&lt;br /&gt;
{{TodoItemDone|Allow the &amp;quot;main query&amp;quot; to be DMLs|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
* Move rows from src to dest, and return them immediately.&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
&lt;br /&gt;
These are only memoranda or references...&lt;br /&gt;
&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=12358</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=12358"/>
		<updated>2010-11-02T17:39:38Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* General Rules */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add &amp;quot;(INSERT | UPDATE | DELETE) .. [RETURNING ..]&amp;quot; to CTEs(Common Table Expressions), both in the WITH clause and the top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
        plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( plannable_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( select | insert | update | delete )&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;DML&lt;br /&gt;
:An INSERT, DELETE, or UPDATE statement.&lt;br /&gt;
&lt;br /&gt;
;Derived table&lt;br /&gt;
:A temporary table (set of tuples) returned by table expressions.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* DMLs are not allowed in a truly recursive table expression, but you can mix recursive queries and DMLs in a single WITH list.&lt;br /&gt;
* DMLs are executed as the query says, whereas SELECTs may be omitted or its order of execution may be changed for optimization. (How?? may need to specify more precisely...)&lt;br /&gt;
* DMLs are executed exactly once, one by one, before starting to execute the top level query.&lt;br /&gt;
* DMLs are executed as separated plans.&lt;br /&gt;
* DMLs in WITH clause can refer to only other table expressions that precedes to it as literally specified. This behavior is the same as normal SELECT CTEs. For example:&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this should work&lt;br /&gt;
    WITH t1 AS(DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this should raise error&lt;br /&gt;
    WITH t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *),&lt;br /&gt;
    t1 AS(DELETE FROM src RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
* Triggers should work in each statement as it does for individual top level statement.&lt;br /&gt;
* You cannot CREATE VIEW on wCTEs query.&lt;br /&gt;
* It is allowed to put DMLs without RETURING clause in WITH, but it is forbidden to refer to that derived table.&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this is ok&lt;br /&gt;
    WITH t1 AS(DELETE FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this raises an error&lt;br /&gt;
    WITH t1 AS(DELETE FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t1;&lt;br /&gt;
* DMLs in WITH clause are allowed only in the top-level WITH.&lt;br /&gt;
    -- raise an error&lt;br /&gt;
    SELECT * FROM(WITH t1 AS(DELETE FROM src) SELECT * FROM t1)s;&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItem|Fix snapshot taking inconsistencies}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow DMLs inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Refactor executors for normal execution, EXPLAIN ANALYZE, SQL language functions and SPI to:|&lt;br /&gt;
* save the results of a certain PlannedStmt&lt;br /&gt;
* maintain a list of those results}}&lt;br /&gt;
{{TodoItemDone|Allow the &amp;quot;main query&amp;quot; to be DMLs|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
&lt;br /&gt;
These are only memoranda or references...&lt;br /&gt;
&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* This should work:&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=12346</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=12346"/>
		<updated>2010-11-01T17:09:43Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* General Rules */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add &amp;quot;(INSERT | UPDATE | DELETE) .. [RETURNING ..]&amp;quot; to CTEs(Common Table Expressions), both in the WITH clause and the top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
        plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( plannable_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( select | insert | update | delete )&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;DML&lt;br /&gt;
:An INSERT, DELETE, or UPDATE statement.&lt;br /&gt;
&lt;br /&gt;
;Derived table&lt;br /&gt;
:A temporary table (set of tuples) returned by table expressions.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* DMLs are not allowed in a truly recursive table expression, but you can mix recursive queries and DMLs in a single WITH list.&lt;br /&gt;
* DMLs are executed as the query says, whereas SELECTs may be omitted or its order of execution may be changed for optimization. (How?? may need to specify more precisely...)&lt;br /&gt;
* DMLs are executed exactly once, one by one, before starting to execute the top level query.&lt;br /&gt;
* DMLs are executed as separated plans.&lt;br /&gt;
* DMLs in WITH clause can refer to only other table expressions that precedes to it as literally specified.  For example:&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this should work&lt;br /&gt;
    WITH t1 AS(DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this should raise error&lt;br /&gt;
    WITH t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *),&lt;br /&gt;
    t1 AS(DELETE FROM src RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
* Triggers should work in each statement as it does for individual top level statement.&lt;br /&gt;
* You cannot CREATE VIEW on wCTEs query.&lt;br /&gt;
* It is allowed to put DMLs without RETURING clause in WITH, but it is forbidden to refer to that derived table.&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this is ok&lt;br /&gt;
    WITH t1 AS(DELETE FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this raises an error&lt;br /&gt;
    WITH t1 AS(DELETE FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t1;&lt;br /&gt;
* DMLs in WITH clause are allowed only in the top-level WITH.&lt;br /&gt;
    -- raise an error&lt;br /&gt;
    SELECT * FROM(WITH t1 AS(DELETE FROM src) SELECT * FROM t1)s;&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItem|Fix snapshot taking inconsistencies}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow DMLs inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Refactor executors for normal execution, EXPLAIN ANALYZE, SQL language functions and SPI to:|&lt;br /&gt;
* save the results of a certain PlannedStmt&lt;br /&gt;
* maintain a list of those results}}&lt;br /&gt;
{{TodoItemDone|Allow the &amp;quot;main query&amp;quot; to be DMLs|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
&lt;br /&gt;
These are only memoranda or references...&lt;br /&gt;
&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* This should work:&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=12345</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=12345"/>
		<updated>2010-11-01T17:04:24Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add &amp;quot;(INSERT | UPDATE | DELETE) .. [RETURNING ..]&amp;quot; to CTEs(Common Table Expressions), both in the WITH clause and the top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
        plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( plannable_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( select | insert | update | delete )&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;DML&lt;br /&gt;
:An INSERT, DELETE, or UPDATE statement.&lt;br /&gt;
&lt;br /&gt;
;Derived table&lt;br /&gt;
:A temporary table (set of tuples) returned by table expressions.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* DMLs are not allowed in a truly recursive table expression, but you can mix recursive queries and DMLs in a single WITH list.&lt;br /&gt;
* DMLs are executed as the query says, whereas SELECTs may be omitted or its order of execution may be changed for optimization. (How?? may need to specify more precisely...)&lt;br /&gt;
* DMLs are executed exactly once, one by one, before starting to execute the top level query.&lt;br /&gt;
* DMLs are executed as separated plans.&lt;br /&gt;
* DMLs in WITH clause can refer to only other table expressions that precedes to it as literally specified.  For example:&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this should work&lt;br /&gt;
    WITH t1 AS(DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this should raise error&lt;br /&gt;
    WITH t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *),&lt;br /&gt;
    t1 AS(DELETE FROM src RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
* Triggers should work in each statement as it does for individual top level statement.&lt;br /&gt;
* You cannot CREATE VIEW on wCTEs query.&lt;br /&gt;
* It is allowed to put DMLs without RETURING clause in WITH, but it is forbidden to refer to that derived table.&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this is ok&lt;br /&gt;
    WITH t1 AS(DELETE FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this raises an error&lt;br /&gt;
    WITH t1 AS(DELETE FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t1;&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItem|Fix snapshot taking inconsistencies}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow DMLs inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Refactor executors for normal execution, EXPLAIN ANALYZE, SQL language functions and SPI to:|&lt;br /&gt;
* save the results of a certain PlannedStmt&lt;br /&gt;
* maintain a list of those results}}&lt;br /&gt;
{{TodoItemDone|Allow the &amp;quot;main query&amp;quot; to be DMLs|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
&lt;br /&gt;
These are only memoranda or references...&lt;br /&gt;
&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* This should work:&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11832</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11832"/>
		<updated>2010-08-17T09:48:27Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* General Rules */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add a feature to existing CTEs(Common Table Expressions) that allow &amp;quot;(INSERT | UPDATE | DELETE) .. [RETURNING ..]&amp;quot; in the WITH clause. Also, we allow (INSERT | UPDATE | DELETE) as CTEs&#039; top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
        plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( plannable_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( select | insert | update | delete )&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;IDU&lt;br /&gt;
:A statement of either INSERT, DELETE, or UPDATE.&lt;br /&gt;
&lt;br /&gt;
;Derived table&lt;br /&gt;
:A temporary table (set of tuples) returned by table expressions.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* IDUs are not allowed in a truly recursive table expression, but you can mix recursive queries and IDUs in a single WITH list.&lt;br /&gt;
* IDUs are executed as the query says, whereas SELECTs may be omitted or its order of execution may be changed for optimization. (How?? may need to specify more precisely...)&lt;br /&gt;
* IDUs are executed exactly once, one by one, before starting to execute the top level query.&lt;br /&gt;
* IDUs are executed as separated plans.&lt;br /&gt;
* IDUs in WITH clause can refer to only other table expressions that precedes to it as literally specified.  For example:&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this should work&lt;br /&gt;
    WITH t1 AS(DELETE * FROM src RETURNING *),&lt;br /&gt;
    t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this should raise error&lt;br /&gt;
    WITH t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *),&lt;br /&gt;
    t1 AS(DELETE * FROM src RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
* Triggers should work in each statement as it does for individual top level statement.&lt;br /&gt;
* You cannot CREATE VIEW on wCTEs query.&lt;br /&gt;
* It is allowed to put IDUs without RETURING clause in WITH, but it is forbidden to refer to that derived table.&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this is ok&lt;br /&gt;
    WITH t1 AS(DELETE * FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this raises an error&lt;br /&gt;
    WITH t1 AS(DELETE * FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t1;&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow IDUs inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be IDUs|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
&lt;br /&gt;
These are nothing more than memorandums or references...&lt;br /&gt;
&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* This should work:&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11831</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11831"/>
		<updated>2010-08-17T09:46:47Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* General Rules */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add a feature to existing CTEs(Common Table Expressions) that allow &amp;quot;(INSERT | UPDATE | DELETE) .. [RETURNING ..]&amp;quot; in the WITH clause. Also, we allow (INSERT | UPDATE | DELETE) as CTEs&#039; top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
        plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( plannable_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( select | insert | update | delete )&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;IDU&lt;br /&gt;
:A statement of either INSERT, DELETE, or UPDATE.&lt;br /&gt;
&lt;br /&gt;
;Derived table&lt;br /&gt;
:A temporary table (set of tuples) returned by table expressions.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* IDUs are not allowed in a truly recursive table expression, but you can mix recursive queries and IDUs in a single WITH list.&lt;br /&gt;
* IDUs are executed as the query says, whereas SELECTs may be omitted or its order of execution may be changed for optimization. (How?? may need to specify more precisely...)&lt;br /&gt;
* IDUs are executed exactly once, one by one, before starting to execute the top level query.&lt;br /&gt;
* IDUs are executed as separated plans.&lt;br /&gt;
* IDUs in WITH clause can refer to only other table expressions that precedes to it as literally specified.  For example:&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this should work&lt;br /&gt;
    WITH t1 AS(DELETE * FROM src RETURNING *),&lt;br /&gt;
    t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this should raise error&lt;br /&gt;
    WITH t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *),&lt;br /&gt;
    t1 AS(DELETE * FROM src RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
* Triggers should work in each statement as it does for individual top level statement.&lt;br /&gt;
* You cannot CREATE VIEW on wCTEs query.&lt;br /&gt;
* It is allowed to put IDUs without RETURING clause in WITH, but it is forbidden to refer to that kind of table.&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this is ok&lt;br /&gt;
    WITH t1 AS(DELETE * FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this raises an error&lt;br /&gt;
    WITH t1 AS(DELETE * FROM src), t2 AS(SELECT * FROM dest)&lt;br /&gt;
    SELECT * FROM t1;&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow IDUs inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be IDUs|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
&lt;br /&gt;
These are nothing more than memorandums or references...&lt;br /&gt;
&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* This should work:&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11797</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11797"/>
		<updated>2010-08-16T04:33:58Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* Implementation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add a feature to existing CTEs(Common Table Expressions) that allow &amp;quot;(INSERT | UPDATE | DELETE)... RETURING *&amp;quot; in the WITH clause. Also, we allow (INSERT | UPDATE | DELTE) as CTEs&#039; top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
    plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( returning_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( SELECT | INSERT | UPDATE | DELETE )&lt;br /&gt;
&lt;br /&gt;
returning_statement is:&lt;br /&gt;
    ( SELECT ... | ( INSERT | UPDATE | DELETE ) ... RETURNING &amp;lt;columns&amp;gt; )&lt;br /&gt;
&lt;br /&gt;
IUD (see below) without RETURNING clause is not allowed in WITH clause. If we have MERGE or something in the future, and it has RETURING clause, then it will be able to be in WITH clause.&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;IUD&lt;br /&gt;
:A statement of either INSERT, UPDATE, or DELETE.&lt;br /&gt;
&lt;br /&gt;
;Derived table&lt;br /&gt;
:A temporary table (set of tuples) returned by table expressions.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* IUDs are not allowed in a truly recursive table expression, but you can mix recursive queries and IUDs in a single WITH list.&lt;br /&gt;
* IUDs are executed as the query says, whereas SELECTs may be omitted or its order of execution may be changed for optimization. (How?? may need to specify more precisely...)&lt;br /&gt;
* IUDs are executed exactly once, one by one, before starting to execute the top level query.&lt;br /&gt;
* IUDs are executed as separated plans.&lt;br /&gt;
* IUDs in WITH clause can refer to only other table expressions that precedes to it as literally specified.  For example:&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this should work&lt;br /&gt;
    WITH t1 AS(DELETE * FROM src RETURNING *),&lt;br /&gt;
    t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this should raise error&lt;br /&gt;
    WITH t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *),&lt;br /&gt;
    t1 AS(DELETE * FROM src RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
* Triggers should work in each statement as it does for individual top level statement.&lt;br /&gt;
* You cannot CREATE VIEW on wCTEs query.&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow IUDs inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be IUDs|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
&lt;br /&gt;
These are nothing more than memorandums or references...&lt;br /&gt;
&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* This should work:&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11783</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11783"/>
		<updated>2010-08-15T09:58:25Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* General Rules */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add a feature to existing CTEs(Common Table Expressions) that allow &amp;quot;(INSERT | UPDATE | DELETE)... RETURING *&amp;quot; in the WITH clause. Also, we allow (INSERT | UPDATE | DELTE) as CTEs&#039; top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
    plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( returning_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( SELECT | INSERT | UPDATE | DELETE )&lt;br /&gt;
&lt;br /&gt;
returning_statement is:&lt;br /&gt;
    ( SELECT ... | ( INSERT | UPDATE | DELETE ) ... RETURNING &amp;lt;columns&amp;gt; )&lt;br /&gt;
&lt;br /&gt;
IUD (see below) without RETURNING clause is not allowed in WITH clause. If we have MERGE or something in the future, and it has RETURING clause, then it will be able to be in WITH clause.&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;IUD&lt;br /&gt;
:A statement of either INSERT, UPDATE, or DELETE.&lt;br /&gt;
&lt;br /&gt;
;Derived table&lt;br /&gt;
:A temporary table (set of tuples) returned by table expressions.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* IUDs are not allowed in a truly recursive table expression, but you can mix recursive queries and IUDs in a single WITH list.&lt;br /&gt;
* IUDs are executed as the query says, whereas SELECTs may be omitted or its order of execution may be changed for optimization. (How?? may need to specify more precisely...)&lt;br /&gt;
* IUDs are executed exactly once, one by one, before starting to execute the top level query.&lt;br /&gt;
* IUDs are executed as separated plans.&lt;br /&gt;
* IUDs in WITH clause can refer to only other table expressions that precedes to it as literally specified.  For example:&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this should work&lt;br /&gt;
    WITH t1 AS(DELETE * FROM src RETURNING *),&lt;br /&gt;
    t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this should raise error&lt;br /&gt;
    WITH t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *),&lt;br /&gt;
    t1 AS(DELETE * FROM src RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
* Triggers should work in each statement as it does for individual top level statement.&lt;br /&gt;
* You cannot CREATE VIEW on wCTEs query.&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow INSERT, UPDATE and DELETE inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be INSERT, UPDATE or DELETE|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
&lt;br /&gt;
These are nothing more than memorandums or references...&lt;br /&gt;
&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* This should work:&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11782</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11782"/>
		<updated>2010-08-15T09:58:10Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* General Rules */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add a feature to existing CTEs(Common Table Expressions) that allow &amp;quot;(INSERT | UPDATE | DELETE)... RETURING *&amp;quot; in the WITH clause. Also, we allow (INSERT | UPDATE | DELTE) as CTEs&#039; top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
    plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( returning_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( SELECT | INSERT | UPDATE | DELETE )&lt;br /&gt;
&lt;br /&gt;
returning_statement is:&lt;br /&gt;
    ( SELECT ... | ( INSERT | UPDATE | DELETE ) ... RETURNING &amp;lt;columns&amp;gt; )&lt;br /&gt;
&lt;br /&gt;
IUD (see below) without RETURNING clause is not allowed in WITH clause. If we have MERGE or something in the future, and it has RETURING clause, then it will be able to be in WITH clause.&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;IUD&lt;br /&gt;
:A statement of either INSERT, UPDATE, or DELETE.&lt;br /&gt;
&lt;br /&gt;
;Derived table&lt;br /&gt;
:A temporary table (set of tuples) returned by table expressions.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* IUDs are not allowed in a truly recursive table expression, but you can mix recursive queries and IUDs in a single WITH list.&lt;br /&gt;
* IUDs are executed as the query says, whereas SELECTs may be omitted or its order of execution may be changed for optimization. (How?? may need to specify more precisely...)&lt;br /&gt;
* IUDs are executed exactly once, one by one, before starting to execute the top level query.&lt;br /&gt;
* IUDs are executed as separated plans.&lt;br /&gt;
* IUDs in WITH clause can refer to only other table expressions that precedes to it as literally specified.  For example:&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this should work&lt;br /&gt;
    WITH t1 AS(DELETE * FROM src RETURNING *),&lt;br /&gt;
    t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this should raise error&lt;br /&gt;
    WITH t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *),&lt;br /&gt;
    t1 AS(DELETE * FROM src RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
* Triggers should work in each statement as it does for individual top level statement.&lt;br /&gt;
* You cannot make VIEW on wCTEs query.&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow INSERT, UPDATE and DELETE inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be INSERT, UPDATE or DELETE|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
&lt;br /&gt;
These are nothing more than memorandums or references...&lt;br /&gt;
&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* This should work:&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11781</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11781"/>
		<updated>2010-08-15T09:57:13Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* General Rules */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add a feature to existing CTEs(Common Table Expressions) that allow &amp;quot;(INSERT | UPDATE | DELETE)... RETURING *&amp;quot; in the WITH clause. Also, we allow (INSERT | UPDATE | DELTE) as CTEs&#039; top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
    plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( returning_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( SELECT | INSERT | UPDATE | DELETE )&lt;br /&gt;
&lt;br /&gt;
returning_statement is:&lt;br /&gt;
    ( SELECT ... | ( INSERT | UPDATE | DELETE ) ... RETURNING &amp;lt;columns&amp;gt; )&lt;br /&gt;
&lt;br /&gt;
IUD (see below) without RETURNING clause is not allowed in WITH clause. If we have MERGE or something in the future, and it has RETURING clause, then it will be able to be in WITH clause.&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;IUD&lt;br /&gt;
:A statement of either INSERT, UPDATE, or DELETE.&lt;br /&gt;
&lt;br /&gt;
;Derived table&lt;br /&gt;
:A temporary table (set of tuples) returned by table expressions.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* IUDs are not allowed in a truly recursive table expression, but you can mix recursive queries and IUDs in a single WITH list.&lt;br /&gt;
* IUDs are executed as the query says, whereas SELECTs may be omitted or its order of execution may be changed for optimization. (How?? may need to specify more precisely...)&lt;br /&gt;
* IUDs are executed exactly once, one by one, before starting to execute the top level query.&lt;br /&gt;
* IUDs are executed as separated plans.&lt;br /&gt;
* IUDs in WITH clause can refer to only other table expressions that precedes to it as literally specified.  For example:&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this should work&lt;br /&gt;
    WITH t1 AS(DELETE * FROM src RETURNING *),&lt;br /&gt;
    t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this should raise error&lt;br /&gt;
    WITH t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *),&lt;br /&gt;
    t1 AS(DELETE * FROM src RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
* Triggers should work in each statement as it does for individual top level statement.&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow INSERT, UPDATE and DELETE inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be INSERT, UPDATE or DELETE|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
&lt;br /&gt;
These are nothing more than memorandums or references...&lt;br /&gt;
&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* This should work:&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11771</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11771"/>
		<updated>2010-08-14T06:07:33Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* General Rules */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add a feature to existing CTEs(Common Table Expressions) that allow &amp;quot;(INSERT | UPDATE | DELETE)... RETURING *&amp;quot; in the WITH clause. Also, we allow (INSERT | UPDATE | DELTE) as CTEs&#039; top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
    plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( returning_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( SELECT | INSERT | UPDATE | DELETE )&lt;br /&gt;
&lt;br /&gt;
returning_statement is:&lt;br /&gt;
    ( SELECT ... | ( INSERT | UPDATE | DELETE ) ... RETURNING &amp;lt;columns&amp;gt; )&lt;br /&gt;
&lt;br /&gt;
IUD (see below) without RETURNING clause is not allowed in WITH clause. If we have MERGE or something in the future, and it has RETURING clause, then it will be able to be in WITH clause.&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;IUD&lt;br /&gt;
:A statement of either INSERT, UPDATE, or DELETE.&lt;br /&gt;
&lt;br /&gt;
;Derived table&lt;br /&gt;
:A temporary table (set of tuples) returned by table expressions.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* IUDs are not allowed in RECURSIVE table expression.&lt;br /&gt;
* IUDs are executed as the query says, whereas SELECTs may be omitted or its order of execution may be changed for optimization. (How?? may need to specify more precisely...)&lt;br /&gt;
* IUDs are executed exactly once before starting to execute the top level query one by one.&lt;br /&gt;
* IUDs are executed separately. (If each execution is isolated, what happens if the second IUD is aborted after the first IUD was succeeded?)&lt;br /&gt;
* IUDs in WITH clause can refer to only other table expressions that precedes to it as literally specified. ex)&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this should work&lt;br /&gt;
    WITH t1 AS(DELETE * FROM src RETURNING *),&lt;br /&gt;
    t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this should raise error&lt;br /&gt;
    WITH t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *),&lt;br /&gt;
    t1 AS(DELETE * FROM src RETURNING *),&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
* Triggers should work in each statement as it does for individual top level statement.&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow INSERT, UPDATE and DELETE inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be INSERT, UPDATE or DELETE|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
&lt;br /&gt;
These are nothing more than memorandums or references...&lt;br /&gt;
&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* This should work:&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11769</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11769"/>
		<updated>2010-08-14T05:22:05Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* Discussion Logs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add a feature to existing CTEs(Common Table Expressions) that allow &amp;quot;(INSERT | UPDATE | DELETE)... RETURING *&amp;quot; in the WITH clause. Also, we allow (INSERT | UPDATE | DELTE) as CTEs&#039; top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
    plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( returning_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( SELECT | INSERT | UPDATE | DELETE )&lt;br /&gt;
&lt;br /&gt;
returning_statement is:&lt;br /&gt;
    ( SELECT ... | ( INSERT | UPDATE | DELETE ) ... RETURNING &amp;lt;columns&amp;gt; )&lt;br /&gt;
&lt;br /&gt;
IUD (see below) without RETURNING clause is not allowed in WITH clause. If we have MERGE or something in the future, and it has RETURING clause, then it will be able to be in WITH clause.&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;IUD&lt;br /&gt;
:A statement of either INSERT, UPDATE, or DELETE.&lt;br /&gt;
&lt;br /&gt;
;Derived table&lt;br /&gt;
:A temporary table (set of tuples) returned by table expressions.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* IUDs are not allowed in RECURSIVE table expression.&lt;br /&gt;
* IUDs are executed as the query says, whereas SELECTs may be omitted or its order of execution may be changed for optimization. (How?? may need to specify more precisely...)&lt;br /&gt;
* IUDs are executed exactly once before starting to execute the top level query one by one.&lt;br /&gt;
* IUDs are executed separately. (If each execution is isolated, what happens if the second IUD is aborted after the first IUD was succeeded?)&lt;br /&gt;
* IUDs in WITH clause can refer to only other table expressions that precedes to it as literally specified. ex)&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this should work&lt;br /&gt;
    WITH t1 AS(DELETE * FROM src RETURNING *),&lt;br /&gt;
    t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this should raise error&lt;br /&gt;
    WITH t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *),&lt;br /&gt;
    t1 AS(DELETE * FROM src RETURNING *),&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow INSERT, UPDATE and DELETE inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be INSERT, UPDATE or DELETE|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
&lt;br /&gt;
These are nothing more than memorandums or references...&lt;br /&gt;
&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* This should work:&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11768</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11768"/>
		<updated>2010-08-14T05:19:20Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* Terminology */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add a feature to existing CTEs(Common Table Expressions) that allow &amp;quot;(INSERT | UPDATE | DELETE)... RETURING *&amp;quot; in the WITH clause. Also, we allow (INSERT | UPDATE | DELTE) as CTEs&#039; top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
    plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( returning_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( SELECT | INSERT | UPDATE | DELETE )&lt;br /&gt;
&lt;br /&gt;
returning_statement is:&lt;br /&gt;
    ( SELECT ... | ( INSERT | UPDATE | DELETE ) ... RETURNING &amp;lt;columns&amp;gt; )&lt;br /&gt;
&lt;br /&gt;
IUD (see below) without RETURNING clause is not allowed in WITH clause. If we have MERGE or something in the future, and it has RETURING clause, then it will be able to be in WITH clause.&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;IUD&lt;br /&gt;
:A statement of either INSERT, UPDATE, or DELETE.&lt;br /&gt;
&lt;br /&gt;
;Derived table&lt;br /&gt;
:A temporary table (set of tuples) returned by table expressions.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* IUDs are not allowed in RECURSIVE table expression.&lt;br /&gt;
* IUDs are executed as the query says, whereas SELECTs may be omitted or its order of execution may be changed for optimization. (How?? may need to specify more precisely...)&lt;br /&gt;
* IUDs are executed exactly once before starting to execute the top level query one by one.&lt;br /&gt;
* IUDs are executed separately. (If each execution is isolated, what happens if the second IUD is aborted after the first IUD was succeeded?)&lt;br /&gt;
* IUDs in WITH clause can refer to only other table expressions that precedes to it as literally specified. ex)&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this should work&lt;br /&gt;
    WITH t1 AS(DELETE * FROM src RETURNING *),&lt;br /&gt;
    t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this should raise error&lt;br /&gt;
    WITH t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *),&lt;br /&gt;
    t1 AS(DELETE * FROM src RETURNING *),&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow INSERT, UPDATE and DELETE inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be INSERT, UPDATE or DELETE|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* This should work:&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11767</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11767"/>
		<updated>2010-08-14T05:17:53Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* General Rules */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add a feature to existing CTEs(Common Table Expressions) that allow &amp;quot;(INSERT | UPDATE | DELETE)... RETURING *&amp;quot; in the WITH clause. Also, we allow (INSERT | UPDATE | DELTE) as CTEs&#039; top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
    plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( returning_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( SELECT | INSERT | UPDATE | DELETE )&lt;br /&gt;
&lt;br /&gt;
returning_statement is:&lt;br /&gt;
    ( SELECT ... | ( INSERT | UPDATE | DELETE ) ... RETURNING &amp;lt;columns&amp;gt; )&lt;br /&gt;
&lt;br /&gt;
IUD (see below) without RETURNING clause is not allowed in WITH clause. If we have MERGE or something in the future, and it has RETURING clause, then it will be able to be in WITH clause.&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;IUD&lt;br /&gt;
:A statement of either INSERT, UPDATE, or DELETE.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* IUDs are not allowed in RECURSIVE table expression.&lt;br /&gt;
* IUDs are executed as the query says, whereas SELECTs may be omitted or its order of execution may be changed for optimization. (How?? may need to specify more precisely...)&lt;br /&gt;
* IUDs are executed exactly once before starting to execute the top level query one by one.&lt;br /&gt;
* IUDs are executed separately. (If each execution is isolated, what happens if the second IUD is aborted after the first IUD was succeeded?)&lt;br /&gt;
* IUDs in WITH clause can refer to only other table expressions that precedes to it as literally specified. ex)&amp;lt;br /&amp;gt;&lt;br /&gt;
    -- this should work&lt;br /&gt;
    WITH t1 AS(DELETE * FROM src RETURNING *),&lt;br /&gt;
    t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
    &lt;br /&gt;
    -- this should raise error&lt;br /&gt;
    WITH t2 AS(INSERT INTO dest SELECT * FROM t1 RETURNING *),&lt;br /&gt;
    t1 AS(DELETE * FROM src RETURNING *),&lt;br /&gt;
    SELECT * FROM t2;&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow INSERT, UPDATE and DELETE inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be INSERT, UPDATE or DELETE|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* This should work:&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11766</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11766"/>
		<updated>2010-08-14T05:12:26Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* Discussion Logs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add a feature to existing CTEs(Common Table Expressions) that allow &amp;quot;(INSERT | UPDATE | DELETE)... RETURING *&amp;quot; in the WITH clause. Also, we allow (INSERT | UPDATE | DELTE) as CTEs&#039; top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
    plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( returning_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( SELECT | INSERT | UPDATE | DELETE )&lt;br /&gt;
&lt;br /&gt;
returning_statement is:&lt;br /&gt;
    ( SELECT ... | ( INSERT | UPDATE | DELETE ) ... RETURNING &amp;lt;columns&amp;gt; )&lt;br /&gt;
&lt;br /&gt;
IUD (see below) without RETURNING clause is not allowed in WITH clause. If we have MERGE or something in the future, and it has RETURING clause, then it will be able to be in WITH clause.&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;IUD&lt;br /&gt;
:A statement of either INSERT, UPDATE, or DELETE.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* IUDs are not allowed in RECURSIVE table expression.&lt;br /&gt;
* IUDs are executed as the query says, whereas SELECTs may be omitted or its order of execution may be changed for optimization. (How?? may need to specify more precisely...)&lt;br /&gt;
* IUDs are executed exactly once before starting to execute the top level query one by one.&lt;br /&gt;
* IUDs are executed separately. (If each execution is isolated, what happens if the second IUD is aborted after the first IUD was succeeded?)&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow INSERT, UPDATE and DELETE inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be INSERT, UPDATE or DELETE|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* This should work:&lt;br /&gt;
    WITH t1 AS (DELETE FROM src RETURNING *),&lt;br /&gt;
    t2 AS (INSERT INTO dest SELECT * FROM t1 RETURNING *)&lt;br /&gt;
    SELECT * FROM t2&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11765</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11765"/>
		<updated>2010-08-14T05:11:07Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* Terminology */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add a feature to existing CTEs(Common Table Expressions) that allow &amp;quot;(INSERT | UPDATE | DELETE)... RETURING *&amp;quot; in the WITH clause. Also, we allow (INSERT | UPDATE | DELTE) as CTEs&#039; top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
    plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( returning_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( SELECT | INSERT | UPDATE | DELETE )&lt;br /&gt;
&lt;br /&gt;
returning_statement is:&lt;br /&gt;
    ( SELECT ... | ( INSERT | UPDATE | DELETE ) ... RETURNING &amp;lt;columns&amp;gt; )&lt;br /&gt;
&lt;br /&gt;
IUD (see below) without RETURNING clause is not allowed in WITH clause. If we have MERGE or something in the future, and it has RETURING clause, then it will be able to be in WITH clause.&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;IUD&lt;br /&gt;
:A statement of either INSERT, UPDATE, or DELETE.&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* IUDs are not allowed in RECURSIVE table expression.&lt;br /&gt;
* IUDs are executed as the query says, whereas SELECTs may be omitted or its order of execution may be changed for optimization. (How?? may need to specify more precisely...)&lt;br /&gt;
* IUDs are executed exactly once before starting to execute the top level query one by one.&lt;br /&gt;
* IUDs are executed separately. (If each execution is isolated, what happens if the second IUD is aborted after the first IUD was succeeded?)&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow INSERT, UPDATE and DELETE inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be INSERT, UPDATE or DELETE|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* This should work:&lt;br /&gt;
    with t1 as (delete from src returning *), t2 as(insert into dest select * from t1 returning *) select * from t2&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11764</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11764"/>
		<updated>2010-08-14T05:10:42Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add a feature to existing CTEs(Common Table Expressions) that allow &amp;quot;(INSERT | UPDATE | DELETE)... RETURING *&amp;quot; in the WITH clause. Also, we allow (INSERT | UPDATE | DELTE) as CTEs&#039; top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
    plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( returning_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( SELECT | INSERT | UPDATE | DELETE )&lt;br /&gt;
&lt;br /&gt;
returning_statement is:&lt;br /&gt;
    ( SELECT ... | ( INSERT | UPDATE | DELETE ) ... RETURNING &amp;lt;columns&amp;gt; )&lt;br /&gt;
&lt;br /&gt;
IUD (see below) without RETURNING clause is not allowed in WITH clause. If we have MERGE or something in the future, and it has RETURING clause, then it will be able to be in WITH clause.&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;IUD&lt;br /&gt;
:Statements of either INSERT, UPDATE, or DELETE.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Rules ==&lt;br /&gt;
&lt;br /&gt;
* IUDs are not allowed in RECURSIVE table expression.&lt;br /&gt;
* IUDs are executed as the query says, whereas SELECTs may be omitted or its order of execution may be changed for optimization. (How?? may need to specify more precisely...)&lt;br /&gt;
* IUDs are executed exactly once before starting to execute the top level query one by one.&lt;br /&gt;
* IUDs are executed separately. (If each execution is isolated, what happens if the second IUD is aborted after the first IUD was succeeded?)&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow INSERT, UPDATE and DELETE inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be INSERT, UPDATE or DELETE|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
* The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
* pg_plan_query() returns List of PlannedStmt instead of one PlannedStmt:&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
* This should work:&lt;br /&gt;
    with t1 as (delete from src returning *), t2 as(insert into dest select * from t1 returning *) select * from t2&lt;br /&gt;
* RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&amp;lt;br /&amp;gt;&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11763</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11763"/>
		<updated>2010-08-14T04:55:04Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* Syntax */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add a feature to existing CTEs(Common Table Expressions) that allow &amp;quot;(INSERT | UPDATE | DELETE)... RETURING *&amp;quot; in the WITH clause. Also, we allow (INSERT | UPDATE | DELTE) as CTEs&#039; top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
    plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( returning_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( SELECT | INSERT | UPDATE | DELETE )&lt;br /&gt;
&lt;br /&gt;
returning_statement is:&lt;br /&gt;
    ( SELECT ... | ( INSERT | UPDATE | DELETE ) ... RETURNING &amp;lt;columns&amp;gt; )&lt;br /&gt;
&lt;br /&gt;
IUD (see below) without RETURNING clause is not allowed in WITH clause. If we have MERGE or something, and it has RETURING clause, then it will be able to be in WITH clause.&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;IUD&lt;br /&gt;
:Statements of either INSERT, UPDATE, or DELETE.&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow INSERT, UPDATE and DELETE inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be INSERT, UPDATE or DELETE|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
&lt;br /&gt;
pg_plan_query returns List of PlannedStmt instead of one PlannedStmt:&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
&lt;br /&gt;
This should work:&lt;br /&gt;
with t1 as (delete from src returning *), t2 as(insert into dest select * from t1 returning *) select * from t2&lt;br /&gt;
&lt;br /&gt;
RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11762</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11762"/>
		<updated>2010-08-14T04:29:14Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
&lt;br /&gt;
Writeable CTEs add a feature to existing CTEs(Common Table Expressions) that allow &amp;quot;(INSERT | UPDATE | DELETE)... RETURING *&amp;quot; in the WITH clause. Also, we allow (INSERT | UPDATE | DELTE) as CTEs&#039; top-level statement.&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
    plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( returning_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( SELECT | INSERT | UPDATE | DELETE )&lt;br /&gt;
&lt;br /&gt;
returning_statement is:&lt;br /&gt;
    ( SELECT ... | ( INSERT | UPDATE | DELETE ) ... RETURNING &amp;lt;columns&amp;gt; )&lt;br /&gt;
&lt;br /&gt;
IUD (see below) without RETURNING clause is not allowed in WITH clause.&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
;IUD&lt;br /&gt;
:Statements of either INSERT, UPDATE, or DELETE.&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow INSERT, UPDATE and DELETE inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be INSERT, UPDATE or DELETE|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
&lt;br /&gt;
pg_plan_query returns List of PlannedStmt instead of one PlannedStmt:&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
&lt;br /&gt;
This should work:&lt;br /&gt;
with t1 as (delete from src returning *), t2 as(insert into dest select * from t1 returning *) select * from t2&lt;br /&gt;
&lt;br /&gt;
RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11759</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11759"/>
		<updated>2010-08-13T18:47:43Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* Discussion Logs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== API ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
    plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( plannable_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( select | insert | update | delete )&lt;br /&gt;
&lt;br /&gt;
INSERT, UPDATE and DELETE can have a RETURNING clause.  In that case, the results of the RETURNING are stored inside the CTE.&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow INSERT, UPDATE and DELETE inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be INSERT, UPDATE or DELETE|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
&lt;br /&gt;
pg_plan_query returns List of PlannedStmt instead of one PlannedStmt:&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
&lt;br /&gt;
This should work:&lt;br /&gt;
with t1 as (delete from src returning *), t2 as(insert into dest select * from t1 returning *) select * from t2&lt;br /&gt;
&lt;br /&gt;
RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever. WITH RETURNING cannot be contained in RECURSIVE. A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11758</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11758"/>
		<updated>2010-08-13T18:30:18Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* Discussion Logs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== API ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
    plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( plannable_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( select | insert | update | delete )&lt;br /&gt;
&lt;br /&gt;
INSERT, UPDATE and DELETE can have a RETURNING clause.  In that case, the results of the RETURNING are stored inside the CTE.&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow INSERT, UPDATE and DELETE inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be INSERT, UPDATE or DELETE|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
&lt;br /&gt;
pg_plan_query returns List of PlannedStmt instead of one PlannedStmt:&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;br /&gt;
&lt;br /&gt;
This should work:&lt;br /&gt;
with t1 as (delete from src returning *), t2 as(insert into dest select * from t1 returning *) select * from t2&lt;br /&gt;
&lt;br /&gt;
RECURSIVE query is fine as long as 1) it&#039;s SELECT-only and 2) it doesn&#039;t loop forever.  A wCTE can of course refer to the result of the recursive SELECT query with INSERT .. SELECT, UPDATE .. FROM or DELETE .. USING. :&lt;br /&gt;
http://archives.postgresql.org/message-id/4C5857DF.4000801@cs.helsinki.fi&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11757</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11757"/>
		<updated>2010-08-13T18:10:57Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* Discussion Logs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== API ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
    plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( plannable_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( select | insert | update | delete )&lt;br /&gt;
&lt;br /&gt;
INSERT, UPDATE and DELETE can have a RETURNING clause.  In that case, the results of the RETURNING are stored inside the CTE.&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow INSERT, UPDATE and DELETE inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be INSERT, UPDATE or DELETE|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
The execution order of each DML should be syntactically? DML -&amp;gt; SELECT?:&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
&lt;br /&gt;
pg_plan_query returns List of PlannedStmt instead of one PlannedStmt:&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11756</id>
		<title>WriteableCTEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=WriteableCTEs&amp;diff=11756"/>
		<updated>2010-08-13T18:08:56Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== API ==&lt;br /&gt;
&lt;br /&gt;
    [WITH [ RECURSIVE ] with_query [, ...]&lt;br /&gt;
    plannable_statement&lt;br /&gt;
&lt;br /&gt;
where with_query is:&lt;br /&gt;
    with_query_name [ ( column_name [, ...] ) ] AS ( plannable_statement )&lt;br /&gt;
&lt;br /&gt;
and plannable_statement (see gram.y for the origin of this term) query is:&lt;br /&gt;
    ( select | insert | update | delete )&lt;br /&gt;
&lt;br /&gt;
INSERT, UPDATE and DELETE can have a RETURNING clause.  In that case, the results of the RETURNING are stored inside the CTE.&lt;br /&gt;
&lt;br /&gt;
== Implementation ==&lt;br /&gt;
Since this patch is quite complicated, I&#039;ve split it up to a few milestones:&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItemDone|Add a new executor node, Derived Table scan, to support scanning from tuplestores.|&lt;br /&gt;
* None of the existing executor nodes did only this (all of them deal with a subplan of some kind), so adding a new one made seemed to make sense.&lt;br /&gt;
* In the future, this node can be used to support other queries in WITHs (COPY, for example).&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Make all WITH queries work like wCTEs would|&lt;br /&gt;
* What this means is that we run all WITH queries to completion and store the results in tuplestores.  Then we proceed to execute the main plan.&lt;br /&gt;
* This means changes to the portal code, EXPLAIN ANALYZE, SQL function and SPI execution code.&lt;br /&gt;
* There&#039;s a proof-of-concept code in the git repo that works, but it&#039;s still very messy and only changes the portal code.  It also doesn&#039;t handle snapshots correctly, but it&#039;s not yet clear what the code should look like (see NOTE near the bottom of this item).  Not all regression tests for WITH are applicable because we don&#039;t need to support non-top-level CTEs, so they&#039;ve been taken out from the git repo.  Also a RECURSIVE query must not loop forever, so those tests are gone too.  All remaining tests are passed now.&lt;br /&gt;
&#039;&#039;&#039;NOTE&#039;&#039;&#039;:  There&#039;s an unresolved issue that affects this part of the plan, see http://archives.postgresql.org/message-id/4C49E821.8060206@cs.helsinki.fi&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow INSERT, UPDATE and DELETE inside top-level CTEs|&lt;br /&gt;
* I think this stage can be completed by just copy-pasting from the patch considered for 9.0.&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem|Allow the &amp;quot;main query&amp;quot; to be INSERT, UPDATE or DELETE|&lt;br /&gt;
* There were some problems with this for 9.0, see http://archives.postgresql.org/pgsql-hackers/2010-02/msg01065.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
== More Features ==&lt;br /&gt;
&lt;br /&gt;
These are just possibilities.  They are not a roadmap.  Your measurements may vary.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    DCL&lt;br /&gt;
&lt;br /&gt;
    DDL&lt;br /&gt;
&lt;br /&gt;
    CTAS support&lt;br /&gt;
&lt;br /&gt;
    Non-Row-Returning CTEs&lt;br /&gt;
&lt;br /&gt;
== Discussion Logs ==&lt;br /&gt;
http://archives.postgresql.org/message-id/6537.1255029119@sss.pgh.pa.us&lt;br /&gt;
&lt;br /&gt;
pg_plan_query returns List of PlannedStmt instead of one PlannedStmt:&lt;br /&gt;
http://archives.postgresql.org/message-id/1296.1265839071@sss.pgh.pa.us&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10425</id>
		<title>TestFest For 9 JP</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10425"/>
		<updated>2010-04-03T15:32:24Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* その他 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== 概要 ==&lt;br /&gt;
PostgreSQL 9のベータリリースに合わせて、Hackathon形式で集中テストを行います。同日にサンフランシスコで行われる[[SFPUG_Beta_Test_Day]]と連携します。&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;以下は現在時点での情報です。変更になる可能性がありますのでご注意ください。&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Twitterハッシュタグ : [http://twitter.com/#search?q=%23TestFest #TestFest]&lt;br /&gt;
&lt;br /&gt;
== 内容 ==&lt;br /&gt;
&lt;br /&gt;
基本的にはSFPUGのテスト内容に準じます。&lt;br /&gt;
&lt;br /&gt;
* コンパイルテスト&lt;br /&gt;
** 各種オプション付けて&lt;br /&gt;
** contribモジュール&lt;br /&gt;
** 外部モジュール&lt;br /&gt;
** 回帰テスト&lt;br /&gt;
* pgBenchテスト&lt;br /&gt;
** 8.4 vs. 9.0&lt;br /&gt;
* 新機能テスト （[http://lets.postgresql.jp/documents/technical/9.0/1 新機能紹介ページ]）&lt;br /&gt;
** ホットスタンバイ&lt;br /&gt;
** ストリーミングレプリケーション&lt;br /&gt;
** 除外制約&lt;br /&gt;
** LISTEN/NOTIFY&lt;br /&gt;
** DO文（各種言語で）&lt;br /&gt;
** 追加されたウィンドウ関数フレーム&lt;br /&gt;
** その他募集中&lt;br /&gt;
* データベース移行テスト データの用意もお願いします！&lt;br /&gt;
* アプリケーション移行テスト&lt;br /&gt;
** MediaWiki&lt;br /&gt;
** Slony&lt;br /&gt;
** Bucardo&lt;br /&gt;
** pgsnmpd&lt;br /&gt;
** pgpool&lt;br /&gt;
** textsearch_senna&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ドライバ&lt;br /&gt;
** Java&lt;br /&gt;
** Python&lt;br /&gt;
*** psycopg2&lt;br /&gt;
** Perl&lt;br /&gt;
*** DBD::Pg&lt;br /&gt;
** R&lt;br /&gt;
** Ruby&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ORMツール&lt;br /&gt;
** SQLAlchemy&lt;br /&gt;
** Django&lt;br /&gt;
** Hibernate&lt;br /&gt;
** その他募集中&lt;br /&gt;
&lt;br /&gt;
9を先取りして勉強することができます。記事等観てもぱっとわからない機能も隣の人が教えてくれます。また、PostgreSQLの今後の開発や普段疑問に思っていることなどについて自由にディスカッションできます。たぶん飲みながらやるのでぐだぐだになりそうです。&lt;br /&gt;
&lt;br /&gt;
== 場所 ==&lt;br /&gt;
フォルシア株式会社 会議室&lt;br /&gt;
&lt;br /&gt;
東京都新宿区新宿4丁目3-25 オリックス新宿ビル9階&lt;br /&gt;
[http://maps.google.co.jp/maps?f=q&amp;amp;hl=ja&amp;amp;geocode=&amp;amp;time=&amp;amp;date=&amp;amp;ttype=&amp;amp;q=%93%8C%8B%9E%93s%90V%8Fh%8B%E6%90V%8Fh%82S%92%9A%96%DA%82R-%82Q%82T&amp;amp;ie=UTF8&amp;amp;ll=35.689321,139.704277&amp;amp;spn=0.010386,0.013776&amp;amp;z=14&amp;amp;iwloc=addr&amp;amp;om=1&amp;amp;source=embed Google Map]&lt;br /&gt;
&lt;br /&gt;
新宿駅南口徒歩3分&lt;br /&gt;
東京メトロ新宿3丁目駅徒歩1分&lt;br /&gt;
&lt;br /&gt;
== 時間 ==&lt;br /&gt;
4月4日 午前3時～午前10時（日本時間）&lt;br /&gt;
※サンフランシスコ時間4月3日午前11時～午後6時で行われるTestに合わせています。&lt;br /&gt;
&lt;br /&gt;
時間が時間なので前日からのスタンバイあり&lt;br /&gt;
&lt;br /&gt;
== 食事 ==&lt;br /&gt;
軽食を用意します。持ち込み（飲食）歓迎。徒歩圏内でも調達可能。&lt;br /&gt;
&lt;br /&gt;
== 持ち物 ==&lt;br /&gt;
ラップトップ持参。インターネット環境（DHCP）は用意します。Wi-fiに対応できるかは調整中。各自テスト環境を外部サーバに用意できれば尚可。&lt;br /&gt;
&lt;br /&gt;
ラップトップは若干台数貸し出し可能です。お気軽にご連絡ください。&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ &lt;br /&gt;
&#039;&#039;&#039;準備機材&#039;&#039;&#039;&lt;br /&gt;
| &#039;&#039;&#039;所有者&#039;&#039;&#039; || &#039;&#039;&#039;物品&#039;&#039;&#039;  || &#039;&#039;&#039;備考&#039;&#039;&#039; &lt;br /&gt;
|-&lt;br /&gt;
| 永安 || AirMac Express（無線LAN AP)  || &lt;br /&gt;
|-&lt;br /&gt;
| 永安 || VAIO X || 作業用&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || MacBook || テスト用or作業用&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || HP 2133 mini || 誰か必要な人がいれば貸し出し用&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ &lt;br /&gt;
&#039;&#039;&#039;テスト環境&#039;&#039;&#039;&lt;br /&gt;
| &#039;&#039;&#039;所有者&#039;&#039;&#039; || &#039;&#039;&#039;アーキテクチャ&#039;&#039;&#039; || &#039;&#039;&#039;OS&#039;&#039;&#039; || &#039;&#039;&#039;IPアドレス&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || Red Hat Enterprise Linux 5.4 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || CentOS 5.3 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || FreeBSD 6.4 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32  || MacOS X 10.5.8 || x.x.x.x&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86 || 未定 || （Amazon EC2）&lt;br /&gt;
|-&lt;br /&gt;
| 原田 || x64 || Windows || Amazon EC2&lt;br /&gt;
|-&lt;br /&gt;
| 原田 || x86,x64 || Linux(some distros) x N || Amazon EC2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== 参加者一覧 ==&lt;br /&gt;
&lt;br /&gt;
ATNDを参照ください。&lt;br /&gt;
http://atnd.org/events/3785&lt;br /&gt;
&lt;br /&gt;
== その他 ==&lt;br /&gt;
* TwitterでSFPUGと連携します。&lt;br /&gt;
* SFPUGのUstream（http://www.ustream.tv/channel/postgresql---sfpug） [http://twitter.com/#search?q=%23sfpug #sfpug]&lt;br /&gt;
* Ustream実施予定。&lt;br /&gt;
* Streaming Replication Q&amp;amp;A&lt;br /&gt;
* SE-PostgreSQL Q&amp;amp;A&lt;br /&gt;
* Foreign Data Wrapper Q&amp;amp;A&lt;br /&gt;
* Global Replication Test&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
テストの方法については、[[HowToBetaTest]]のフォーマットに従うとよいと思います。翻訳求む。&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10423</id>
		<title>TestFest For 9 JP</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10423"/>
		<updated>2010-04-03T12:35:56Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* その他 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== 概要 ==&lt;br /&gt;
PostgreSQL 9のベータリリースに合わせて、Hackathon形式で集中テストを行います。同日にサンフランシスコで行われる[[SFPUG_Beta_Test_Day]]と連携します。&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;以下は現在時点での情報です。変更になる可能性がありますのでご注意ください。&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Twitterハッシュタグ : [http://twitter.com/#search?q=%23TestFest #TestFest]&lt;br /&gt;
&lt;br /&gt;
== 内容 ==&lt;br /&gt;
&lt;br /&gt;
基本的にはSFPUGのテスト内容に準じます。&lt;br /&gt;
&lt;br /&gt;
* コンパイルテスト&lt;br /&gt;
** 各種オプション付けて&lt;br /&gt;
** contribモジュール&lt;br /&gt;
** 外部モジュール&lt;br /&gt;
** 回帰テスト&lt;br /&gt;
* pgBenchテスト&lt;br /&gt;
** 8.4 vs. 9.0&lt;br /&gt;
* 新機能テスト （[http://lets.postgresql.jp/documents/technical/9.0/1 新機能紹介ページ]）&lt;br /&gt;
** ホットスタンバイ&lt;br /&gt;
** ストリーミングレプリケーション&lt;br /&gt;
** 除外制約&lt;br /&gt;
** LISTEN/NOTIFY&lt;br /&gt;
** DO文（各種言語で）&lt;br /&gt;
** 追加されたウィンドウ関数フレーム&lt;br /&gt;
** その他募集中&lt;br /&gt;
* データベース移行テスト データの用意もお願いします！&lt;br /&gt;
* アプリケーション移行テスト&lt;br /&gt;
** MediaWiki&lt;br /&gt;
** Slony&lt;br /&gt;
** Bucardo&lt;br /&gt;
** pgsnmpd&lt;br /&gt;
** pgpool&lt;br /&gt;
** textsearch_senna&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ドライバ&lt;br /&gt;
** Java&lt;br /&gt;
** Python&lt;br /&gt;
*** psycopg2&lt;br /&gt;
** Perl&lt;br /&gt;
*** DBD::Pg&lt;br /&gt;
** R&lt;br /&gt;
** Ruby&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ORMツール&lt;br /&gt;
** SQLAlchemy&lt;br /&gt;
** Django&lt;br /&gt;
** Hibernate&lt;br /&gt;
** その他募集中&lt;br /&gt;
&lt;br /&gt;
9を先取りして勉強することができます。記事等観てもぱっとわからない機能も隣の人が教えてくれます。また、PostgreSQLの今後の開発や普段疑問に思っていることなどについて自由にディスカッションできます。たぶん飲みながらやるのでぐだぐだになりそうです。&lt;br /&gt;
&lt;br /&gt;
== 場所 ==&lt;br /&gt;
フォルシア株式会社 会議室&lt;br /&gt;
&lt;br /&gt;
東京都新宿区新宿4丁目3-25 オリックス新宿ビル9階&lt;br /&gt;
[http://maps.google.co.jp/maps?f=q&amp;amp;hl=ja&amp;amp;geocode=&amp;amp;time=&amp;amp;date=&amp;amp;ttype=&amp;amp;q=%93%8C%8B%9E%93s%90V%8Fh%8B%E6%90V%8Fh%82S%92%9A%96%DA%82R-%82Q%82T&amp;amp;ie=UTF8&amp;amp;ll=35.689321,139.704277&amp;amp;spn=0.010386,0.013776&amp;amp;z=14&amp;amp;iwloc=addr&amp;amp;om=1&amp;amp;source=embed Google Map]&lt;br /&gt;
&lt;br /&gt;
新宿駅南口徒歩3分&lt;br /&gt;
東京メトロ新宿3丁目駅徒歩1分&lt;br /&gt;
&lt;br /&gt;
== 時間 ==&lt;br /&gt;
4月4日 午前3時～午前10時（日本時間）&lt;br /&gt;
※サンフランシスコ時間4月3日午前11時～午後6時で行われるTestに合わせています。&lt;br /&gt;
&lt;br /&gt;
時間が時間なので前日からのスタンバイあり&lt;br /&gt;
&lt;br /&gt;
== 食事 ==&lt;br /&gt;
軽食を用意します。持ち込み（飲食）歓迎。徒歩圏内でも調達可能。&lt;br /&gt;
&lt;br /&gt;
== 持ち物 ==&lt;br /&gt;
ラップトップ持参。インターネット環境（DHCP）は用意します。Wi-fiに対応できるかは調整中。各自テスト環境を外部サーバに用意できれば尚可。&lt;br /&gt;
&lt;br /&gt;
ラップトップは若干台数貸し出し可能です。お気軽にご連絡ください。&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ &lt;br /&gt;
&#039;&#039;&#039;準備機材&#039;&#039;&#039;&lt;br /&gt;
| &#039;&#039;&#039;所有者&#039;&#039;&#039; || &#039;&#039;&#039;物品&#039;&#039;&#039;  || &#039;&#039;&#039;備考&#039;&#039;&#039; &lt;br /&gt;
|-&lt;br /&gt;
| 永安 || AirMac Express（無線LAN AP)  || &lt;br /&gt;
|-&lt;br /&gt;
| 永安 || VAIO X || 作業用&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || MacBook || テスト用or作業用&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || HP 2133 mini || 誰か必要な人がいれば貸し出し用&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ &lt;br /&gt;
&#039;&#039;&#039;テスト環境&#039;&#039;&#039;&lt;br /&gt;
| &#039;&#039;&#039;所有者&#039;&#039;&#039; || &#039;&#039;&#039;アーキテクチャ&#039;&#039;&#039; || &#039;&#039;&#039;OS&#039;&#039;&#039; || &#039;&#039;&#039;IPアドレス&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || Red Hat Enterprise Linux 5.4 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || CentOS 5.3 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || FreeBSD 6.4 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32  || MacOS X 10.5.8 || x.x.x.x&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86 || 未定 || （Amazon EC2）&lt;br /&gt;
|-&lt;br /&gt;
| 原田 || x64 || Windows || Amazon EC2&lt;br /&gt;
|-&lt;br /&gt;
| 原田 || x86,x64 || Linux(some distros) x N || Amazon EC2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== 参加者一覧 ==&lt;br /&gt;
&lt;br /&gt;
ATNDを参照ください。&lt;br /&gt;
http://atnd.org/events/3785&lt;br /&gt;
&lt;br /&gt;
== その他 ==&lt;br /&gt;
* TwitterでSFPUGと連携します。&lt;br /&gt;
* SFPUGのUstream（http://www.ustream.tv/channel/postgresql---sfpug） [http://twitter.com/#search?q=%23sfpug #sfpug]&lt;br /&gt;
* Ustream実施予定。&lt;br /&gt;
* Streaming Replication Q&amp;amp;A&lt;br /&gt;
* SE-PostgreSQL Q&amp;amp;A&lt;br /&gt;
* Foreign Data Wrapper Q&amp;amp;A&lt;br /&gt;
* Global Replication Test&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10422</id>
		<title>TestFest For 9 JP</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10422"/>
		<updated>2010-04-03T12:35:20Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* 概要 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== 概要 ==&lt;br /&gt;
PostgreSQL 9のベータリリースに合わせて、Hackathon形式で集中テストを行います。同日にサンフランシスコで行われる[[SFPUG_Beta_Test_Day]]と連携します。&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;以下は現在時点での情報です。変更になる可能性がありますのでご注意ください。&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Twitterハッシュタグ : [http://twitter.com/#search?q=%23TestFest #TestFest]&lt;br /&gt;
&lt;br /&gt;
== 内容 ==&lt;br /&gt;
&lt;br /&gt;
基本的にはSFPUGのテスト内容に準じます。&lt;br /&gt;
&lt;br /&gt;
* コンパイルテスト&lt;br /&gt;
** 各種オプション付けて&lt;br /&gt;
** contribモジュール&lt;br /&gt;
** 外部モジュール&lt;br /&gt;
** 回帰テスト&lt;br /&gt;
* pgBenchテスト&lt;br /&gt;
** 8.4 vs. 9.0&lt;br /&gt;
* 新機能テスト （[http://lets.postgresql.jp/documents/technical/9.0/1 新機能紹介ページ]）&lt;br /&gt;
** ホットスタンバイ&lt;br /&gt;
** ストリーミングレプリケーション&lt;br /&gt;
** 除外制約&lt;br /&gt;
** LISTEN/NOTIFY&lt;br /&gt;
** DO文（各種言語で）&lt;br /&gt;
** 追加されたウィンドウ関数フレーム&lt;br /&gt;
** その他募集中&lt;br /&gt;
* データベース移行テスト データの用意もお願いします！&lt;br /&gt;
* アプリケーション移行テスト&lt;br /&gt;
** MediaWiki&lt;br /&gt;
** Slony&lt;br /&gt;
** Bucardo&lt;br /&gt;
** pgsnmpd&lt;br /&gt;
** pgpool&lt;br /&gt;
** textsearch_senna&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ドライバ&lt;br /&gt;
** Java&lt;br /&gt;
** Python&lt;br /&gt;
*** psycopg2&lt;br /&gt;
** Perl&lt;br /&gt;
*** DBD::Pg&lt;br /&gt;
** R&lt;br /&gt;
** Ruby&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ORMツール&lt;br /&gt;
** SQLAlchemy&lt;br /&gt;
** Django&lt;br /&gt;
** Hibernate&lt;br /&gt;
** その他募集中&lt;br /&gt;
&lt;br /&gt;
9を先取りして勉強することができます。記事等観てもぱっとわからない機能も隣の人が教えてくれます。また、PostgreSQLの今後の開発や普段疑問に思っていることなどについて自由にディスカッションできます。たぶん飲みながらやるのでぐだぐだになりそうです。&lt;br /&gt;
&lt;br /&gt;
== 場所 ==&lt;br /&gt;
フォルシア株式会社 会議室&lt;br /&gt;
&lt;br /&gt;
東京都新宿区新宿4丁目3-25 オリックス新宿ビル9階&lt;br /&gt;
[http://maps.google.co.jp/maps?f=q&amp;amp;hl=ja&amp;amp;geocode=&amp;amp;time=&amp;amp;date=&amp;amp;ttype=&amp;amp;q=%93%8C%8B%9E%93s%90V%8Fh%8B%E6%90V%8Fh%82S%92%9A%96%DA%82R-%82Q%82T&amp;amp;ie=UTF8&amp;amp;ll=35.689321,139.704277&amp;amp;spn=0.010386,0.013776&amp;amp;z=14&amp;amp;iwloc=addr&amp;amp;om=1&amp;amp;source=embed Google Map]&lt;br /&gt;
&lt;br /&gt;
新宿駅南口徒歩3分&lt;br /&gt;
東京メトロ新宿3丁目駅徒歩1分&lt;br /&gt;
&lt;br /&gt;
== 時間 ==&lt;br /&gt;
4月4日 午前3時～午前10時（日本時間）&lt;br /&gt;
※サンフランシスコ時間4月3日午前11時～午後6時で行われるTestに合わせています。&lt;br /&gt;
&lt;br /&gt;
時間が時間なので前日からのスタンバイあり&lt;br /&gt;
&lt;br /&gt;
== 食事 ==&lt;br /&gt;
軽食を用意します。持ち込み（飲食）歓迎。徒歩圏内でも調達可能。&lt;br /&gt;
&lt;br /&gt;
== 持ち物 ==&lt;br /&gt;
ラップトップ持参。インターネット環境（DHCP）は用意します。Wi-fiに対応できるかは調整中。各自テスト環境を外部サーバに用意できれば尚可。&lt;br /&gt;
&lt;br /&gt;
ラップトップは若干台数貸し出し可能です。お気軽にご連絡ください。&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ &lt;br /&gt;
&#039;&#039;&#039;準備機材&#039;&#039;&#039;&lt;br /&gt;
| &#039;&#039;&#039;所有者&#039;&#039;&#039; || &#039;&#039;&#039;物品&#039;&#039;&#039;  || &#039;&#039;&#039;備考&#039;&#039;&#039; &lt;br /&gt;
|-&lt;br /&gt;
| 永安 || AirMac Express（無線LAN AP)  || &lt;br /&gt;
|-&lt;br /&gt;
| 永安 || VAIO X || 作業用&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || MacBook || テスト用or作業用&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || HP 2133 mini || 誰か必要な人がいれば貸し出し用&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ &lt;br /&gt;
&#039;&#039;&#039;テスト環境&#039;&#039;&#039;&lt;br /&gt;
| &#039;&#039;&#039;所有者&#039;&#039;&#039; || &#039;&#039;&#039;アーキテクチャ&#039;&#039;&#039; || &#039;&#039;&#039;OS&#039;&#039;&#039; || &#039;&#039;&#039;IPアドレス&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || Red Hat Enterprise Linux 5.4 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || CentOS 5.3 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || FreeBSD 6.4 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32  || MacOS X 10.5.8 || x.x.x.x&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86 || 未定 || （Amazon EC2）&lt;br /&gt;
|-&lt;br /&gt;
| 原田 || x64 || Windows || Amazon EC2&lt;br /&gt;
|-&lt;br /&gt;
| 原田 || x86,x64 || Linux(some distros) x N || Amazon EC2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== 参加者一覧 ==&lt;br /&gt;
&lt;br /&gt;
ATNDを参照ください。&lt;br /&gt;
http://atnd.org/events/3785&lt;br /&gt;
&lt;br /&gt;
== その他 ==&lt;br /&gt;
* TwitterでSFPUGと連携します。&lt;br /&gt;
* SFPUGのUstream（http://www.ustream.tv/channel/postgresql---sfpug） #sfpug&lt;br /&gt;
* Ustream実施予定。&lt;br /&gt;
* Streaming Replication Q&amp;amp;A&lt;br /&gt;
* SE-PostgreSQL Q&amp;amp;A&lt;br /&gt;
* Foreign Data Wrapper Q&amp;amp;A&lt;br /&gt;
* Global Replication Test&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10421</id>
		<title>TestFest For 9 JP</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10421"/>
		<updated>2010-04-03T12:33:13Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* その他 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== 概要 ==&lt;br /&gt;
PostgreSQL 9のベータリリースに合わせて、Hackathon形式で集中テストを行います。同日にサンフランシスコで行われる[[SFPUG_Beta_Test_Day]]と連携します。&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;以下は現在時点での情報です。変更になる可能性がありますのでご注意ください。&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Twitterハッシュタグ : #TestFest&lt;br /&gt;
&lt;br /&gt;
== 内容 ==&lt;br /&gt;
&lt;br /&gt;
基本的にはSFPUGのテスト内容に準じます。&lt;br /&gt;
&lt;br /&gt;
* コンパイルテスト&lt;br /&gt;
** 各種オプション付けて&lt;br /&gt;
** contribモジュール&lt;br /&gt;
** 外部モジュール&lt;br /&gt;
** 回帰テスト&lt;br /&gt;
* pgBenchテスト&lt;br /&gt;
** 8.4 vs. 9.0&lt;br /&gt;
* 新機能テスト （[http://lets.postgresql.jp/documents/technical/9.0/1 新機能紹介ページ]）&lt;br /&gt;
** ホットスタンバイ&lt;br /&gt;
** ストリーミングレプリケーション&lt;br /&gt;
** 除外制約&lt;br /&gt;
** LISTEN/NOTIFY&lt;br /&gt;
** DO文（各種言語で）&lt;br /&gt;
** 追加されたウィンドウ関数フレーム&lt;br /&gt;
** その他募集中&lt;br /&gt;
* データベース移行テスト データの用意もお願いします！&lt;br /&gt;
* アプリケーション移行テスト&lt;br /&gt;
** MediaWiki&lt;br /&gt;
** Slony&lt;br /&gt;
** Bucardo&lt;br /&gt;
** pgsnmpd&lt;br /&gt;
** pgpool&lt;br /&gt;
** textsearch_senna&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ドライバ&lt;br /&gt;
** Java&lt;br /&gt;
** Python&lt;br /&gt;
*** psycopg2&lt;br /&gt;
** Perl&lt;br /&gt;
*** DBD::Pg&lt;br /&gt;
** R&lt;br /&gt;
** Ruby&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ORMツール&lt;br /&gt;
** SQLAlchemy&lt;br /&gt;
** Django&lt;br /&gt;
** Hibernate&lt;br /&gt;
** その他募集中&lt;br /&gt;
&lt;br /&gt;
9を先取りして勉強することができます。記事等観てもぱっとわからない機能も隣の人が教えてくれます。また、PostgreSQLの今後の開発や普段疑問に思っていることなどについて自由にディスカッションできます。たぶん飲みながらやるのでぐだぐだになりそうです。&lt;br /&gt;
&lt;br /&gt;
== 場所 ==&lt;br /&gt;
フォルシア株式会社 会議室&lt;br /&gt;
&lt;br /&gt;
東京都新宿区新宿4丁目3-25 オリックス新宿ビル9階&lt;br /&gt;
[http://maps.google.co.jp/maps?f=q&amp;amp;hl=ja&amp;amp;geocode=&amp;amp;time=&amp;amp;date=&amp;amp;ttype=&amp;amp;q=%93%8C%8B%9E%93s%90V%8Fh%8B%E6%90V%8Fh%82S%92%9A%96%DA%82R-%82Q%82T&amp;amp;ie=UTF8&amp;amp;ll=35.689321,139.704277&amp;amp;spn=0.010386,0.013776&amp;amp;z=14&amp;amp;iwloc=addr&amp;amp;om=1&amp;amp;source=embed Google Map]&lt;br /&gt;
&lt;br /&gt;
新宿駅南口徒歩3分&lt;br /&gt;
東京メトロ新宿3丁目駅徒歩1分&lt;br /&gt;
&lt;br /&gt;
== 時間 ==&lt;br /&gt;
4月4日 午前3時～午前10時（日本時間）&lt;br /&gt;
※サンフランシスコ時間4月3日午前11時～午後6時で行われるTestに合わせています。&lt;br /&gt;
&lt;br /&gt;
時間が時間なので前日からのスタンバイあり&lt;br /&gt;
&lt;br /&gt;
== 食事 ==&lt;br /&gt;
軽食を用意します。持ち込み（飲食）歓迎。徒歩圏内でも調達可能。&lt;br /&gt;
&lt;br /&gt;
== 持ち物 ==&lt;br /&gt;
ラップトップ持参。インターネット環境（DHCP）は用意します。Wi-fiに対応できるかは調整中。各自テスト環境を外部サーバに用意できれば尚可。&lt;br /&gt;
&lt;br /&gt;
ラップトップは若干台数貸し出し可能です。お気軽にご連絡ください。&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ &lt;br /&gt;
&#039;&#039;&#039;準備機材&#039;&#039;&#039;&lt;br /&gt;
| &#039;&#039;&#039;所有者&#039;&#039;&#039; || &#039;&#039;&#039;物品&#039;&#039;&#039;  || &#039;&#039;&#039;備考&#039;&#039;&#039; &lt;br /&gt;
|-&lt;br /&gt;
| 永安 || AirMac Express（無線LAN AP)  || &lt;br /&gt;
|-&lt;br /&gt;
| 永安 || VAIO X || 作業用&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || MacBook || テスト用or作業用&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || HP 2133 mini || 誰か必要な人がいれば貸し出し用&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ &lt;br /&gt;
&#039;&#039;&#039;テスト環境&#039;&#039;&#039;&lt;br /&gt;
| &#039;&#039;&#039;所有者&#039;&#039;&#039; || &#039;&#039;&#039;アーキテクチャ&#039;&#039;&#039; || &#039;&#039;&#039;OS&#039;&#039;&#039; || &#039;&#039;&#039;IPアドレス&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || Red Hat Enterprise Linux 5.4 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || CentOS 5.3 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || FreeBSD 6.4 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32  || MacOS X 10.5.8 || x.x.x.x&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86 || 未定 || （Amazon EC2）&lt;br /&gt;
|-&lt;br /&gt;
| 原田 || x64 || Windows || Amazon EC2&lt;br /&gt;
|-&lt;br /&gt;
| 原田 || x86,x64 || Linux(some distros) x N || Amazon EC2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== 参加者一覧 ==&lt;br /&gt;
&lt;br /&gt;
ATNDを参照ください。&lt;br /&gt;
http://atnd.org/events/3785&lt;br /&gt;
&lt;br /&gt;
== その他 ==&lt;br /&gt;
* TwitterでSFPUGと連携します。&lt;br /&gt;
* SFPUGのUstream（http://www.ustream.tv/channel/postgresql---sfpug） #sfpug&lt;br /&gt;
* Ustream実施予定。&lt;br /&gt;
* Streaming Replication Q&amp;amp;A&lt;br /&gt;
* SE-PostgreSQL Q&amp;amp;A&lt;br /&gt;
* Foreign Data Wrapper Q&amp;amp;A&lt;br /&gt;
* Global Replication Test&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10349</id>
		<title>TestFest For 9 JP</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10349"/>
		<updated>2010-03-30T05:41:27Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* 持ち物 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== 概要 ==&lt;br /&gt;
PostgreSQL 9のベータリリースに合わせて、Hackathon形式で集中テストを行います。同日にサンフランシスコで行われる[[SFPUG_Beta_Test_Day]]と連携します。&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;以下は現在時点での情報です。変更になる可能性がありますのでご注意ください。&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Twitterハッシュタグ : #TestFest&lt;br /&gt;
&lt;br /&gt;
== 内容 ==&lt;br /&gt;
&lt;br /&gt;
基本的にはSFPUGのテスト内容に準じます。&lt;br /&gt;
&lt;br /&gt;
* コンパイルテスト&lt;br /&gt;
** 各種オプション付けて&lt;br /&gt;
** contribモジュール&lt;br /&gt;
** 外部モジュール&lt;br /&gt;
** 回帰テスト&lt;br /&gt;
* pgBenchテスト&lt;br /&gt;
** 8.4 vs. 9.0&lt;br /&gt;
* 新機能テスト （[http://lets.postgresql.jp/documents/technical/9.0/1 新機能紹介ページ]）&lt;br /&gt;
** ホットスタンバイ&lt;br /&gt;
** ストリーミングレプリケーション&lt;br /&gt;
** 除外制約&lt;br /&gt;
** LISTEN/NOTIFY&lt;br /&gt;
** DO文（各種言語で）&lt;br /&gt;
** 追加されたウィンドウ関数フレーム&lt;br /&gt;
** その他募集中&lt;br /&gt;
* データベース移行テスト データの用意もお願いします！&lt;br /&gt;
* アプリケーション移行テスト&lt;br /&gt;
** MediaWiki&lt;br /&gt;
** Slony&lt;br /&gt;
** Bucardo&lt;br /&gt;
** pgsnmpd&lt;br /&gt;
** pgpool&lt;br /&gt;
** textsearch_senna&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ドライバ&lt;br /&gt;
** Java&lt;br /&gt;
** Python&lt;br /&gt;
*** psycopg2&lt;br /&gt;
** Perl&lt;br /&gt;
*** DBD::Pg&lt;br /&gt;
** R&lt;br /&gt;
** Ruby&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ORMツール&lt;br /&gt;
** SQLAlchemy&lt;br /&gt;
** Django&lt;br /&gt;
** Hibernate&lt;br /&gt;
** その他募集中&lt;br /&gt;
&lt;br /&gt;
9を先取りして勉強することができます。記事等観てもぱっとわからない機能も隣の人が教えてくれます。また、PostgreSQLの今後の開発や普段疑問に思っていることなどについて自由にディスカッションできます。たぶん飲みながらやるのでぐだぐだになりそうです。&lt;br /&gt;
&lt;br /&gt;
== 場所 ==&lt;br /&gt;
フォルシア株式会社 会議室&lt;br /&gt;
&lt;br /&gt;
東京都新宿区新宿4丁目3-25 オリックス新宿ビル9階&lt;br /&gt;
[http://maps.google.co.jp/maps?f=q&amp;amp;hl=ja&amp;amp;geocode=&amp;amp;time=&amp;amp;date=&amp;amp;ttype=&amp;amp;q=%93%8C%8B%9E%93s%90V%8Fh%8B%E6%90V%8Fh%82S%92%9A%96%DA%82R-%82Q%82T&amp;amp;ie=UTF8&amp;amp;ll=35.689321,139.704277&amp;amp;spn=0.010386,0.013776&amp;amp;z=14&amp;amp;iwloc=addr&amp;amp;om=1&amp;amp;source=embed Google Map]&lt;br /&gt;
&lt;br /&gt;
新宿駅南口徒歩3分&lt;br /&gt;
東京メトロ新宿3丁目駅徒歩1分&lt;br /&gt;
&lt;br /&gt;
== 時間 ==&lt;br /&gt;
4月4日 午前3時～午前10時（日本時間）&lt;br /&gt;
※サンフランシスコ時間4月3日午前11時～午後6時で行われるTestに合わせています。&lt;br /&gt;
&lt;br /&gt;
時間が時間なので前日からのスタンバイあり&lt;br /&gt;
&lt;br /&gt;
== 食事 ==&lt;br /&gt;
軽食を用意します。持ち込み（飲食）歓迎。徒歩圏内でも調達可能。&lt;br /&gt;
&lt;br /&gt;
== 持ち物 ==&lt;br /&gt;
ラップトップ持参。インターネット環境（DHCP）は用意します。Wi-fiに対応できるかは調整中。各自テスト環境を外部サーバに用意できれば尚可。&lt;br /&gt;
&lt;br /&gt;
ラップトップは若干台数貸し出し可能です。お気軽にご連絡ください。&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ &lt;br /&gt;
&#039;&#039;&#039;準備機材&#039;&#039;&#039;&lt;br /&gt;
| &#039;&#039;&#039;所有者&#039;&#039;&#039; || &#039;&#039;&#039;物品&#039;&#039;&#039;  || &#039;&#039;&#039;備考&#039;&#039;&#039; &lt;br /&gt;
|-&lt;br /&gt;
| 永安 || AirMac Express（無線LAN AP)  || &lt;br /&gt;
|-&lt;br /&gt;
| 永安 || VAIO X || 作業用&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || MacBook || テスト用or作業用&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || HP 2133 mini || 誰か必要な人がいれば貸し出し用&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ &lt;br /&gt;
&#039;&#039;&#039;テスト環境&#039;&#039;&#039;&lt;br /&gt;
| &#039;&#039;&#039;所有者&#039;&#039;&#039; || &#039;&#039;&#039;アーキテクチャ&#039;&#039;&#039; || &#039;&#039;&#039;OS&#039;&#039;&#039; || &#039;&#039;&#039;IPアドレス&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || Red Hat Enterprise Linux 5.4 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || CentOS 5.3 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || FreeBSD 6.4 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32  || MacOS X 10.5.8 || x.x.x.x&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86 || 未定 || （Amazon EC2）&lt;br /&gt;
|-&lt;br /&gt;
| 原田 || x64 || Windows || Amazon EC2&lt;br /&gt;
|-&lt;br /&gt;
| 原田 || x86,x64 || Linux(some distros) x N || Amazon EC2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== 参加者一覧 ==&lt;br /&gt;
&lt;br /&gt;
ATNDを参照ください。&lt;br /&gt;
http://atnd.org/events/3785&lt;br /&gt;
&lt;br /&gt;
== その他 ==&lt;br /&gt;
* TwitterでSFPUGと連携します（したいです）&lt;br /&gt;
* Ustreamできるかどうか検討中。東京にいない人も参加するなら必須？機器を用意できる方歓迎。&lt;br /&gt;
* ライトニングトーク？&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=Todo&amp;diff=10346</id>
		<title>Todo</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=Todo&amp;diff=10346"/>
		<updated>2010-03-29T14:46:15Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* Window Functions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;margin: 1ex 1em; float: right;&amp;quot;&amp;gt;&lt;br /&gt;
__TOC__&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This list contains &#039;&#039;&#039;all known PostgreSQL bugs and feature requests&#039;&#039;&#039;. If you would like to work on an item, please read the [[Developer FAQ]] first. There is also a [[Development_information|development information page]].&lt;br /&gt;
&lt;br /&gt;
* {{TodoPending}} - marks ordinary, incomplete items&lt;br /&gt;
* {{TodoEasy}} - marks items that are easier to implement&lt;br /&gt;
* {{TodoDone}} - marks changes that are done, and will appear in the next major release&lt;br /&gt;
&lt;br /&gt;
For help on editing this list, please see [[Talk:Todo]]. &amp;lt;b&amp;gt;Please do not add items here without discussion on the mailing list.&amp;lt;/b&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;padding: 1ex 4em;&amp;quot;&amp;gt;&lt;br /&gt;
== Administration ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow administrators to cancel multi-statement idle transactions&lt;br /&gt;
|This allows locks to be released, but it is complex to report the cancellation back to the client.&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-12/msg01340.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-12/msg00441.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Check for unreferenced table files created by transactions that were in-progress when the server terminated abruptly&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php &amp;lt;nowiki&amp;gt;Removing unreferenced files&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Set proper permissions on non-system schemas during db creation&lt;br /&gt;
|Currently all schemas are owned by the super-user because they are copied from the template1 database.  However, since all objects are inherited from the template database, it is not clear that setting schemas to the db owner is correct.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow log_min_messages to be specified on a per-module basis&lt;br /&gt;
|This would allow administrators to see more detailed information from specific sections of the backend, e.g. checkpoints, autovacuum, etc. Another idea is to allow separate configuration files for each module, or allow arbitrary SET commands to be passed to them. See also [[Logging Brainstorm]].}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Simplify ability to create partitioned tables&lt;br /&gt;
|This would allow creation of partitioned tables without requiring creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints for rapid partition selection.  Options could include range and hash partition selection. See also [[Table partitioning]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow auto-selection of partitioned tables for min/max() operations&lt;br /&gt;
|There was a patch on -hackers from July 2009, but it has not been merged: http://archives.postgresql.org/pgsql-hackers/2009-07/msg01115.php}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Allow more complex user/database default GUC settings&lt;br /&gt;
|Currently ALTER USER and ALTER DATABASE support per-user and per-database defaults.  Consider adding per-user-and-database defaults so things like search_path can be defaulted for a specific user connecting to a specific database.&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-09/msg02345.php &amp;lt;nowiki&amp;gt;Re: Per-database search_path&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* http://archives.postgresql.org/message-id/20090811221921.GK16362@alvh.no-ip.org&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow custom variables to appear in pg_settings()&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-06/msg00850.php &amp;lt;nowiki&amp;gt;Re: count(*) performance improvement ideas&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow custom variable classes that can restrict who can set the values&lt;br /&gt;
|The common cases (POSTMASTER, SIGHUP, and SUSET) are already handled to some extent as of 8.4.  Should we mark this DONE?&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-11/msg00911.php &amp;lt;nowiki&amp;gt;custom variable classes&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Implement the SQL standard mechanism whereby REVOKE ROLE revokes only the privilege granted by the invoking role, and not those granted by other roles&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-bugs/2007-05/msg00010.php &amp;lt;nowiki&amp;gt;Re: Grantor name gets lost when grantor role dropped&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve server security options&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg01875.php &amp;lt;nowiki&amp;gt;Re: [0/4] Proposal of SE-PostgreSQL patches&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00000.php &amp;lt;nowiki&amp;gt;Re: [0/4] Proposal of SE-PostgreSQL patches&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Prevent query cancel packets from being replayed by an attacker, especially when using SSL&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-08/msg00345.php &amp;lt;nowiki&amp;gt;Replay attack of query cancel&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Provide a way to query the log collector subprocess to determine what the currently active log file is&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-general/2008-11/msg00418.php &amp;lt;nowiki&amp;gt;Current log files when rotating?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow the client to authenticate the server in a Unix-domain socket connection, e.g., using SO_PEERCRED&lt;br /&gt;
* http://archives.postgresql.org/message-id/20090401173756.GB21229@svana.org&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Allow the client to set an application_name to appear in pg_stat_activity&lt;br /&gt;
* http://archives.postgresql.org/message-id/407d949e0907161237r76ebd92av6836c6563d8a230e@mail.gmail.com&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Allow server-side enforcement of password policies&lt;br /&gt;
|Password checks might include password complexity or non-reuse of passwords.  This facility will require the client to send password creation/changes to the server in plain-text, not MD5.&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-09/msg01766.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-10/msg00025.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow custom daemons to be automatically stopped/started along postmaster&lt;br /&gt;
|This allows easier administration of daemons like user job schedulers or replication-related daemons.&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2010-02/msg01701.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Have custom GUCs be transaction safe&lt;br /&gt;
* {{MessageLink|4B577E9F.8000505@dunslane.net|Custom GUCs still a bit broken}}&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=== Configuration files ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow pg_hba.conf to specify host names along with IP addresses&lt;br /&gt;
|Host name lookup could occur when the postmaster reads the pg_hba.conf file, or when the backend starts.  Another solution would be to reverse lookup the connection IP and check that hostname against the host names in pg_hba.conf. We could also then check that the host name maps to the IP address. &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-06/msg00569.php &amp;lt;nowiki&amp;gt;TODO Item: Allow pg_hba.conf to specify host names along with IP addresses&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow postgresql.conf file values to be changed via an SQL API, perhaps using SET GLOBAL}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow the server to be stopped/restarted via an SQL API}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider normalizing fractions in postgresql.conf, perhaps using &#039;%&#039;&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-06/msg00550.php &amp;lt;nowiki&amp;gt;Fractions in GUC variables&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow Kerberos to disable stripping of realms so we can check the username@realm against multiple realms&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg00009.php &amp;lt;nowiki&amp;gt;krb_match_realm patch&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add functions to check correctness of configuration files before they are loaded &amp;quot;live&amp;quot;}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve LDAP authentication configuration options&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg01745.php &amp;lt;nowiki&amp;gt;Proposed Patch - LDAPS support for servers on port 636 w/o TLS&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add external tool to auto-tune some postgresql.conf parameters&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-06/msg00000.php &amp;lt;nowiki&amp;gt;Re: Overhauling GUCS&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-11/msg00033.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add &#039;hostgss&#039; pg_hba.conf option to allow GSS link-level encryption&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-07/msg01454.php &amp;lt;nowiki&amp;gt;Re: Plans for 8.4&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Process pg_hba.conf keywords as case-insensitive&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-09/msg00432.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== Tablespaces ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow a database in tablespace t1 with tables created in tablespace t2 to be used as a template for a new database created with default tablespace t2&lt;br /&gt;
|Currently all objects in the default database tablespace must have default tablespace specifications. This is because new databases are created by copying directories. If you mix default tablespace tables and tablespace-specified tables in the same directory, creating a new database from such a mixed directory would create a new database with tables that had incorrect explicit tablespaces.  To fix this would require modifying pg_class in the newly copied database, which we don&#039;t currently do.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow reporting of which objects are in which tablespaces&lt;br /&gt;
|This item is difficult because a tablespace can contain objects from multiple databases. There is a server-side function that returns the databases which use a specific tablespace, so this requires a tool that will call that function and connect to each database to find the objects in each database for that tablespace.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow WAL replay of CREATE TABLESPACE to work when the directory structure on the recovery computer is different from the original}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow per-tablespace quotas}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Allow per-tablespace random_page_cost&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-10/msg01128.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-10/msg01486.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== Statistics Collector ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow statistics last vacuum/analyze execution times to be displayed without requiring track_counts to be enabled&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-docs/2007-04/msg00028.php &amp;lt;nowiki&amp;gt;row-level stats and last analyze time&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Clear table counters on TRUNCATE&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg00169.php &amp;lt;nowiki&amp;gt;Small TRUNCATE glitch&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
| Allow the clearing of cluster-level statistics&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-03/msg00917.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== Point-In-Time Recovery (PITR) ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Allow a warm standby system to also allow read-only statements&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php &amp;lt;nowiki&amp;gt;Updated propsoal for read-only queries on PITR slaves (SoC 2007)&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemEasy&lt;br /&gt;
|Create dump tool for write-ahead logs for use in determining transaction id for point-in-time recovery&lt;br /&gt;
|This is useful for checking PITR recovery.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow recovery.conf to support the same syntax as postgresql.conf, including quoting&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php &amp;lt;nowiki&amp;gt;recovery.conf parsing problems&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow archive_mode to be changed without server restart?&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-10/msg01655.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider avoiding WAL switching via archive_timeout if there has been no database activity&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2010-01/msg01469.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2010-02/msg00395.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemEasy&lt;br /&gt;
|[http://archives.postgresql.org/message-id/4B901D73.8030003@agliodbs.com Expose pg_controldata via SQL interface]&lt;br /&gt;
|Helpful for monitoring replicated databases}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== SSL ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow SSL authentication/encryption over unix domain sockets&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-12/msg00924.php &amp;lt;nowiki&amp;gt;Re: Spoofing as the postmaster&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow SSL key file permission checks to be optionally disabled when sharing SSL keys with other applications&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-bugs/2007-12/msg00069.php &amp;lt;nowiki&amp;gt;BUG #3809: SSL &amp;amp;quot;unsafe&amp;amp;quot; private key permissions bug&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow SSL CRL files to be re-read during configuration file reload, rather than requiring a server restart&lt;br /&gt;
|Unlike SSL CRT files, CRL (Certificate Revocation List) files are updated frequently&lt;br /&gt;
* http://archives.postgresql.org/pgsql-general/2008-12/msg00832.php&lt;br /&gt;
Alternatively or additionally supporting OCSP (online certificate security protocol) would provide real-time revocation discovery without reloading&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
| Allow automatic selection of SSL client certificates from a certificate store&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2009-05/msg00406.php &amp;lt;nowiki&amp;gt;Allow multiple certificates or keys in the postgresql.crt/.key files&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Data Types ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Change NUMERIC to enforce the maximum precision}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Reduce storage space for small NUMERICs&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-02/msg01331.php &amp;lt;nowiki&amp;gt;Saving space for common kinds of numeric values&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2007-02/msg00505.php &amp;lt;nowiki&amp;gt;Numeric patch to add special-case representations for &amp;amp;lt; 8 bytes&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-06/msg00715.php &amp;lt;nowiki&amp;gt;Re: Reducing NUMERIC size for 8.3&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix data types where equality comparison isn&#039;t intuitive, e.g. box}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add support for public SYNONYMs&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-03/msg00519.php &amp;lt;nowiki&amp;gt;Proposal for SYNONYMS&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add support for SQL-standard GENERATED/IDENTITY columns&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-07/msg00543.php &amp;lt;nowiki&amp;gt;Re: Three weeks left until feature freeze&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-08/msg00038.php &amp;lt;nowiki&amp;gt;GENERATED ... AS IDENTITY, Was: Re: Feature Freeze&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-05/msg00344.php &amp;lt;nowiki&amp;gt;Behavior of GENERATED columns per SQL2003&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2007-05/msg00076.php &amp;lt;nowiki&amp;gt;Re: [HACKERS] Behavior of GENERATED columns per SQL2003&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00604.php &amp;lt;nowiki&amp;gt;IDENTITY/GENERATED patch&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider placing all sequences in a single table, or create a system view&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php &amp;lt;nowiki&amp;gt;Re: newbie: renaming sequences task&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider a special data type for regular expressions&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-08/msg01067.php &amp;lt;nowiki&amp;gt;Why is there a tsquery data type?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Reduce BIT data type overhead using short varlena headers&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-general/2007-12/msg00273.php &amp;lt;nowiki&amp;gt;storage size of &amp;amp;quot;bit&amp;amp;quot; data type..&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow adding/renaming/removing enumerated values to an existing enumerated data type&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg01718.php &amp;lt;nowiki&amp;gt;Re: [COMMITTERS] pgsql: Update:  &amp;amp;lt; * Allow adding enumerated	values to an existing&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Support scoped IPv6 addresses in inet type&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-bugs/2007-05/msg00111.php &amp;lt;nowiki&amp;gt;strange problem with ip6&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add JSON (JavaScript Object Notation) data type&lt;br /&gt;
|This would behave similar to the XML data type, which is stored as text, but allows element lookup and conversion functions.&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-12/msg01494.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2010-01/msg00001.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Considering improving performance of computing CHAR() value lengths&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-06/msg00900.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2010-02/msg01787.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=== Domains ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix CREATE CAST on DOMAINs&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-05/msg00072.php &amp;lt;nowiki&amp;gt;bug? non working casts for domain&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-09/msg01681.php &amp;lt;nowiki&amp;gt;TODO: Fix CREATE CAST on DOMAINs&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow domains to be cast&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2003-06/msg01206.php &amp;lt;nowiki&amp;gt;Domain casting still doesn&#039;t work right&amp;lt;/nowiki&amp;gt;] &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-08/msg00289.php &amp;lt;nowiki&amp;gt;domain casting?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Make domains work better with polymorphic functions&lt;br /&gt;
* [http://archives.postgresql.org/message-id/4887.1228700773@sss.pgh.pa.us Polymorphic types vs. domains]&lt;br /&gt;
* [http://archives.postgresql.org/message-id/15535.1238774571@sss.pgh.pa.us some difficulties with fixing it]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== Dates and Times ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow infinite intervals just like infinite timestamps}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow TIMESTAMP WITH TIME ZONE to store the original timezone information, either zone name or offset from UTC&lt;br /&gt;
|If the TIMESTAMP value is stored with a time zone name, interval computations should adjust based on the time zone rules. &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2004-10/msg00705.php &amp;lt;nowiki&amp;gt;timestamp with time zone a la sql99&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix SELECT &#039;0.01 years&#039;::interval, &#039;0.01 months&#039;::interval}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Have timestamp subtraction not call justify_hours()?&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-sql/2006-10/msg00059.php &amp;lt;nowiki&amp;gt;timestamp subtraction (was Re: formatting intervals with to_char)&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve timestamptz subtraction to be DST-aware&lt;br /&gt;
|Currently subtracting one date from another that crosses a daylight savings time adjustment can return &#039;1 day 1 hour&#039;, but adding that back to the first date returns a time one hour in the future.  This is caused by the adjustment of &#039;25 hours&#039; to &#039;1 day 1 hour&#039;, and &#039;1 day&#039; is the same time the next day, even if daylight savings adjustments are involved.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix interval display to support values exceeding 2^31 hours}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add overflow checking to timestamp and interval arithmetic}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Revise the src/timezone/tznames abbreviation files:&lt;br /&gt;
* to add missing abbreviations&lt;br /&gt;
* to find abbreviations that can be safely promoted to the Default list&lt;br /&gt;
* {{messageLink|7867.1219793881@sss.pgh.pa.us|BUG #4377: casting result of timeofday() to timestamp fails in some timezones}}}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== Arrays ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add support for arrays of domains&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2007-05/msg00114.php &amp;lt;nowiki&amp;gt;Re: updated WIP: arrays of composites&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow single-byte header storage for array elements}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add function to detect if an array is empty&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-11/msg00475.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve handling of empty arrays&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-10/msg01033.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve handling of NULLs in arrays&lt;br /&gt;
* http://archives.postgresql.org/pgsql-bugs/2008-11/msg00009.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== Binary Data ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve vacuum of large objects, like contrib/vacuumlo?}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Add security checks for large objects}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Auto-delete large objects when referencing row is deleted&lt;br /&gt;
|contrib/lo offers this functionality.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow read/write into TOAST values like large objects&lt;br /&gt;
|This requires the TOAST column to be stored EXTERNAL.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add API for 64-bit large object access&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php &amp;lt;nowiki&amp;gt;64-bit API for large objects&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== MONEY Data Type ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add locale-aware MONEY type, and support multiple currencies&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php &amp;lt;nowiki&amp;gt;A real currency type&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg01181.php &amp;lt;nowiki&amp;gt;Money type todos?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|MONEY dumps in a locale-specific format making it difficult to restore to a system with a different locale}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow MONEY to be easily cast to/from other numeric data types}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== Text Search ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow dictionaries to change the token that is passed on to later dictionaries&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2007-11/msg00081.php &amp;lt;nowiki&amp;gt;a tsearch2 (8.2.4) dictionary that only filters out stopwords&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider a function-based API for &#039;@@&#039; searches&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg00511.php &amp;lt;nowiki&amp;gt;Simplifying Text Search&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve text search error messages&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-10/msg00966.php &amp;lt;nowiki&amp;gt;Poorly designed tsearch NOTICEs&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg01146.php &amp;lt;nowiki&amp;gt;Re: Poorly designed tsearch NOTICEs&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider changing error to warning for strings larger than one megabyte&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-bugs/2008-02/msg00190.php &amp;lt;nowiki&amp;gt;BUG #3975: tsearch2 index should not bomb out of 1Mb limit&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2008-03/msg00062.php &amp;lt;nowiki&amp;gt;Re: [BUGS] BUG #3975: tsearch2 index should not bomb out of 1Mb limit&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|tsearch and tsdicts regression tests fail in Turkish locale on glibc&lt;br /&gt;
* [http://archives.postgresql.org/message-id/49749645.5070801@gmx.net tsearch with Turkish locale]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== XML ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow xml arrays to be cast to other data types&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-09/msg00981.php &amp;lt;nowiki&amp;gt;proposal casting from XML[] to int[], numeric[], text[]&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-10/msg00231.php &amp;lt;nowiki&amp;gt;Re: proposal casting from XML[] to int[], numeric[], text[]&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg00471.php &amp;lt;nowiki&amp;gt;Re: proposal casting from XML[] to int[], numeric[], text[]&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add XML Schema validation and xmlvalidate function (SQL:2008)}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add xmlvalidatedtd variant to support validating against a DTD?}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Relax-NG validation; libxml2 supports this already}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Make it work reliably for non-UTF8 server encoding (xpath()) in particular is known to not work)&lt;br /&gt;
* http://archives.postgresql.org/pgsql-bugs/2009-01/msg00135.php &lt;br /&gt;
* http://archives.postgresql.org/message-id/4110.1238973350@sss.pgh.pa.us}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Extra functions from SQL:2006: XMLDOCUMENT, XMLCAST, XMLTEXT}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Inline ORDER BY for XMLAGG. Example: &amp;quot;... XMLAGG(XMLELEMENT(...) ORDER BY col1) ...&amp;quot; (should be made to work with all aggregate functions)}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|XMLNAMESPACES support in XMLELEMENT and elsewhere}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|XSLT support; already available in contrib/xml2, but needs API fixes and adaptation to xml type.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|XML Canonical: Convert XML documents to canonical form to compare them. libxml2 has support for this.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Pretty-printing XML: Parse a document and serialize it back in some indented form. libxml2 might support this.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|XMLQUERY (from SQL/XML standard)}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|In some cases shredding could be better option (if there is no need in keeping XML docs entirely; if we have already developed tools that understand only relational data; etc) -- it would be a separate module that implements annotated schema decomposition technique, similar to DB2 and SQL Server functionality.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
| Nested or repeated xpath() apparently mess up namespaces [http://archives.postgresql.org/pgsql-bugs/2008-03/msg00097.php] [http://archives.postgresql.org/pgsql-bugs/2008-03/msg00144.php] [http://archives.postgresql.org/pgsql-general/2008-03/msg00295.php] [http://archives.postgresql.org/pgsql-bugs/2008-07/msg00054.php] [http://archives.postgresql.org/message-id/004f01c90e91$138e9d10$3aabd730$@anstett@iaas.uni-stuttgart.de]}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|XPath: Adding the &amp;lt;x&amp;gt; at the root causes problems [http://archives.postgresql.org/pgsql-bugs/2008-05/msg00184.php] [http://archives.postgresql.org/pgsql-bugs/2008-07/msg00054.php] [http://archives.postgresql.org/pgsql-general/2008-07/msg00613.php]}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|xpath_table needs to be implemented/implementable to get rid of contrib/xml2 [http://archives.postgresql.org/pgsql-general/2008-05/msg00823.php]}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|better handling of XPath data types [http://archives.postgresql.org/pgsql-hackers/2008-06/msg00616.php] [http://archives.postgresql.org/message-id/004a01c90e90$4b986d90$e2c948b0$@anstett@iaas.uni-stuttgart.de]}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|xpath_exists() is needed. It checks, whether or not the path specified exists in the XML value. (W/o this function we need to use weird &amp;quot;array_dims(xpath(...)) IS NOT NULL&amp;quot; syntax.)}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Functions ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow INET subnet tests using non-constants to be indexed}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow to_date() and to_timestamp() to accept localized month names}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add missing parameter handling in to_char()&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2005-12/msg00948.php &amp;lt;nowiki&amp;gt;Re: to_char and i18n&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Throw an error from to_char() instead of printing a string of &amp;quot;#&amp;quot; when a number doesn&#039;t fit in the desired output format.&lt;br /&gt;
* discussed in [http://archives.postgresql.org/message-id/37ed240d0907290836w42187222n18664dfcbcb445b1@mail.gmail.com &amp;quot;to_char, support for EEEE format&amp;quot;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Add functions to get/set bit values&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2004-01/msg00498.php &amp;lt;nowiki&amp;gt;implemented missing bitSetBit() and bitGetBit()&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2004-02/msg00478.php &amp;lt;nowiki&amp;gt;Re: implemented missing bitSetBit() and bitGetBit()&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow to_char() on interval values to accumulate the highest unit requested&lt;br /&gt;
|2= Some special format flag would be required to request such accumulation.  Such functionality could also be added to EXTRACT. Prevent accumulation that crosses the month/day boundary because of the uneven number of days in a month.&lt;br /&gt;
* to_char(INTERVAL &#039;1 hour 5 minutes&#039;, &#039;MI&#039;) =&amp;amp;gt; 65&lt;br /&gt;
* to_char(INTERVAL &#039;43 hours 20 minutes&#039;, &#039;MI&#039; ) =&amp;amp;gt; 2600&lt;br /&gt;
* to_char(INTERVAL &#039;43 hours 20 minutes&#039;, &#039;WK:DD:HR:MI&#039;) =&amp;amp;gt; 0:1:19:20&lt;br /&gt;
* to_char(INTERVAL &#039;3 years 5 months&#039;,&#039;MM&#039;) =&amp;amp;gt; 41}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow SQL-language functions to reference parameters by parameter name&lt;br /&gt;
|Currently SQL-language functions can only refer to dollar parameters, e.g. $1}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add SPI_gettypmod() to return the typemod for a TupleDesc}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Enforce typmod for function inputs, function results and parameters for spi_prepare&#039;d statements called from PLs&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-01/msg01403.php &amp;lt;nowiki&amp;gt;Re: BUG #2917: spi_prepare doesn&#039;t accept typename aliases&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-11/msg01160.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow holdable cursors in SPI}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Tighten function permission checks&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00568.php &amp;lt;nowiki&amp;gt;Re: Security leak with trigger functions?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix IS OF so it matches the ISO specification, and add documentation&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2003-08/msg00060.php &amp;lt;nowiki&amp;gt;Re: [HACKERS] IS OF&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-02/msg00060.php &amp;lt;nowiki&amp;gt;ToDo: add documentation for operator IS OF&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add missing operators for geometric data types&lt;br /&gt;
|Some geometric types do not have the full suite of geometric operators, e.g. box @&amp;amp;gt; point&lt;br /&gt;
* {{messageLink|4B0A8F0F.3020308@sigaev.ru|point_ops for GiST}}&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Implement Boyer-Moore searching in LIKE queries&lt;br /&gt;
* {{messageLink|27645.1220635769@sss.pgh.pa.us|TODO item: Implement Boyer-Moore searching (First time hacker)}}&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Prevent malicious functions from being executed with the permissions of unsuspecting users&lt;br /&gt;
|Index functions are safe, so VACUUM and ANALYZE are safe too.  Triggers, CHECK and DEFAULT expressions, and rules are still vulnerable. &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00268.php &amp;lt;nowiki&amp;gt;Some notes about the index-functions security vulnerability&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Reduce memory usage of aggregates in set returning functions&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-performance/2008-01/msg00031.php &amp;lt;nowiki&amp;gt;Re: Performance of aggregates over set-returning functions&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix /contrib/ltree operator&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-bugs/2007-11/msg00044.php &amp;lt;nowiki&amp;gt;BUG #3720: wrong results at using ltree&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|&amp;lt;nowiki&amp;gt;Fix inconsistent precedence of =, &amp;amp;gt;, and &amp;amp;lt; compared to &amp;amp;lt;&amp;amp;gt;, &amp;amp;gt;=, and &amp;amp;lt;=&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-bugs/2007-12/msg00145.php &amp;lt;nowiki&amp;gt;BUG #3822: Nonstandard precedence for comparison operators&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix regular expression bug when using complex back-references&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-bugs/2007-10/msg00000.php &amp;lt;nowiki&amp;gt;BUG #3645: regular expression back references seem broken&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Have /contrib/dblink reuse unnamed connections&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-10/msg00895.php &amp;lt;nowiki&amp;gt;dblink un-named connection doesn&#039;t get re-used&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow calling of a procedure outside a SELECT that can control the transaction state&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-10/msg01375.php &amp;lt;nowiki&amp;gt;Proposal: real procedures again (8.4)&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Add has_sequence_privilege()&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-09/msg00032.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve formatting of pg_get_viewdef() output&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-01/msg01648.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-08/msg01885.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add printf()-like functionality&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-09/msg00367.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix to_number() handling for values not matching the format string&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-09/msg01447.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add function to dump pg_depend information cleanly&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-09/msg00226.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Multi-Language Support ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add NCHAR (as distinguished from ordinary varchar),}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow more fine-grained collation selection; add CREATE COLLATION.&lt;br /&gt;
|Right now the collation is fixed at database creation time.&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php &amp;lt;nowiki&amp;gt;Re: Patch for collation using ICU&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2005-08/msg00039.php &amp;lt;nowiki&amp;gt;FW: Win32 unicode vs ICU&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2005-08/msg00309.php &amp;lt;nowiki&amp;gt;Re: FW: Win32 unicode vs ICU&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2005-09/msg00110.php &amp;lt;nowiki&amp;gt;Proof of concept COLLATE support with patch&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2005-09/msg00020.php &amp;lt;nowiki&amp;gt;For review: Initial support for COLLATE&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2005-12/msg01121.php &amp;lt;nowiki&amp;gt;Proposed COLLATE implementation&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-01/msg00767.php &amp;lt;nowiki&amp;gt;TODO item: locale per database patch (new iteration)&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2006-03/msg00233.php &amp;lt;nowiki&amp;gt;Re: FW: Win32 unicode vs ICU&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-09/msg00662.php &amp;lt;nowiki&amp;gt;Re: Fixed length data types issue&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-07/msg00557.php&lt;br /&gt;
* [[Todo:Collate]]&lt;br /&gt;
* [[Todo:ICU]]&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-08/msg01362.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-09/msg00012.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-10/msg00868.php&lt;br /&gt;
* [http://www.unicode.org/unicode/reports/tr10/ Unicode collation algorithm]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add a LOCALE option to CREATE DATABASE, as a shorthand&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg00119.php &amp;lt;nowiki&amp;gt; Re: 8.4 open items list&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Support multiple simultaneous character sets, per SQL:2008}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve UTF8 combined character handling?}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add octet_length_server() and octet_length_client()}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Make octet_length_client() the same as octet_length()?}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix problems with wrong runtime encoding conversion for NLS message files}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add URL to more complete multi-byte regression tests&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2005-07/msg00272.php &amp;lt;nowiki&amp;gt;Multi-byte and client side character encoding tests for copy command..&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix contrib/fuzzystrmatch to work with multibyte encodings&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-bugs/2009-04/msg00047.php &amp;lt;nowiki&amp;gt; soundex function returns UTF-16 characters&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Set client encoding based on the client operating system encoding&lt;br /&gt;
|Currently client_encoding is set in postgresql.conf, which defaults to the server encoding. &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-08/msg01696.php &amp;lt;nowiki&amp;gt;Re: [GENERAL] invalid byte sequence ?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Change memory allocation for multi-byte functions so memory is allocated inside conversion functions&lt;br /&gt;
|Currently we preallocate memory based on worst-case usage.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add ability to use case-insensitive regular expressions on multi-byte characters&lt;br /&gt;
|ILIKE already works with multi-byte characters&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-12/msg00433.php&lt;br /&gt;
* {{MessageLink|20091201210024.B1393753FB7@cvs.postgresql.org|A partial solution for UTF-8}}&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve encoding of connection startup messages sent to the client&lt;br /&gt;
|Currently some authentication error messages are sent in the server encoding&lt;br /&gt;
* http://archives.postgresql.org/pgsql-general/2008-12/msg00801.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-general/2009-01/msg00005.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Have pg_stat_activity display query strings in the correct client encoding&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-01/msg00131.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|More sensible support for Unicode combining characters, normal forms&lt;br /&gt;
* http://archives.postgresql.org/message-id/200904141532.44618.peter_e@gmx.net&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Views / Rules ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Automatically create rules on views so they are updateable, per SQL:2008&lt;br /&gt;
|We can only auto-create rules for simple views.  For more complex cases users will still have to write rules manually.&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-03/msg00586.php &amp;lt;nowiki&amp;gt;Proposal for updatable views&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2006-08/msg00255.php &amp;lt;nowiki&amp;gt;Updatable views&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-01/msg01746.php&lt;br /&gt;
* http://wiki.postgresql.org/wiki/Updatable_views&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add the functionality for WITH CHECK OPTION clause of CREATE VIEW}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow VIEW/RULE recompilation when the underlying tables change&lt;br /&gt;
|This is both difficult and controversial.&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2009-12/msg01723.php Re: About &amp;quot;Allow VIEW/RULE recompilation when the underlying tables change&amp;quot;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2009-12/msg01724.php Re: About &amp;quot;Allow VIEW/RULE recompilation when the underlying tables change&amp;quot;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Make it possible to use RETURNING together with conditional DO INSTEAD rules, such as for partitioning setups&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-09/msg00577.php &amp;lt;nowiki&amp;gt;RETURNING and DO INSTEAD ... Intentional or not?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add the ability to automatically create materialized views&lt;br /&gt;
|Right now materialized views require the user to create triggers on the main table to keep the summary table current.  SQL syntax should be able to manage the triggers and summary table automatically.  A more sophisticated implementation would automatically retrieve from the summary table when the main table is referenced, if possible.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve ability to modify views via ALTER TABLE&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00691.php &amp;lt;nowiki&amp;gt;Re: idea: storing view source in system catalogs&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-07/msg01410.php &amp;lt;nowiki&amp;gt;modifying views&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-08/msg00300.php &amp;lt;nowiki&amp;gt;Re: patch: Add columns via CREATE OR REPLACE VIEW&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Prevent low-cost functions from seeing unauthorized view rows&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-10/msg01346.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== SQL Commands ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add CORRESPONDING BY to UNION/INTERSECT/EXCEPT}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add ROLLUP, CUBE, GROUPING SETS options to GROUP BY&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-10/msg00838.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-05/msg00466.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemEasy&lt;br /&gt;
|Allow SET CONSTRAINTS to be qualified by schema/table name}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemEasy&lt;br /&gt;
|Fix TRUNCATE ... RESTART IDENTITY so its effect on sequences is rolled back on transaction abort&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00550.php &amp;lt;nowiki&amp;gt;Re: [PATCHES] TRUNCATE TABLE with IDENTITY&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow PREPARE of cursors}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow finer control over the caching of prepared query plans&lt;br /&gt;
|Currently anonymous (un-named) queries prepared via the wire protocol are replanned every time bind parameters are supplied --- allow SQL PREPARE to do the same.  Also, allow control over replanning prepared queries either manually or automatically when statistics for execute parameters differ dramatically from those used during planning.&lt;br /&gt;
* http://archives.postgresql.org/message-id/201002151911.o1FJBYh22763@momjian.us&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve logging of prepared transactions recovered during startup&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-11/msg00092.php &amp;lt;nowiki&amp;gt;&amp;amp;quot;recovering prepared transaction&amp;amp;quot; after server restart message&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow prepared transactions with temporary tables created and dropped in the same transaction, and when an ON COMMIT DELETE ROWS temporary  table is accessed&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00047.php &amp;lt;nowiki&amp;gt;Re: &amp;amp;quot;could not open relation 1663/16384/16584: No such file or directory&amp;amp;quot; in a specific combination of transactions with temp tables&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/message-id/492543D5.9050904@enterprisedb.com A suggestion on how to implement this]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add a GUC variable to warn about non-standard SQL usage in queries}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add SQL-standard MERGE/REPLACE/UPSERT command&lt;br /&gt;
|MERGE is typically used to merge two tables.  REPLACE or UPSERT command does UPDATE, or on failure, INSERT. This is similar to UPDATE, then for unmatched rows, INSERT.  Whether concurrent access allows modifications which could cause row loss is implementation independent. To implement this cleanly requires that the table have a unique index so duplicate checking can be easily performed.  It is possible to do it without a unique index if we require the user to LOCK the table before the MERGE.&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2005-11/msg00501.php &amp;lt;nowiki&amp;gt;someone working to add merge?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2005-11/msg00536.php &amp;lt;nowiki&amp;gt;MERGE vs REPLACE&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg01157.php &amp;lt;nowiki&amp;gt;MERGE SQL Statement&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg01475.php &amp;lt;nowiki&amp;gt;MERGE Specification&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg01890.php &amp;lt;nowiki&amp;gt;Internal design of MERGE, with Rules&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add NOVICE output level for helpful messages like automatic sequence/index creation}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add GUC to issue notice about statements that use unjoined tables}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow EXPLAIN to identify tables that were skipped because of constraint_exclusion}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Allow EXPLAIN output to be more easily processed by scripts, perhaps XML&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-05/msg00857.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Enable standard_conforming_strings by default in 9.1?&lt;br /&gt;
|When this is done, backslash-quote should be prohibited in non-E&amp;lt;nowiki&amp;gt;&#039;&#039;&amp;lt;/nowiki&amp;gt; strings because of possible confusion over how such strings treat backslashes.  Basically, &amp;lt;nowiki&amp;gt;&#039;&#039;&amp;lt;/nowiki&amp;gt; is always safe for a literal single quote, while \&#039; might or might not be based on the backslash handling rules.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Simplify dropping roles that have objects in several databases}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow the count returned by SELECT, etc to be represented as an int64 to allow a higher range of values}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add support for WITH RECURSIVE ... CYCLE&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-10/msg00291.php}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add DEFAULT .. AS OWNER so permission checks are done as the table owner&lt;br /&gt;
|This would be useful for SERIAL nextval() calls and CHECK constraints.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow DISTINCT to work in multiple-argument aggregate calls}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add column to pg_stat_activity that shows the progress of long-running commands like CREATE INDEX and VACUUM&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2008-04/msg00203.php &amp;lt;nowiki&amp;gt;EXPLAIN progress info&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow INSERT/UPDATE/DELETE ... RETURNING inside a SELECT &#039;FROM&#039; clause or target list&lt;br /&gt;
|Actually it would be saner to allow this in WITH&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-general/2006-09/msg00803.php &amp;lt;nowiki&amp;gt;8.2: select from an INSERT returning?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-10/msg00693.php &amp;lt;nowiki&amp;gt;Re: SQL functions, INSERT/UPDATE/DELETE RETURNING, and triggers&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-06/msg00124.php &amp;lt;nowiki&amp;gt;cannot use result of (insert..returning)&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00979.php &amp;lt;nowiki&amp;gt;insert ... delete ... returning ... ?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-general/2009-06/msg00357.php Using results from DELETE ... RETURNING]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow INSERT/UPDATE/DELETE ... RETURNING in common table expressions&lt;br /&gt;
*  http://archives.postgresql.org/pgsql-hackers/2009-10/msg00472.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add comments on system tables/columns using the information in catalogs.sgml&lt;br /&gt;
|Ideally the information would be pulled from the SGML file automatically.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Prevent the specification of conflicting transaction read/write options&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-01/msg00684.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Support LATERAL subqueries&lt;br /&gt;
|Lateral subqueries can reference columns of tables defined outside the subquery at the same level, i.e. &#039;&#039;laterally&#039;&#039;.&lt;br /&gt;
For example, a LATERAL subquery in a FROM clause could reference tables defined in the same FROM clause.&lt;br /&gt;
Currently only the columns of tables defined &#039;&#039;above&#039;&#039; subqueries are recognized.&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-09/msg00292.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-10/msg00991.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Forbid COMMENT on columns of an index&lt;br /&gt;
|Postgres currently allows comments to be placed on the columns of an index, but pg_dump doesn&#039;t handle them and the column names themselves are implementation-dependent.&lt;br /&gt;
* http://archives.postgresql.org/message-id/27676.1237906577@sss.pgh.pa.us&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add support for functional dependencies&lt;br /&gt;
|This would allow omitting GROUP BY columns when grouping by the primary key.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=== CREATE ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow CREATE TABLE AS to determine column lengths for complex expressions like SELECT col1 || col2}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Have WITH CONSTRAINTS also create constraint indexes&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2007-04/msg00149.php &amp;lt;nowiki&amp;gt;Re: CREATE TABLE LIKE INCLUDING INDEXES support&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Move NOT NULL constraint information to pg_constraint&lt;br /&gt;
|Currently NOT NULL constraints are stored in pg_attribute without any designation of their origins, e.g. primary keys.  One manifest problem is that dropping a PRIMARY KEY constraint does not remove the NOT NULL constraint designation.  Another issue is that we should probably force NOT NULL to be propagated from parent tables to children, just as CHECK constraints are.  (But then does dropping PRIMARY KEY affect children?)&lt;br /&gt;
* http://archives.postgresql.org/message-id/19768.1238680878@sss.pgh.pa.us&lt;br /&gt;
* http://archives.postgresql.org/message-id/200909181005.n8IA5Ris061239@wwwmaster.postgresql.org&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Prevent concurrent CREATE TABLE from sometimes returning a cryptic error message&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-bugs/2007-10/msg00169.php &amp;lt;nowiki&amp;gt;BUG #3692: Conflicting create table statements throw unexpected error&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add CREATE SCHEMA ... LIKE that copies a schema}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Add CREATE TABLE LIKE ... INCLUDING COMMENTS}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Have CREATE TABLE LIKE copy column storage parameters&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-07/msg01417.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-08/msg00423.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-09/msg00576.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-09/msg00824.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|CREATE OR REPLACE FUNCTION might leave dependent objects depending on the function in inconsistent state&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-general/2008-08/msg00985.php indexes on functions and create or replace function]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow GLOBAL temporary tables to exist as empty by default in all sessions&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00006.php &amp;lt;nowiki&amp;gt;what is difference between LOCAL and GLOBAL TEMP TABLES in PostgreSQL&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-04/msg01329.php&lt;br /&gt;
* http://archives.postgresql.org//pgsql-hackers/2009-05/msg00016.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add OR REPLACE to CREATE LANGUAGE&lt;br /&gt;
* http://archives.postgresql.org/pgsql-patches/2008-05/msg00057.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow the creation of &amp;quot;distinct&amp;quot; types&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-10/msg01647.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== UPDATE ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|&amp;lt;nowiki&amp;gt;Allow UPDATE tab SET ROW (col, ...) = (SELECT...)&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-07/msg01308.php &amp;lt;nowiki&amp;gt;Re: [PATCHES] extension for sql update&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg00865.php &amp;lt;nowiki&amp;gt;UPDATE using sub selects&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2007-04/msg00315.php &amp;lt;nowiki&amp;gt;UPDATE using sub selects&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2008-03/msg00237.php &amp;lt;nowiki&amp;gt;Re: UPDATE using sub selects&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Research self-referential UPDATEs that see inconsistent row versions in read-committed mode&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-05/msg00507.php &amp;lt;nowiki&amp;gt;Concurrently updating an updatable view&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-06/msg00016.php &amp;lt;nowiki&amp;gt;Re: Do we need a TODO? (was Re: Concurrently updating anupdatable view)&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve performance of EvalPlanQual mechanism that rechecks already-updated rows&lt;br /&gt;
|This is related to the previous item, which questions whether it even has the right semantics&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-bugs/2008-09/msg00045.php &amp;lt;nowiki&amp;gt;BUG #4401: concurrent updates to a table blocks one update indefinitely&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-bugs/2009-07/msg00302.php &amp;lt;nowiki&amp;gt;BUG #4945: Parallel update(s) gone wild&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== ALTER ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Have ALTER TABLE RENAME rename SERIAL sequence names&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php &amp;lt;nowiki&amp;gt;Re: newbie: renaming sequences task&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemEasy&lt;br /&gt;
|Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php &amp;lt;nowiki&amp;gt;ALTER CONSTRAINT RENAME patch reverted&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add ALTER TABLE RENAME CONSTRAINT}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Have ALTER SEQUENCE RENAME rename the sequence name stored in the sequence table&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-bugs/2007-09/msg00092.php &amp;lt;nowiki&amp;gt;BUG #3619: Renaming sequence does not update its &#039;sequence_name&#039; field&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-bugs/2007-10/msg00007.php &amp;lt;nowiki&amp;gt;Re: BUG #3619: Renaming sequence does not update its &#039;sequence_name&#039; field&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00008.php &amp;lt;nowiki&amp;gt;Re: newbie: renaming sequences task&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add ALTER DOMAIN to modify the underlying data type}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemEasy&lt;br /&gt;
|Allow ALTER TABLE to change constraint deferrability and actions}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add missing object types for ALTER ... SET SCHEMA}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow ALTER TABLESPACE to move to different directories}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow moving system tables to other tablespaces, where possible&lt;br /&gt;
|Currently non-global system tables must be in the default database tablespace. Global system tables can never be moved.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Have ALTER INDEX update the name of a constraint using that index}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow column display reordering by recording a display, storage, and permanent id for every column?&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php &amp;lt;nowiki&amp;gt;Re: column ordering, was Re: [PATCHES] Enums patch v2&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-11/msg01029.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow an existing index to be marked as a table&#039;s primary key&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg00500.php &amp;lt;nowiki&amp;gt;Setting a pre-existing index as a primary key&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow ALTER TYPE on composite types to perform operations similar to ALTER TABLE&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-12/msg00245.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Don&#039;t require table rewrite on ALTER TABLE ... ALTER COLUMN TYPE, when the old and new data types are binary compatible&lt;br /&gt;
* http://archives.postgresql.org/message-id/200903040137.n241bAUV035002@wwwmaster.postgresql.org&lt;br /&gt;
* http://archives.postgresql.org/pgsql-patches/2006-10/msg00154.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Reduce locking required for ALTER commands&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-08/msg00533.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-10/msg01083.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2010-01/msg02349.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== CLUSTER ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Automatically maintain clustering on a table&lt;br /&gt;
|This might require some background daemon to maintain clustering during periods of low usage. It might also require tables to be only partially filled for easier reorganization.  Another idea would be to create a merged heap/index data file so an index lookup would automatically access the heap data too.  A third idea would be to store heap rows in hashed groups, perhaps using a user-supplied hash function.&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-performance/2004-08/msg00350.php &amp;lt;nowiki&amp;gt;Equivalent praxis to CLUSTERED INDEX?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00155.php &amp;lt;nowiki&amp;gt;Re: Grouped Index Tuples&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* http://community.enterprisedb.com/git/&lt;br /&gt;
* http://archives.postgresql.org/pgsql-performance/2009-10/msg00346.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemEasy&lt;br /&gt;
|Add default clustering to system tables&lt;br /&gt;
|To do this, determine the ideal cluster index for each system table and set the cluster setting during initdb.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve CLUSTER performance by sorting to reduce random I/O&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-08/msg01371.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemEasy&lt;br /&gt;
|Make CLUSTER VERBOSE more verbose.&lt;br /&gt;
|It is also used by new VACUUM FULL VERBOSE.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== COPY ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow COPY to report error lines and continue&lt;br /&gt;
|This requires the use of a savepoint before each COPY line is processed, with ROLLBACK on COPY failure. &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-12/msg00572.php &amp;lt;nowiki&amp;gt;Re: VLDB Features&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow COPY on a newly-created table to skip WAL logging&lt;br /&gt;
|On crash recovery, the table involved in the COPY would be removed or have its heap and index files truncated.  One issue is that no other backend should be able to add to the table at the same time, which is something that is currently allowed.  This currently is done if the table is created inside the same transaction block as the COPY because no other backends can see the table.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow COPY FROM to create index entries in bulk&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00811.php &amp;lt;nowiki&amp;gt;Batch update of indexes on data loading&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow COPY in CSV mode to control whether a quoted zero-length string is treated as NULL&lt;br /&gt;
|Currently this is always treated as a zero-length string, which generates an error when loading into an integer column &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00905.php &amp;lt;nowiki&amp;gt;Re: [PATCHES] allow CSV quote in NULL&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve COPY performance&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00954.php &amp;lt;nowiki&amp;gt;Re: 8.3 / 8.2.6 restore comparison&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow COPY to report errors sooner&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg01169.php &amp;lt;nowiki&amp;gt;Timely reporting of COPY errors&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Improve bytea COPY format&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-05/msg00192.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow COPY to handle other number formats eg. the German notation. Best would be something like WITH DECIMAL &#039;,&#039;.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow a stalled COPY to exit if the backend is terminated&lt;br /&gt;
* http://archives.postgresql.org/pgsql-bugs/2009-04/msg00067.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== GRANT/REVOKE ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Allow GRANT/REVOKE permissions to be applied to all schema objects with one command&lt;br /&gt;
|The proposed syntax is: GRANT SELECT ON ALL TABLES IN public TO phpuser; GRANT SELECT ON NEW TABLES IN public TO phpuser;&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-06/msg01014.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Allow GRANT/REVOKE permissions to be inherited by objects based on schema permissions&lt;br /&gt;
* http://wiki.postgresql.org/wiki/DefaultACL&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow SERIAL sequences to inherit permissions from the base table?}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow dropping of a role that has connection rights&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-05/msg00736.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== DECLARE CURSOR ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Prevent DROP TABLE from dropping a table referenced by its own open cursor?}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Provide some guarantees about the behavior of cursors that invoke volatile functions&lt;br /&gt;
* [http://archives.postgresql.org/message-id/20997.1244563664@sss.pgh.pa.us Re: Cursor with hold emits the same row more than once across commits in 8.3.7]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== INSERT ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow INSERT/UPDATE of the system-generated oid value for a row}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|In rules, allow VALUES() to contain a mixture of &#039;old&#039; and &#039;new&#039; references}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== SHOW/SET ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM ANALYZE, and CLUSTER}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Rationalize the discrepancy between settings that use values in bytes and SHOW that returns the object count&lt;br /&gt;
* http://archives.postgresql.org/pgsql-docs/2008-07/msg00007.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== LISTEN/NOTIFY ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Allow LISTEN/NOTIFY to store info in memory rather than tables&lt;br /&gt;
|Currently LISTEN/NOTIFY information is stored in pg_listener.  Storing such information in memory would improve performance.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Add optional textual message to NOTIFY&lt;br /&gt;
|This would allow an informational message to be added to the notify message, perhaps indicating the row modified or other custom information.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow NOTIFY in rules involving conditionals}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== Window Functions ===&lt;br /&gt;
See {{messageLink|357.1230492361@sss.pgh.pa.us|TODO items for window functions}}.&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Support creation of user-defined window functions.&lt;br /&gt;
|We have the ability to create new window functions written in C.  Is it&lt;br /&gt;
worth the effort to create an API that would let them be written in PL/pgsql, etc?}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Implement full support for window framing clauses.&lt;br /&gt;
|In addition to done clauses described in the [http://developer.postgresql.org/pgdocs/postgres/sql-expressions.html#SYNTAX-WINDOW-FUNCTIONS latest doc], these clauses are not implemented yet.&lt;br /&gt;
* RANGE BETWEEN ... PRECEDING/FOLLOWING&lt;br /&gt;
* EXCLUDE&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Look at tuplestore performance issues.&lt;br /&gt;
|The tuplestore_in_memory() thing is just a band-aid, we ought to try to solve it properly.  tuplestore_advance seems like a weak spot as well.&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-12/msg00152.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem|Do we really need so much duplicated code between Agg and WindowAgg?}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Teach planner to evaluate multiple windows in the optimal order.&lt;br /&gt;
|Currently windows are always evaluated in the query-specified order.&lt;br /&gt;
* http://archives.postgresql.org/message-id/3CDAD71E9D70417290FCF66F0178D1E1@amd64&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Implement DISTINCT clause in window aggregates.&lt;br /&gt;
|Some commercial DBs have implemented it already, thus it helps porting from those.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Integrity Constraints ==&lt;br /&gt;
=== Keys ===&lt;br /&gt;
&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Allow DEFERRABLE UNIQUE constraints&lt;br /&gt;
|&amp;lt;nowiki&amp;gt;This would allow UPDATE tab SET col = col + 1 to work if col has a unique index.  Currently, uniqueness checks are done while the command is being executed, rather than at the end of the statement or transaction.&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
* http://people.planetpostgresql.org/greg/index.php?/archives/46-Updating-unique-columns.html&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-09/msg01458.php &amp;lt;nowiki&amp;gt;Re: Unique index: update error&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve deferrable unique constraints for cases with many conflicts&lt;br /&gt;
|The current implementation fires a trigger for each potentially conflicting row.  This might not scale well for an update that changes many key values at once.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== Referential Integrity ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add MATCH PARTIAL referential integrity}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Change foreign key constraint for array -&amp;amp;gt; element to mean element in array?}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix problem when cascading referential triggers make changes on cascaded tables, seeing the tables in an intermediate state&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php &amp;lt;nowiki&amp;gt;Re: [PATCHES] Work-in-progress referential action trigger timing&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Optimize referential integrity checks&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-performance/2005-10/msg00458.php &amp;lt;nowiki&amp;gt;Re: Effects of cascading references in foreign keys&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-04/msg00744.php &amp;lt;nowiki&amp;gt;Can&#039;t ri_KeysEqual() consider two nulls as equal?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Server-Side Languages ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add support for polymorphic arguments and return types to languages other than PL/PgSQL}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add capability to create and call PROCEDURES}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add support for OUT and INOUT parameters to languages other than PL/PgSQL}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add more fine-grained specification of functions taking arbitrary data types&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-09/msg00367.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=== PL/pgSQL ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Allow function parameters to be passed by name, get_employee_salary(12345 AS emp_id, 2001 AS tax_year)&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-08/msg00559.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-12/msg00880.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow handling of %TYPE arrays, e.g. tab.col%TYPE[]}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|&amp;lt;nowiki&amp;gt;Allow listing of record column names, and access to record columns via variables, e.g. columns := r.(*), tval2 := r.(colname)&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php &amp;lt;nowiki&amp;gt;Re: PL/PGSQL: Dynamic Record Introspection&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2006-05/msg00302.php &amp;lt;nowiki&amp;gt;Re: PL/PGSQL: Dynamic Record Introspection&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2006-06/msg00031.php &amp;lt;nowiki&amp;gt;Re: PL/PGSQL: Dynamic Record Introspection&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add support for SCROLL cursors}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add support for WITH HOLD cursors}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow row and record variables to be set to NULL constants, and allow NULL tests on such variables&lt;br /&gt;
|Because a row is not scalar, do not allow assignment from NULL-valued scalars.&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-10/msg00070.php &amp;lt;nowiki&amp;gt;NULL and plpgsql rows&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Review handling of MOVE and FETCH&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2007-04/msg00527.php &amp;lt;nowiki&amp;gt;Re: actualised forgotten Magnus&#039;s patch for plpgsql MOVE	statement&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Improve logic of determining if an identifier is a variable or a column name&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00436.php &amp;lt;nowiki&amp;gt;Re: plpgsql and qualified variable names&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* * http://archives.postgresql.org/message-id/603c8f070903061741l1f11ba59q783745cc3cb79dba@mail.gmail.com&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider keeping separate cached copies when search_path changes&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg01009.php &amp;lt;nowiki&amp;gt;pl/pgsql Plan Invalidation and search_path&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Improve PL/pgSQL&#039;s ability to cope with rowtypes containing dropped columns&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-bugs/2008-09/msg00004.php &amp;lt;nowiki&amp;gt;Bug in RETURN QUERY&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve handling of NULL row values vs. NULL rows&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-09/msg01758.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== PL/Perl ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow data to be passed in native language formats, rather than only text&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-05/msg00289.php &amp;lt;nowiki&amp;gt;plperl vs. bytea&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow regex operations in plperl using UTF8 characters in non-UTF8 encoded databases.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== PL/Python ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add table function support}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add tracebacks&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2006-02/msg00288.php &amp;lt;nowiki&amp;gt;Re: plpython tracebacks&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Add support for Python 3&lt;br /&gt;
* [http://archives.postgresql.org/message-id/3544.1238817272@sss.pgh.pa.us &amp;lt;nowiki&amp;gt;Re: Python 3.0 does not work with PL/Python&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-07/msg01519.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Develop a trusted variant of PL/Python.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow arrays as function arguments and return values.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Create a new restricted execution class that will allow passing function arguments in as locals.  Passing them as globals means functions cannot be called recursively.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Functions cache the input and output functions for their arguments, so the following will make PostgreSQL unhappy:&lt;br /&gt;
&lt;br /&gt;
 create table users (first_name text, last_name text);&lt;br /&gt;
 create function user_name(user) returns text as &#039;mycode&#039; language plpython;&lt;br /&gt;
 select user_name(user) from users;&lt;br /&gt;
 alter table add column user_id integer;&lt;br /&gt;
 select user_name(user) from users;&lt;br /&gt;
&lt;br /&gt;
You have to drop and create the function(s) each time its arguments&lt;br /&gt;
are modified (not nice), or don&#039;t cache the input and output functions&lt;br /&gt;
(slower?), or check if the structure of the argument has been&lt;br /&gt;
altered (is this possible, easy, quick?) and recreate cache.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Better documentation}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add a DB-API compliant interface on top of the SPI interface.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|check encoding validity of values passed back to Postgres in function returns, trigger tuple changes, or SPI calls.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== PL/Tcl ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add table function support}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|check encoding validity of values passed back to Postgres in function returns, trigger tuple changes, or SPI calls.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Clients ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add a function like pg_get_indexdef() that report more detailed index information&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-bugs/2007-12/msg00166.php &amp;lt;nowiki&amp;gt;BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=== pg_ctl ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow pg_ctl to work properly with configuration files located outside the PGDATA directory&lt;br /&gt;
|pg_ctl can not read the pid file because it isn&#039;t located in the config directory but in the PGDATA directory.  The solution is to allow pg_ctl to read and understand postgresql.conf to find the data_directory value.&lt;br /&gt;
* http://archives.postgresql.org/pgsql-bugs/2009-10/msg00024.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Have the postmaster write a random number to a file on startup that pg_ctl checks against the contents of a pg_ping response on its initial connection (without login)&lt;br /&gt;
|This will protect against connecting to an old instance of the postmaster in a different or deleted subdirectory.&lt;br /&gt;
* http://archives.postgresql.org/pgsql-bugs/2009-10/msg00110.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-bugs/2009-10/msg00156.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Modify pg_ctl behavior and exit codes to make it easier to write an LSB conforming init script&lt;br /&gt;
|It may be desirable to condition some of the changes on a command-line switch, to avoid breaking existing scripts.  A Linux shell (sh) script is referenced which has been tested and seems to provide a high degree of conformance in multiple environments.  Study of this script might suggest areas where pg_ctl could be modified to make writing an LSB conforming script easier; however, some aspects of that script would be unnecessary with other suggested changes to pg_ctl, and discussion on the lists did not reach consensus on support for all aspects of this script.  Further discussion of particular changes is needed before beginning any work.&lt;br /&gt;
* [[Lsb_conforming_init_script|LSB conforming init script]]&lt;br /&gt;
These threads should be studied for other ideas on improvements:&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-08/msg01390.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-08/msg01843.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-09/msg00008.php&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== psql ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Have psql \ds show all sequences and their settings&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-07/msg00916.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-12/msg00401.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Have \d on a sequence indicate if the sequences is owned by a table}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Move psql backslash database information into the backend, use mnemonic commands?&lt;br /&gt;
|This would allow non-psql clients to pull the same information out of the database as psql. &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2004-01/msg00191.php &amp;lt;nowiki&amp;gt;Re: psql \d option list overloaded&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Make psql&#039;s \d commands more consistent in its handling of schemas&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php &amp;lt;nowiki&amp;gt;Re: psql and schemas&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consistently display privilege information for all objects in psql}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add auto-expanded mode so expanded output is used if the row length is wider than the screen width.&lt;br /&gt;
|Consider using auto-expanded mode for backslash commands like \df+.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Prevent tab completion of SET TRANSACTION from querying the database and therefore preventing the transaction isolation level from being set.&lt;br /&gt;
|Currently SET &amp;amp;lt;tab&amp;amp;gt; causes a database lookup to check all supported session variables.  This query causes problems because setting the transaction isolation level must be the first statement of a transaction.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add a \set variable to control whether \s displays line numbers&lt;br /&gt;
|Another option is to add \# which lists line numbers, and allows command execution.&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php &amp;lt;nowiki&amp;gt;Re: psql possible TODO&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Prevent escape string warnings when object names have backslashes&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00227.php &amp;lt;nowiki&amp;gt;Psql command-line completion bug&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Have \d show child tables that inherit from the specified parent}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Include the symbolic SQLSTATE name in verbose error reports&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-general/2007-09/msg00438.php &amp;lt;nowiki&amp;gt;Re: Checking is TSearch2 query is valid&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add prompt escape to display the client and server versions&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2009-05/msg00310.php &amp;lt;nowiki&amp;gt;WIP patch for TODO Item: Add prompt escape to display the client and server versions&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add option to wrap column values at whitespace boundaries, rather than chopping them at a fixed width.&lt;br /&gt;
|Currently, &amp;amp;quot;wrapped&amp;amp;quot; format chops values into fixed widths.  Perhaps the word wrapping could use the same algorithm documented in the W3C specification. &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00404.php &amp;lt;nowiki&amp;gt;Re: psql wrapped format default for backslash-d commands&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* http://www.w3.org/TR/CSS21/tables.html#auto-table-layout}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add &amp;amp;quot;auto&amp;amp;quot; expanded mode that outputs in expanded format if &amp;amp;quot;wrapped&amp;amp;quot; mode can&#039;t wrap the output to the screen width&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00417.php &amp;lt;nowiki&amp;gt;Re: psql wrapped format default for backslash-d commands&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Support the ReST table output format&lt;br /&gt;
|Details about the ReST format:  http://docutils.sourceforge.net/rst.html#reference-documentation&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-08/msg01007.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-01/msg00518.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-01/msg00609.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add option to print advice for people familiar with other databases&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2010-01/msg01845.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider showing TOAST and index sizes in \dt+&lt;br /&gt;
* http://archives.postgresql.org/pgsql-general/2010-01/msg00912.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow \dd to show constraint comments&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-09/msg00436.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-general/2009-09/msg00199.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add ability to edit views with \ev&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-09/msg00023.php&lt;br /&gt;
}}&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add \dL to show languages&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-07/msg00915.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== pg_dump / pg_restore ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Add dumping of comments on composite type columns&lt;br /&gt;
* {{MessageLink|20090723225940.E35D975331E@cvs.postgresql.org|Teach pg_dump to dump comments attached to the columns of a composite type.}}&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemEasy&lt;br /&gt;
|&amp;lt;nowiki&amp;gt;Add full object name to the tag field.  eg. for operators we need &#039;=(integer, integer)&#039;, instead of just &#039;=&#039;.&amp;lt;/nowiki&amp;gt;}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemEasyDone&lt;br /&gt;
| Add comments to output indicating version of pg_dump and of the database server&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add pg_dumpall custom format dumps?}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Avoid using platform-dependent locale names in pg_dumpall output&lt;br /&gt;
|Using native locale names puts roadblocks in the way of porting a dump to another platform.  One possible solution is to get&lt;br /&gt;
CREATE DATABASE to accept some agreed-on set of locale names and fix them up to meet the platform&#039;s requirements.&lt;br /&gt;
* http://archives.postgresql.org/message-id/21396.1241716688@sss.pgh.pa.us&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow selection of individual object(s) of all types, not just tables}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|In a selective dump, allow dumping of an object and all its dependencies}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add options like pg_restore -l and -L to pg_dump}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add support for multiple pg_restore -t options, like pg_dump&lt;br /&gt;
|pg_restore&#039;s -t switch is less useful than pg_dump&#039;s in quite a few ways: no multiple switches, no pattern matching, no ability to pick up indexes and other dependent items for a selected table.  It should be made to handle this switch just like pg_dump does.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Stop dumping CASCADE on DROP TYPE commands in clean mode}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow pg_dump --clean to drop roles that own objects or have privileges&lt;br /&gt;
|tgl says: if this is about pg_dumpall, it&#039;s done as of 8.4.  If it&#039;s really about pg_dump, what does it mean?  pg_dump has no business dropping roles.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Change pg_dump so that a comment on the dumped database is applied to the loaded database, even if the database has a different name.  This will require new backend syntax, perhaps COMMENT ON CURRENT DATABASE.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Remove unnecessary function pointer abstractions in pg_dump source code}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow pg_dump to utilize multiple CPUs and I/O channels by dumping multiple objects simultaneously&lt;br /&gt;
|The difficulty with this is getting multiple dump processes to produce a single dump output file.  It also would require several sessions to share the same snapshot. &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php &amp;lt;nowiki&amp;gt;pg_dump additional options for performance&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow pg_restore to load different parts of the COPY data for a single table simultaneously}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Remove support for dumping from pre-7.3 servers&lt;br /&gt;
|In 7.3 and later, we can get accurate dependency information from the server.  pg_dump still contains a lot of crufty code&lt;br /&gt;
to try to deal with the lack of dependency info in older servers, but the usefulness of maintaining that code grows small.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow pre/data/post files when schema and data are dumped separately, for performance reasons&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php &amp;lt;nowiki&amp;gt;pg_dump additional options for performance&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* http://archives.postgresql.org/pgsql-patches/2008-07/msg00185.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Have pg_dump -C emit ALTER DATABASE ... SET commands after database creation&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-06/msg01031.php &amp;lt;nowiki&amp;gt;ALTER DATABASE vs pg_dump&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow parallel restore of tar dumps&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-02/msg01154.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== ecpg ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Docs&lt;br /&gt;
|Document differences between ecpg and the SQL standard and information about the Informix-compatibility module.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Solve cardinality &amp;amp;gt; 1 for input descriptors / variables?}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add a semantic check level, e.g. check if a table really exists}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|fix handling of DB attributes that are arrays}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Implement SQLDA&lt;br /&gt;
|{{MessageLink|20100105163823.7C70B753FB7@cvs.postgresql.org|add sqlda support to ecpg in both native and compatibility mode}}&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix nested C comments}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemEasy&lt;br /&gt;
|sqlwarn[6] should be &#039;W&#039; if the PRECISION or SCALE value specified}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Make SET CONNECTION thread-aware, non-standard?}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow multidimensional arrays}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Implement COPY FROM STDIN}} &lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Provide a way to specify size of a bytea parameter&lt;br /&gt;
* [http://archives.postgresql.org/message-id/200906192131.n5JLVoMo044178@wwwmaster.postgresql.org &amp;lt;nowiki&amp;gt;BUG #4866: ECPG and BYTEA&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix small memory leaks in ecpg&lt;br /&gt;
|Memory leaks in a short running application like ecpg are not really a problem, but make debugging more complicated}} &lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== libpq ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add PQescapeIdentifierConn()}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Prevent PQfnumber() from lowercasing unquoted column names&lt;br /&gt;
|PQfnumber() should never have been doing lowercasing, but historically it has so we need a way to prevent it}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow statement results to be automatically batched to the client&lt;br /&gt;
|Currently all statement results are transferred to the libpq client before libpq makes the results available to the application.  This feature would allow the application to make use of the first result rows while the rest are transferred, or held on the server waiting for them to be requested by libpq. One complexity is that a statement like SELECT 1/col could error out mid-way through the result set.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider disallowing multiple queries in PQexec() as an additional barrier to SQL injection attacks&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-01/msg00184.php &amp;lt;nowiki&amp;gt;Re: InitPostgres and flatfiles question&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add PQexecf() that allows complex parameter substitution&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg01803.php &amp;lt;nowiki&amp;gt;Last minute mini-proposal (I know, know) for PQexecf()&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add SQLSTATE and severity to errors generated within libpq itself&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-interfaces/2007-11/msg00015.php &amp;lt;nowiki&amp;gt;v8.1: Error severity on libpq PGconn*&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add code to detect client encoding and locale from the operating system environment&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-06/msg01040.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add keepalive support to libpq&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2010-02/msg00611.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add support for interface/ipaddress binding to libpq&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2010-02/msg01811.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Triggers ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve storage of deferred trigger queue&lt;br /&gt;
|Right now all deferred trigger information is stored in backend memory.  This could exhaust memory for very large trigger queues. This item involves dumping large queues into files, or doing some kind of join to process all the triggers, some bulk operation, or a bitmap. &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00876.php &amp;lt;nowiki&amp;gt;Re: BUG #4204: COPY to table with FK has memory leak&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-10/msg00464.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow triggers to be disabled in only the current session.&lt;br /&gt;
|This is currently possible by starting a multi-statement transaction, modifying the system tables, performing the desired SQL, restoring the system tables, and committing the transaction.  ALTER TABLE ... TRIGGER requires a table lock so it is not ideal for this usage.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|With disabled triggers, allow pg_dump to use ALTER TABLE ADD FOREIGN KEY&lt;br /&gt;
|If the dump is known to be valid, allow foreign keys to be added without revalidating the data.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow statement-level triggers to access modified rows}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|When statement-level triggers are defined on a parent table, have them fire only on the parent table, and fire child table triggers only where appropriate&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-11/msg01883.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Support triggers on columns&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php &amp;lt;nowiki&amp;gt;Column-level triggers&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow AFTER triggers on system tables&lt;br /&gt;
|System tables are modified in many places in the backend without going through the executor and therefore not causing triggers to fire. To complete this item, the functions that modify system tables will have to fire triggers.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Tighten trigger permission checks&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php &amp;lt;nowiki&amp;gt;Security leak with trigger functions?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow BEFORE INSERT triggers on views&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-general/2007-02/msg01466.php &amp;lt;nowiki&amp;gt;Re: Why can&#039;t I put a BEFORE EACH ROW trigger on a view?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add database and transaction-level triggers&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00451.php &amp;lt;nowiki&amp;gt;Proposal for db level triggers&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00620.php &amp;lt;nowiki&amp;gt;triggers on prepare, commit, rollback... ?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Reduce locking requirements for creating a trigger&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-06/msg00635.php &amp;lt;nowiki&amp;gt;Re: Change lock requirements for adding a trigger&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Inheritance ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow inherited tables to inherit indexes, UNIQUE constraints, and primary/foreign keys}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Honor UNIQUE INDEX on base column in INSERTs/UPDATEs on inherited table, e.g.  INSERT INTO inherit_table (unique_index_col) VALUES (dup) should fail&lt;br /&gt;
|The main difficulty with this item is the problem of creating an index that can span multiple tables.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Determine whether ALTER TABLE / SET SCHEMA should work on inheritance hierarchies (and thus support ONLY).  If yes, implement it.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|ALTER TABLE variants sometimes support recursion and sometimes not, but this is poorly/not documented, and the ONLY marker would then be silently ignored. Clarify the documentation, and reject ONLY if it is not supported.}}&lt;br /&gt;
&lt;br /&gt;
== Indexes ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add UNIQUE capability to non-btree indexes}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Prevent index uniqueness checks when UPDATE does not modify the column&lt;br /&gt;
|Uniqueness (index) checks are done when updating a column even if the column is not modified by the UPDATE.&lt;br /&gt;
However, HOT already short-circuits this in common cases, so more work might not be helpful.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow the creation of on-disk bitmap indexes which can be quickly combined with other bitmap indexes&lt;br /&gt;
|Such indexes could be more compact if there are only a few distinct values. Such indexes can also be compressed.  Keeping such indexes updated can be costly.&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php &amp;lt;nowiki&amp;gt;Re: Bitmap index AM&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg01107.php &amp;lt;nowiki&amp;gt;Bitmap index thoughts&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg00265.php &amp;lt;nowiki&amp;gt;Stream bitmaps&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg01214.php &amp;lt;nowiki&amp;gt;Re: Bitmapscan changes - Requesting further feedback&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2007-05/msg00013.php &amp;lt;nowiki&amp;gt;Updated bitmap index patch&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00741.php &amp;lt;nowiki&amp;gt;Reviewing new index types (was Re: [PATCHES] Updated bitmap indexpatch)&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-10/msg01023.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow accurate statistics to be collected on indexes with more than one column or expression indexes, perhaps using per-index statistics&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-performance/2006-10/msg00222.php &amp;lt;nowiki&amp;gt;Re: Simple join optimized badly?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg01131.php &amp;lt;nowiki&amp;gt;Stats for multi-column indexes&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-10/msg00741.php &amp;lt;nowiki&amp;gt;Cross-column statistics revisited&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2009-06/msg01431.php &amp;lt;nowiki&amp;gt;Multi-Dimensional Histograms&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider having a larger statistics target for indexed columns and expression indexes. &lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider smaller indexes that record a range of values per heap page, rather than having one index entry for every heap row&lt;br /&gt;
|This is useful if the heap is clustered by the indexed values. &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00341.php &amp;lt;nowiki&amp;gt;Grouped Index Tuples&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php &amp;lt;nowiki&amp;gt;Grouped Index Tuples&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php &amp;lt;nowiki&amp;gt;Grouped Index Tuples / Clustered Indexes&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2007-03/msg00163.php &amp;lt;nowiki&amp;gt;Bitmapscan changes&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-08/msg00014.php &amp;lt;nowiki&amp;gt;Re: GIT patch&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-08/msg00487.php &amp;lt;nowiki&amp;gt;Re: Index Tuple Compression Approach?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg01589.php &amp;lt;nowiki&amp;gt;Re: Index AM change proposals, redux&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY&lt;br /&gt;
|This is difficult because you must upgrade to an exclusive table lock to replace the existing index file.  CREATE INDEX CONCURRENTLY does not have this complication.  This would allow index compaction without downtime. &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-performance/2007-08/msg00289.php &amp;lt;nowiki&amp;gt;Re: When/if to Reindex&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow multiple indexes to be created concurrently, ideally via a single heap scan&lt;br /&gt;
|pg_restore allows parallel index builds, but it is done via subprocesses, and there is no SQL interface for this.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider sorting entries before inserting into btree index&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-general/2008-01/msg01010.php &amp;lt;nowiki&amp;gt;Re: ATTN: Clodaldo was Performance problem. Could it be related to 8.3-beta4?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow index scans to return matching index keys, not just the matching heap locations&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg01657.php &amp;lt;nowiki&amp;gt;Re: Is this TODO item done?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-08/msg01477.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow creation of an index that can do comparisons to test if a value is between two column values&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-05/msg00757.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider using &amp;quot;effective_io_concurrency&amp;quot; for index scans&lt;br /&gt;
* Currently only bitmap scans use this, which might be fine because most multi-row index scans use bitmap scans.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=== GIST ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add more GIST index support for geometric data types}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow GIST indexes to create certain complex index types, like digital trees (see Aoki)}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix performance issues in contrib/seg and contrib/cube GiST support&lt;br /&gt;
* [http://archives.postgresql.org/message-id/alpine.DEB.2.00.0904161633160.4053@aragorn.flymine.org GiST index performance]&lt;br /&gt;
* [http://archives.postgresql.org/message-id/alpine.DEB.2.00.0904221704470.22330@aragorn.flymine.org draft patch]&lt;br /&gt;
* http://archives.postgresql.org/pgsql-performance/2009-05/msg00069.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-performance/2009-06/msg00068.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== GIN ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Support empty indexed values (such as zero-element arrays) properly&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg00237.php contrib/intarray vs empty arrays]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-bugs/2009-05/msg00118.php BUG #4806: Bug with GiST index and empty integer array]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Behave correctly for cases where some elements of an indexed value are NULL&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-03/msg01003.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Support queries that require a full scan&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-general/2009-05/msg00402.php Issue report]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-general/2007-06/msg01132.php Older issue report]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-01/msg01581.php Original discussion of issue and proposed resolution]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== Hash ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Pack hash index buckets onto disk pages more efficiently&lt;br /&gt;
|Currently only one hash bucket can be stored on a page. Ideally several hash buckets could be stored on a single page and greater granularity used for the hash algorithm.&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2004-06/msg00168.php &amp;lt;nowiki&amp;gt;Why hash indexes suck&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
However, the binary searching within a hash page probably renders this issue moot.&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-committers/2008-09/msg00154.php &amp;lt;nowiki&amp;gt;pgsql: Change hash indexes to store only the hash code rather than the&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add hash WAL logging for crash recovery}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow multi-column hash indexes}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Catalogs ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Improve performance of information_schema views&lt;br /&gt;
* [http://archives.postgresql.org/message-id/29921.1230246746%40sss.pgh.pa.us table_privileges is way too slow]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Improve information_schema&#039;s entries for precision and scale&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-05/msg01485.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Sorting ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider whether duplicate keys should be sorted by block/offset&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00558.php &amp;lt;nowiki&amp;gt;Remove hacks for old bad qsort() implementations?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider being smarter about memory and external files used during sorts&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg01101.php &amp;lt;nowiki&amp;gt;Sorting Improvements for 8.4&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-12/msg00045.php &amp;lt;nowiki&amp;gt;Re: Sorting Improvements for 8.4&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider detoasting keys before sorting}}&lt;br /&gt;
&lt;br /&gt;
== Fsync ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options&lt;br /&gt;
|Ideally this requires a separate test program that can be run at initdb time or optionally later.  Consider O_SYNC when O_DIRECT exists.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add program to test if fsync has a delay compared to non-fsync}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider sorting writes during checkpoint&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-06/msg00541.php &amp;lt;nowiki&amp;gt;Sorted writes in checkpoint&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* http://archives.postgresql.org/pgsql-patches/2008-07/msg00050.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Cache Usage ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Speed up COUNT(*)&lt;br /&gt;
|We could use a fixed row count and a +/- count to follow MVCC visibility rules, or a single cached value could be used and invalidated if anyone modifies the table.  Another idea is to get a count directly from a unique index, but for this to be faster than a sequential scan it must avoid access to the heap to obtain tuple visibility information.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Provide a way to calculate an &amp;amp;quot;estimated COUNT(*)&amp;amp;quot;&lt;br /&gt;
|Perhaps by using the optimizer&#039;s cardinality estimates or random sampling.&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php &amp;lt;nowiki&amp;gt;Re: Improving count(*)&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow data to be pulled directly from indexes&lt;br /&gt;
|Currently indexes do not have enough tuple visibility information to allow data to be pulled from the index without also accessing the heap.  One way to allow this is to set a bit on index tuples to indicate if a tuple is currently visible to all transactions when the first valid heap lookup happens.  This bit would have to be cleared when a heap tuple is expired.&lt;br /&gt;
Another idea is to maintain a bitmap of heap pages where all rows are visible to all backends, and allow index lookups to reference that bitmap to avoid heap lookups, perhaps the same bitmap we might add someday to determine which heap pages need vacuuming.  Frequently accessed bitmaps would have to be stored in shared memory.  One 8k page of bitmaps could track 512MB of heap pages.&lt;br /&gt;
A third idea would be for a heap scan to check if all rows are visible and if so set a per-table flag which can be checked by index scans.  Any change to the table would have to clear the flag.  To detect changes during the heap scan a counter could be set at the start and checked at the end --- if it is the same, the table has not been modified --- any table change would increment the counter.&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2007-10/msg00166.php &amp;lt;nowiki&amp;gt;Re: [HACKERS] Including Snapshot Info with Indexes&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2008-01/msg00049.php &amp;lt;nowiki&amp;gt;Re: [HACKERS] Including Snapshot Info with Indexes&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-06/msg01094.php &amp;lt;nowiki&amp;gt;TODO item: Allow data to be pulled directly from indexes&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-09/msg00003.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider automatic caching of statements at various levels:&lt;br /&gt;
* Parsed query tree&lt;br /&gt;
* Query execute plan&lt;br /&gt;
* Query results &lt;br /&gt;
&lt;br /&gt;
:&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg00823.php &amp;lt;nowiki&amp;gt;Cached Query Plans (was: global prepared statements)&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider increasing internal areas (NUM_CLOG_BUFFERS) when shared buffers is increased&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php &amp;lt;nowiki&amp;gt;Re: slru.c race condition (was Re: TRAP: FailedAssertion(&amp;amp;quot;!((itemid)-&amp;amp;gt;lp_flags &amp;amp;amp; 0x01)&amp;amp;quot;,)&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-08/msg00030.php &amp;lt;nowiki&amp;gt;clog_buffers to 64 in 8.3?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-performance/2007-08/msg00024.php &amp;lt;nowiki&amp;gt;CLOG Patch&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider decreasing the amount of memory used by PrivateRefCount&lt;br /&gt;
|&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-11/msg00797.php &amp;lt;nowiki&amp;gt;PrivateRefCount (for 8.3)&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php &amp;lt;nowiki&amp;gt;Re: PrivateRefCount (for 8.3)&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider allowing higher priority queries to have referenced buffer cache pages stay in memory longer&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg00562.php &amp;lt;nowiki&amp;gt;Re: How to keep a table in memory?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Vacuum ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Improve VACUUM FULL&#039;s speed when major data movement is needed&lt;br /&gt;
|For large table adjustments during VACUUM FULL, it would be faster to cluster or reindex rather than update the indexes piecemeal as it does now.  Also, this behavior tends to bloat the indexes.&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg00024.php &amp;lt;nowiki&amp;gt;Revitalising VACUUM FULL for 8.3&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-performance/2007-05/msg00296.php &amp;lt;nowiki&amp;gt;Re: [doc patch] a slight VACUUM / VACUUM FULL doc improvement proposal&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-08/msg00307.php &amp;lt;nowiki&amp;gt;Re: Unexpected VACUUM FULL failure&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-06/msg00656.php A note about VACUUM syntax]&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-09/msg01045.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Clean up VACUUM FULL&#039;s klugy transaction management&lt;br /&gt;
|VACUUM FULL marks its transaction committed before it&#039;s really done, which means a PANIC if it fails after that point.  This needs to be&lt;br /&gt;
split into two transactions.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Auto-fill the free space map by scanning the buffer cache or by checking pages written by the background writer&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-02/msg01125.php &amp;lt;nowiki&amp;gt;Dead Space Map&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-03/msg00011.php &amp;lt;nowiki&amp;gt;Re: Automatic free space map filling&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider having single-page pruning update the visibility map&lt;br /&gt;
* &amp;lt;nowiki&amp;gt;https://commitfest.postgresql.org/action/patch_view?id=75&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2010-02/msg02344.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve tracking of total relation tuple counts now that vacuum doesn&#039;t always scan the whole heap&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2009-06/msg00531.php Partial vacuum versus pg_class.reltuples]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Bias FSM towards returning free space near the beginning of the heap file, in hopes that empty pages at the end can be truncated by VACUUM}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Make FSM return free space based on table clustering, to assist in maintaining clustering?}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider a more compact data representation for dead tuple locations within VACUUM&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2007-05/msg00143.php &amp;lt;nowiki&amp;gt;Re: Have vacuum emit a warning when it runs out of maintenance_work_mem&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Provide more information in order to improve user-side estimates of dead space bloat in relations&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-general/2009-05/msg01039.php &amp;lt;nowiki&amp;gt;Re: Bloated Table&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=== Auto-vacuum ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemEasy&lt;br /&gt;
|Issue log message to suggest VACUUM FULL if a table is nearly empty?}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Prevent long-lived temporary tables from causing frozen-xid advancement starvation&lt;br /&gt;
|The problem is that autovacuum cannot vacuum them to set frozen xids; only the session that created them can do that. &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-general/2007-06/msg01645.php &amp;lt;nowiki&amp;gt;Re: AutoVacuum Behaviour Question&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Prevent autovacuum from running if an old transaction is still running from the last vacuum&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg00899.php &amp;lt;nowiki&amp;gt;Re: Autovacuum and OldestXmin&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Have free space allocation bias away from using trailing table pages&lt;br /&gt;
|This improves the chances of truncating the table during vacuum&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-09/msg01124.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Locking ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix priority ordering of read and write light-weight locks&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2004-11/msg00893.php &amp;lt;nowiki&amp;gt;lwlocks and starvation&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2004-11/msg00905.php &amp;lt;nowiki&amp;gt;Re: lwlocks and starvation&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix problem when multiple subtransactions of the same outer transaction hold different types of locks, and one subtransaction aborts&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-11/msg01011.php &amp;lt;nowiki&amp;gt;FOR SHARE vs FOR UPDATE locks&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg00001.php &amp;lt;nowiki&amp;gt;Re: FOR SHARE vs FOR UPDATE locks&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-02/msg00435.php &amp;lt;nowiki&amp;gt;Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-05/msg00773.php &amp;lt;nowiki&amp;gt;Re: savepoints and upgrading locks&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow UPDATEs on only non-referential integrity columns not to conflict with referential integrity locks&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-02/msg00073.php &amp;lt;nowiki&amp;gt;Referential Integrity and SHARE locks&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add idle_in_transaction_timeout GUC so locks are not held for long periods of time}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve deadlock detection when a page cleaning lock conflicts with a shared buffer that is pinned&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-bugs/2008-01/msg00138.php &amp;lt;nowiki&amp;gt;BUG #3883: Autovacuum deadlock with truncate?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php &amp;lt;nowiki&amp;gt;Thoughts about bug #3883&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-committers/2008-01/msg00365.php &amp;lt;nowiki&amp;gt;Re: pgsql: Add checks to TRUNCATE, CLUSTER, and REINDEX to prevent&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Detect deadlocks involving LockBufferForCleanup()&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php &amp;lt;nowiki&amp;gt;Thoughts about bug #3883&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider a lock timeout parameter&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-05/msg00485.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider improving serialized transaction behavior to avoid anomalies&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-05/msg00217.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-05/msg01136.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-06/msg00035.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Startup Time Improvements ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Experiment with multi-threaded backend for backend creation&lt;br /&gt;
|This would prevent the overhead associated with process creation. Most operating systems have trivial process creation time compared to database startup overhead, but a few operating systems (Win32, Solaris) might benefit from threading.  Also explore the idea of a single session using multiple threads to execute a statement faster.}}&lt;br /&gt;
&lt;br /&gt;
== Write-Ahead Log ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Eliminate need to write full pages to WAL before page modification&lt;br /&gt;
|Currently, to protect against partial disk page writes, we write full page images to WAL before they are modified so we can correct any partial page writes during recovery.  These pages can also be eliminated from point-in-time archive files. &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2002-06/msg00655.php &amp;lt;nowiki&amp;gt;Re: Index Scans become Seq Scans after VACUUM ANALYSE&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|When full page writes are off, write CRC to WAL and check file system blocks on recovery&lt;br /&gt;
|If CRC check fails during recovery, remember the page in case a later CRC for that page properly matches.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Write full pages during file system write and not when the page is modified in the buffer cache&lt;br /&gt;
|This allows most full page writes to happen in the background writer.  It might cause problems for applying WAL on recovery into a partially-written page, but later the full page will be replaced from WAL.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Allow WAL traffic to be streamed to another server for stand-by replication}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Reduce WAL traffic so only modified values are written rather than entire rows&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-03/msg01589.php &amp;lt;nowiki&amp;gt;Reduction in WAL for UPDATEs&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow WAL information to recover corrupted pg_controldata&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php &amp;lt;nowiki&amp;gt;Re: [HACKERS] pg_resetxlog -r flag&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Find a way to reduce rotational delay when repeatedly writing last WAL page&lt;br /&gt;
|Currently fsync of WAL requires the disk platter to perform a full rotation to fsync again. One idea is to write the WAL to different offsets that might reduce the rotational delay. &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2002-11/msg00483.php &amp;lt;nowiki&amp;gt;500 tpsQL + WAL log implementation&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow WAL logging to be turned off for a table, but the table might be dropped or truncated during crash recovery&lt;br /&gt;
|Allow tables to bypass WAL writes and just fsync() dirty pages on commit.  This should be implemented using ALTER TABLE, e.g. &amp;lt;nowiki&amp;gt;ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | DEFAULT ]&amp;lt;/nowiki&amp;gt;.  Tables using non-default logging should not use referential integrity with default-logging tables.  A table without dirty buffers during a crash could perhaps avoid the drop/truncate. &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2005-12/msg01016.php &amp;lt;nowiki&amp;gt;Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow WAL logging to be turned off for a table, but the table would avoid being truncated/dropped&lt;br /&gt;
|To do this, only a single writer can modify the table, and writes must happen only on new pages so the new pages can be removed during crash recovery.  Readers can continue accessing the table.  Such tables probably cannot have indexes.  One complexity is the handling of indexes on TOAST tables. &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2005-12/msg01016.php &amp;lt;nowiki&amp;gt;Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Speed WAL recovery by allowing more than one page to be prefetched&lt;br /&gt;
|This should be done utilizing the same infrastructure used for prefetching in general to avoid introducing complex error-prone code in WAL replay. &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-general/2007-12/msg00683.php &amp;lt;nowiki&amp;gt;Slow PITR restore&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-12/msg00497.php &amp;lt;nowiki&amp;gt;Re: [GENERAL] Slow PITR restore&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg01279.php &amp;lt;nowiki&amp;gt;Read-ahead and parallelism in redo recovery&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve WAL concurrency by increasing lock granularity&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00556.php &amp;lt;nowiki&amp;gt;Reworking WAL locking&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Be more aggressive about creating WAL files&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-10/msg01325.php &amp;lt;nowiki&amp;gt;Re: PANIC caused by open_sync on Linux&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2004-07/msg01075.php &amp;lt;nowiki&amp;gt;PreallocXlogFiles&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2005-04/msg00556.php &amp;lt;nowiki&amp;gt;WAL/PITR additional items&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Have resource managers report the duration of their status changes&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-10/msg01468.php &amp;lt;nowiki&amp;gt;Recovery of Multi-stage WAL actions&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Move pgfoundry&#039;s xlogdump to /contrib and have it rely more closely on the WAL backend code&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg00035.php &amp;lt;nowiki&amp;gt;xlogdump&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Close deleted WAL files held open in *nix by long-lived read-only backends&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2009-11/msg01754.php &amp;lt;nowiki&amp;gt;Deleted WAL files held open by backends in Linux&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2009-12/msg00060.php &amp;lt;nowiki&amp;gt;Re: Deleted WAL files held open by backends in Linux&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Optimizer / Executor ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve selectivity functions for geometric operators}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Precompile SQL functions to avoid overhead}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Create utility to compute accurate random_page_cost value}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider increasing the default values of from_collapse_limit, join_collapse_limit, and/or geqo_threshold&lt;br /&gt;
* [http://archives.postgresql.org/message-id/4136ffa0905210551u22eeb31bn5655dbe7c9a3aed5@mail.gmail.com from_collapse_limit vs. geqo_threshold]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve ability to display optimizer analysis using OPTIMIZER_DEBUG}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Have EXPLAIN ANALYZE issue NOTICE messages when the estimated and actual row counts differ by a specified percentage}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Have EXPLAIN ANALYZE report rows as floating-point numbers&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-05/msg01363.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-06/msg00108.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Log statements where the optimizer row estimates were dramatically different from the number of rows actually found?}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve how ANALYZE computes in-doubt tuples&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-11/msg00771.php &amp;lt;nowiki&amp;gt;VACUUM/ANALYZE counting of in-doubt tuples&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider compressed annealing to search for query plans&lt;br /&gt;
|This might replace GEQO.&lt;br /&gt;
* http://archives.postgresql.org/message-id/15658.1241278636%40sss.pgh.pa.us&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider using a hash for joining to a large IN (VALUES ...) list&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-05/msg00450.php &amp;lt;nowiki&amp;gt;Planning large IN lists&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow single batch hash joins to preserve outer pathkeys&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-09/msg00806.php Re: Potential Join Performance Issue]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg00153.php a few crazy ideas about hash joins]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|&amp;quot;lazy&amp;quot; hash tables - look up only the tuples that are actually requested&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg00153.php a few crazy ideas about hash joins]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Avoid building the same hash table more than once during the same query&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg00153.php a few crazy ideas about hash joins]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Avoid hashing for distinct and then re-hashing for hash join&lt;br /&gt;
* [http://archives.postgresql.org/message-id/4136ffa0902191346g62081081v8607f0b92c206f0a@mail.gmail.com Re: Fixing Grittner&#039;s planner issues]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2009-04/msg00153.php a few crazy ideas about hash joins]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow hashing to be used on arrays, if the element type is hashable&lt;br /&gt;
* http://archives.postgresql.org/message-id/11087.1244905821@sss.pgh.pa.us&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve use of expression indexes for ORDER BY &lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-08/msg01553.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Background Writer ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider having the background writer update the transaction status hint bits before writing out the page&lt;br /&gt;
|Implementing this requires the background writer to have access to system catalogs and the transaction status log.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider adding buffers the background writer finds reusable to the free list &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php &amp;lt;nowiki&amp;gt;Background LRU Writer/free list&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Automatically tune bgwriter_delay based on activity rather then using a fixed interval&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php &amp;lt;nowiki&amp;gt;Background LRU Writer/free list&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider whether increasing BM_MAX_USAGE_COUNT improves performance&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-06/msg01007.php &amp;lt;nowiki&amp;gt;Bgwriter LRU cleaning: we&#039;ve been going at this all wrong&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Test to see if calling PreallocXlogFiles() from the background writer will help with WAL segment creation latency&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2007-06/msg00340.php &amp;lt;nowiki&amp;gt;Re: Load Distributed Checkpoints, final patch&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Concurrent Use of Resources ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Do async I/O for faster random read-ahead of data&lt;br /&gt;
|Async I/O allows multiple I/O requests to be sent to the disk with results coming back asynchronously.&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-10/msg00820.php &amp;lt;nowiki&amp;gt;Asynchronous I/O Support&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-performance/2007-09/msg00255.php &amp;lt;nowiki&amp;gt;Re: random_page_costs - are defaults of 4.0 realistic for SCSI RAID 1&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-12/msg00027.php &amp;lt;nowiki&amp;gt;There&#039;s random access and then there&#039;s random access&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2008-01/msg00170.php &amp;lt;nowiki&amp;gt;Bitmap index scan preread using posix_fadvise (Was: There&#039;s random access and then there&#039;s random access)&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
The above patch is already applied as of 8.4, but it still remains to figure out how to handle plain indexscans effectively.&lt;br /&gt;
* [http://archives.postgresql.org//pgsql-hackers/2009-01/msg00806.php Problems with the patch submitted for posix_fadvise in index scans]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Experiment with multi-threaded backend for better I/O utilization&lt;br /&gt;
|This would allow a single query to make use of multiple I/O channels simultaneously.  One idea is to create a background reader that can pre-fetch sequential and index scan pages needed by other backends. This could be expanded to allow concurrent reads from multiple devices in a partitioned table.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Experiment with multi-threaded backend for better CPU utilization&lt;br /&gt;
|This would allow several CPUs to be used for a single query, such as for sorting or query execution.&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-10/msg00945.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|SMP scalability improvements&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00439.php &amp;lt;nowiki&amp;gt;Straightforward changes for increased SMP scalability&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-09/msg00206.php &amp;lt;nowiki&amp;gt;Re: Reducing Transaction Start/End Contention&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00361.php &amp;lt;nowiki&amp;gt;Re: Reducing Transaction Start/End Contention&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== TOAST ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow user configuration of TOAST thresholds&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-02/msg00213.php &amp;lt;nowiki&amp;gt;Re: Proposed adjustments in MaxTupleSize and toastthresholds&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-08/msg00082.php &amp;lt;nowiki&amp;gt;pg_lzcompress strategy parameters&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Reduce unnecessary cases of deTOASTing&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-09/msg00895.php &amp;lt;nowiki&amp;gt;Re: [PATCHES] Eliminate more detoast copies for packed varlenas&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Reduce costs of repeat de-TOASTing of values&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-06/msg01096.php &amp;lt;nowiki&amp;gt;WIP patch: reducing overhead for repeat de-TOASTing&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Miscellaneous Performance ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Use mmap() rather than SYSV shared memory or to write WAL files?&lt;br /&gt;
|This would remove the requirement for SYSV SHM but would introduce portability issues. Anonymous mmap (or mmap to /dev/zero) is required to prevent I/O overhead.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider mmap()&#039;ing files into a backend?&lt;br /&gt;
|Doing I/O to large tables would consume a lot of address space or require frequent mapping/unmapping.  Extending the file also causes mapping problems that might require mapping only individual pages, leading to thousands of mappings.  Another problem is that there is no way to _prevent_ I/O to disk from the dirty shared buffers so changes could hit disk before WAL is written.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add a script to ask system configuration questions and tune postgresql.conf}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider ways of storing rows more compactly on disk:&lt;br /&gt;
* Reduce the row header size?&lt;br /&gt;
* Consider reducing on-disk varlena length from four bytes to two because a heap row cannot be more than 64k in length}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider transaction start/end performance improvements&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00948.php &amp;lt;nowiki&amp;gt;Reducing Transaction Start/End Contention&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00361.php &amp;lt;nowiki&amp;gt;Re: Reducing Transaction Start/End Contention&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow configuration of backend priorities via the operating system&lt;br /&gt;
|Though backend priorities make priority inversion during lock waits possible, research shows that this is not a huge problem.&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php &amp;lt;nowiki&amp;gt;Priorities for users or queries?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider increasing the minimum allowed number of shared buffers&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-bugs/2008-02/msg00157.php &amp;lt;nowiki&amp;gt;Re: [PATCH] Don&#039;t bail with legitimate -N/-B options&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider if CommandCounterIncrement() can avoid its AcceptInvalidationMessages() call&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-committers/2007-11/msg00585.php &amp;lt;nowiki&amp;gt;pgsql: Avoid incrementing the CommandCounter when&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider Cartesian joins when both relations are needed to form an indexscan qualification for a third relation&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-performance/2007-12/msg00090.php &amp;lt;nowiki&amp;gt;Re: TB-sized databases&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider not storing a NULL bitmap on disk if all the NULLs are trailing&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-12/msg00624.php &amp;lt;nowiki&amp;gt;Proposal for Null Bitmap Optimization(for Trailing NULLs)&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2007-12/msg00109.php &amp;lt;nowiki&amp;gt;Re: [HACKERS] Proposal for Null Bitmap Optimization(for TrailingNULLs)&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Sort large UPDATE/DELETEs so it is done in heap order&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg01119.php &amp;lt;nowiki&amp;gt;Possible future performance improvement: sort updates/deletes by ctid&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow one transaction to see tuples using the snapshot of another transaction&lt;br /&gt;
|This would assist multiple backends in working together. &lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00400.php &amp;lt;nowiki&amp;gt;Transaction Snapshot Cloning&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider decreasing the I/O caused by updating tuple hint bits&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-05/msg00847.php &amp;lt;nowiki&amp;gt;Hint Bits and Write I/O&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2008-07/msg00199.php &amp;lt;nowiki&amp;gt;Re: [HACKERS] Hint Bits and Write I/O&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Miscellaneous Other ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Deal with encoding issues for filenames in the server filesystem&lt;br /&gt;
* {{MessageLink|20090413184335.39BE.52131E4D@oss.ntt.co.jp|a proposed patch here}}&lt;br /&gt;
* {{MessageLink|8484.1244655656@sss.pgh.pa.us|some issues about it here}}&lt;br /&gt;
* {{MessageLink|20100107103740.97A5.52131E4D@oss.ntt.co.jp|Windows-specific patch here}}&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Deal with encoding issues in the output of localeconv()&lt;br /&gt;
* [http://archives.postgresql.org/message-id/40c6d9160904210658y590377cfw6dbbecb53d2b8be0@mail.gmail.com bug report]&lt;br /&gt;
* [http://archives.postgresql.org/message-id/49EF8DA0.90008@tpf.co.jp draft patch]&lt;br /&gt;
* [http://archives.postgresql.org/message-id/21710.1243620986@sss.pgh.pa.us review of patch]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Provide schema name and other fields available from SQL GET DIAGNOSTICS in error reports&lt;br /&gt;
* [http://archives.postgresql.org/message-id/dcc563d10810211907n3c59a920ia9eb7cd2a6d5ea58@mail.gmail.com &amp;lt;nowiki&amp;gt;How to get schema name which violates fk constraint&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-11/msg00846.php&lt;br /&gt;
* {{MessageLink|3191.1263306359@sss.pgh.pa.us|Re: NOT NULL violation and error-message}}&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-08/msg00213.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Source Code ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add use of &#039;const&#039; for variables in source tree}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Move some things from contrib into main tree}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemEasy&lt;br /&gt;
|Remove warnings created by -Wcast-align}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Move platform-specific ps status display info from ps_status.c to ports}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add optional CRC checksum to heap and index pages&lt;br /&gt;
|One difficulty is how to prevent hint bit changes from affecting the computed CRC checksum.&lt;br /&gt;
* http://archives.postgresql.org/message-id/19934.1226601952%40sss.pgh.pa.us&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-10/msg00002.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-10/msg01028.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-11/msg00524.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-12/msg01101.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-12/msg00011.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve documentation to build only interfaces}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow cross-compiling by generating the zic database on the target system}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve NLS maintenance of libpgport messages linked onto applications}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve the module installation experience (/contrib, etc)&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-04/msg00132.php &amp;lt;nowiki&amp;gt;modules&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* {{messageLink|ca33c0a30807231640n6fb4035dod8121a18aa1fa29c@mail.gmail.com|Re: PostgreSQL extensions packaging}}&lt;br /&gt;
* {{messageLink|ca33c0a30804061349s41b4d8fcsa9c579454b27ecd2@mail.gmail.com|Database owner installable modules patch}}&lt;br /&gt;
* http://archives.postgresql.org//pgsql-hackers/2009-03/msg00855.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-05/msg00912.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Use UTF8 encoding for NLS messages so all server encodings can read them properly}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Update Bonjour to work with newer cross-platform SDK&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-09/msg02238.php &amp;lt;nowiki&amp;gt;Darwin stuff is getting deprecated&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2006-10/msg00048.php &amp;lt;nowiki&amp;gt;Use dns_sd.h for Bonjour&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow creation of universal binaries for Darwin&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-07/msg00884.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider GnuTLS if OpenSSL license becomes a problem&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php &amp;lt;nowiki&amp;gt;[PATCH] Add support for GnuTLS&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-12/msg01213.php &amp;lt;nowiki&amp;gt;TODO: GNU TLS&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider making NAMEDATALEN more configurable in future releases}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Research use of signals and sleep wake ups&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-07/msg00003.php &amp;lt;nowiki&amp;gt;Restartable signals &#039;n all that&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Add automated check for invalid C++ source code constructs&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2007-07/msg00056.php &amp;lt;nowiki&amp;gt;Re: SPI-header-files safe for C++-compiler&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow C++ code to more easily access backend code&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-12/msg00302.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider simplifying how memory context resets handle child contexts&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2007-08/msg00067.php &amp;lt;nowiki&amp;gt;Re: Memory leak in nodeAgg&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Create three versions of libpgport to simplify client code&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-10/msg00154.php &amp;lt;nowiki&amp;gt;8.4 TODO item: make src/port support libpq and ecpg directly&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve detection of shared memory segments being used by others by checking the SysV shared memory field &#039;nattch&#039;&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00656.php &amp;lt;nowiki&amp;gt;postgresql in FreeBSD jails: proposal&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00673.php &amp;lt;nowiki&amp;gt;Re: postgresql in FreeBSD jails: proposal&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Implement the non-threaded Avahi service discovery protocol&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00939.php &amp;lt;nowiki&amp;gt;Re: [PATCHES] Avahi support for Postgresql&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2008-02/msg00097.php &amp;lt;nowiki&amp;gt;Re: Avahi support for Postgresql&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg01211.php &amp;lt;nowiki&amp;gt;Re: [PATCHES] Avahi support for Postgresql&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2008-04/msg00001.php &amp;lt;nowiki&amp;gt;Re: [HACKERS] Avahi support for Postgresql&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix system views like pg_stat_all_tables to use set-returning functions, rather than views of per-column functions}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Allow table and index WITH options to be specified via hooks, for use with plugins like GiST index methods&lt;br /&gt;
* {{MessageLink|20090105171428.77B29754A17@cvs.postgresql.org|Change the reloptions machinery to use a table-based parser}}&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Reduce data row alignment requirements on some 64-bit systems&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-10/msg00369.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add support for returning multiple result sets?&lt;br /&gt;
* http://archives.postgresql.org/pgsql-general/2008-10/msg00454.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Restructure TOAST internal storage format for greater flexibility&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-11/msg00049.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Allow setting of system oids during object creation, for use by pg_migrator&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2009-08/msg00401.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=== Documentation ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Convert single quotes to apostrophes in the PDF documentation&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-docs/2007-12/msg00059.php &amp;lt;nowiki&amp;gt;SGML docs and pdf single-quotes&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Provide a manpage for postgresql.conf&lt;br /&gt;
* {{messageLink|20080819194311.GH4428@alvh.no-ip.org|A smaller default postgresql.conf}}&lt;br /&gt;
* {{messageLink|200808211910.37524.peter_e@gmx.net|A smaller default postgresql.conf}}&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Change the manpage-generating toolchain to use the new XML-based docbook2x tools&lt;br /&gt;
* {{messageLink|200808211910.37524.peter_e@gmx.net|A smaller default postgresql.conf}}}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider changing documentation format from SGML to XML&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-docs/2006-12/msg00152.php &amp;lt;nowiki&amp;gt;Re: Authoring Tools WAS: Switching to XML&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== Windows ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Remove configure.in check for link failure when cause is found}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Remove readdir() errno patch when runtime/mingwex/dirent.c rev 1.4 is released}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow psql to use readline once non-US code pages work with backslashes}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix problem with shared memory on the Win32 Terminal Server}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Diagnose problem where shared memory can sometimes not be attached by postmaster children&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-general/2007-08/msg01377.php &amp;lt;nowiki&amp;gt;FATAL: could not reattach to shared memory (Win32)&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/message-id/13271.1241561721@sss.pgh.pa.us &amp;lt;nowiki&amp;gt;Re: &amp;quot;could not reattach to shared memory&amp;quot; captured in buildfarm&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve signal handling&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php &amp;lt;nowiki&amp;gt;Simplify Win32 Signaling code&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Convert MSVC build system to remove most batch files&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2007-08/msg00961.php &amp;lt;nowiki&amp;gt;MSVC build system&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Support pgxs when using MSVC}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix MSVC NLS support, like for to_char()&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-02/msg00485.php &amp;lt;nowiki&amp;gt;NLS on MSVC  strikes back!&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-patches/2008-02/msg00038.php &amp;lt;nowiki&amp;gt;Fix for 8.3 MSVC locale (Was  [HACKERS] NLS on MSVC strikes back!)&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix locale-aware handling (e.g. monetary) for specific server/client encoding combinations&lt;br /&gt;
* http://archives.postgresql.org/pgsql-general/2009-04/msg00799.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Find a correct rint() substitute on Windows&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00808.php &amp;lt;nowiki&amp;gt;Minor bug in src/port/rint.c&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Reduce compiler warnings on 64-bit Windows&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-07/msg00437.php&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-07/msg00440.php }}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Fix global namespace issues when using multiple terminal server sessions&lt;br /&gt;
* [http://archives.postgresql.org/message-id/48F3BFCC.8030107@dunslane.net problems with Windows global namespace]}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Change from the current autoconf/gmake build system to cmake&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-12/msg01869.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Improve consistency of path separator usage&lt;br /&gt;
* http://archives.postgresql.org/message-id/49C0BDC5.4010002@hagander.net&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItemDone&lt;br /&gt;
|Allow compilation using MSVC 2008&lt;br /&gt;
* http://archives.postgresql.org/pgsql-general/2009-08/msg01172.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
=== Wire Protocol Changes ===&lt;br /&gt;
{{TodoSubsection}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow dynamic character set handling}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add decoded type, length, precision}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Use compression?}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Update clients to use data types, typmod, schema.table.column names of result sets using new statement protocol}}&lt;br /&gt;
&lt;br /&gt;
{{TodoEndSubsection}}&lt;br /&gt;
&lt;br /&gt;
== Exotic Features ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add pre-parsing phase that converts non-ISO syntax to supported syntax&lt;br /&gt;
|This could allow SQL written for other databases to run without modification.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Allow plug-in modules to emulate features from other databases}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add features of Oracle-style packages&lt;br /&gt;
|A package would be a schema with session-local variables, public/private functions, and initialization functions.  It is also possible to implement these capabilities in any schema and not use a separate &amp;amp;quot;packages&amp;amp;quot; syntax at all.&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php &amp;lt;nowiki&amp;gt;proposal for PL packages for 8.3.&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Consider allowing control of upper/lower case folding of unquoted identifiers&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php &amp;lt;nowiki&amp;gt;Bringing PostgreSQL torwards the standard regarding case folding&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-10/msg01527.php &amp;lt;nowiki&amp;gt;Re: [SQL] Case Preservation disregarding case sensitivity?&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-03/msg00849.php &amp;lt;nowiki&amp;gt;TODO Item: Consider allowing control of upper/lower case folding of unquoted,  identifiers&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-07/msg00415.php &amp;lt;nowiki&amp;gt;Identifier case folding notes&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2008-07/msg00415.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Add autonomous transactions&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php &amp;lt;nowiki&amp;gt;autonomous transactions&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Give query progress indication&lt;br /&gt;
* [[Query progress indication]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Rethinking our type system&lt;br /&gt;
* [[Rethinking datatypes]]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Features We Do &#039;&#039;Not&#039;&#039; Want ==&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|All backends running as threads in a single process (not wanted)&lt;br /&gt;
|This eliminates the process protection we get from the current setup. Thread creation is usually the same overhead as process creation on modern systems, so it seems unwise to use a pure threaded model, and MySQL and DB2 have demonstrated that threads introduce as many issues as they solve.  Threading specific operations such as I/O, seq scans, and connection management has been discussed and will probably be implemented to enable specific performance features.  Moving to a threaded engine would also require halting all other work on PostgreSQL for one to two years.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Optimizer hints (not wanted)&lt;br /&gt;
|Optimizer hints are used to work around problems in the optimizer and introduce upgrade and maintenance issues.  We would rather have the problems reported and fixed.  We have discussed a more sophisticated system of per-class cost adjustment instead, but a specification remains to be developed.&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-08/msg00506.php &amp;lt;nowiki&amp;gt;Re: An Idea for planner hints&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-10/msg00517.php &amp;lt;nowiki&amp;gt;Index Tuning Features&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
* [http://archives.postgresql.org/pgsql-hackers/2006-10/msg00663.php &amp;lt;nowiki&amp;gt;Re: [PERFORM] Hints proposal&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Embedded server (not wanted)&lt;br /&gt;
|While PostgreSQL clients runs fine in limited-resource environments, the server requires multiple processes and a stable pool of resources to run reliably and efficiently. Stripping down the PostgreSQL server to run in the same process address space as the client application would add too much complexity and failure cases. Besides, there are several very mature embedded SQL databases already available.}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Obfuscated function source code (not wanted)&lt;br /&gt;
|Obfuscating function source code has minimal protective benefits because anyone with super-user access can find a way to view the code. At the same time, it would greatly complicate backups and other administrative tasks. To prevent non-super-users from viewing function source code, remove SELECT permission on pg_proc.&lt;br /&gt;
* http://archives.postgresql.org/pgsql-general/2008-09/msg00668.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{TodoItem&lt;br /&gt;
|Indeterminate behavior for the GROUP BY clause (not wanted)&lt;br /&gt;
|At least one other database product allows specification of a subset of the result columns which GROUP BY would need to be able to provide predictable results; the server is free to return any value from the group.  This is not viewed as a desirable feature.&lt;br /&gt;
* http://archives.postgresql.org/pgsql-hackers/2010-03/msg00297.php&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Todo]]&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10339</id>
		<title>TestFest For 9 JP</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10339"/>
		<updated>2010-03-29T00:54:06Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* 持ち物 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== 概要 ==&lt;br /&gt;
PostgreSQL 9のベータリリースに合わせて、Hackathon形式で集中テストを行います。同日にサンフランシスコで行われる[[SFPUG_Beta_Test_Day]]と連携します。&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;以下は現在時点での情報です。変更になる可能性がありますのでご注意ください。&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== 内容 ==&lt;br /&gt;
&lt;br /&gt;
基本的にはSFPUGのテスト内容に準じます。&lt;br /&gt;
&lt;br /&gt;
* コンパイルテスト&lt;br /&gt;
** 各種オプション付けて&lt;br /&gt;
** contribモジュール&lt;br /&gt;
** 外部モジュール&lt;br /&gt;
** 回帰テスト&lt;br /&gt;
* pgBenchテスト&lt;br /&gt;
** 8.4 vs. 9.0&lt;br /&gt;
* 新機能テスト （[http://lets.postgresql.jp/documents/technical/9.0/1 新機能紹介ページ]）&lt;br /&gt;
** ホットスタンバイ&lt;br /&gt;
** ストリーミングレプリケーション&lt;br /&gt;
** 除外制約&lt;br /&gt;
** LISTEN/NOTIFY&lt;br /&gt;
** DO文（各種言語で）&lt;br /&gt;
** 追加されたウィンドウ関数フレーム&lt;br /&gt;
** その他募集中&lt;br /&gt;
* データベース移行テスト データの用意もお願いします！&lt;br /&gt;
* アプリケーション移行テスト&lt;br /&gt;
** MediaWiki&lt;br /&gt;
** Slony&lt;br /&gt;
** Bucardo&lt;br /&gt;
** pgsnmpd&lt;br /&gt;
** pgpool&lt;br /&gt;
** textsearch_senna&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ドライバ&lt;br /&gt;
** Java&lt;br /&gt;
** Python&lt;br /&gt;
*** psycopg2&lt;br /&gt;
** Perl&lt;br /&gt;
*** DBD::Pg&lt;br /&gt;
** R&lt;br /&gt;
** Ruby&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ORMツール&lt;br /&gt;
** SQLAlchemy&lt;br /&gt;
** Django&lt;br /&gt;
** Hibernate&lt;br /&gt;
** その他募集中&lt;br /&gt;
&lt;br /&gt;
9を先取りして勉強することができます。記事等観てもぱっとわからない機能も隣の人が教えてくれます。また、PostgreSQLの今後の開発や普段疑問に思っていることなどについて自由にディスカッションできます。たぶん飲みながらやるのでぐだぐだになりそうです。&lt;br /&gt;
&lt;br /&gt;
== 場所 ==&lt;br /&gt;
フォルシア株式会社 会議室&lt;br /&gt;
&lt;br /&gt;
東京都新宿区新宿4丁目3-25 オリックス新宿ビル9階&lt;br /&gt;
[http://maps.google.co.jp/maps?f=q&amp;amp;hl=ja&amp;amp;geocode=&amp;amp;time=&amp;amp;date=&amp;amp;ttype=&amp;amp;q=%93%8C%8B%9E%93s%90V%8Fh%8B%E6%90V%8Fh%82S%92%9A%96%DA%82R-%82Q%82T&amp;amp;ie=UTF8&amp;amp;ll=35.689321,139.704277&amp;amp;spn=0.010386,0.013776&amp;amp;z=14&amp;amp;iwloc=addr&amp;amp;om=1&amp;amp;source=embed Google Map]&lt;br /&gt;
&lt;br /&gt;
新宿駅南口徒歩3分&lt;br /&gt;
東京メトロ新宿3丁目駅徒歩1分&lt;br /&gt;
&lt;br /&gt;
== 時間 ==&lt;br /&gt;
4月4日 午前3時～午前10時（日本時間）&lt;br /&gt;
※サンフランシスコ時間4月3日午前11時～午後6時で行われるTestに合わせています。&lt;br /&gt;
&lt;br /&gt;
時間が時間なので前日からのスタンバイあり&lt;br /&gt;
&lt;br /&gt;
== 食事 ==&lt;br /&gt;
軽食を用意します。持ち込み（飲食）歓迎。徒歩圏内でも調達可能。&lt;br /&gt;
&lt;br /&gt;
== 持ち物 ==&lt;br /&gt;
ラップトップ持参。インターネット環境（DHCP）は用意します。Wi-fiに対応できるかは調整中。各自テスト環境を外部サーバに用意できれば尚可。&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ &lt;br /&gt;
&#039;&#039;&#039;テスト環境&#039;&#039;&#039;&lt;br /&gt;
| &#039;&#039;&#039;所有者&#039;&#039;&#039; || &#039;&#039;&#039;アーキテクチャ&#039;&#039;&#039; || &#039;&#039;&#039;OS&#039;&#039;&#039; || &#039;&#039;&#039;IPアドレス&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || Red Hat Enterprise Linux 5.4 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || CentOS 5.3 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || FreeBSD 6.4 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32  || MacOS X 10.5.8 || x.x.x.x&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86 || 未定 || （Amazon EC2）&lt;br /&gt;
|-&lt;br /&gt;
| 原田 || x64 || Windows || Amazon EC2&lt;br /&gt;
|-&lt;br /&gt;
| 原田 || x86,x64 || Linux(some distros) x N || Amazon EC2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== 参加者一覧 ==&lt;br /&gt;
&lt;br /&gt;
ATNDを参照ください。&lt;br /&gt;
http://atnd.org/events/3785&lt;br /&gt;
&lt;br /&gt;
== その他 ==&lt;br /&gt;
* TwitterでSFPUGと連携します（したいです）&lt;br /&gt;
* Ustreamできるかどうか検討中。東京にいない人も参加するなら必須？機器を用意できる方歓迎。&lt;br /&gt;
* ライトニングトーク？&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10338</id>
		<title>TestFest For 9 JP</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10338"/>
		<updated>2010-03-29T00:53:47Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* 持ち物 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== 概要 ==&lt;br /&gt;
PostgreSQL 9のベータリリースに合わせて、Hackathon形式で集中テストを行います。同日にサンフランシスコで行われる[[SFPUG_Beta_Test_Day]]と連携します。&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;以下は現在時点での情報です。変更になる可能性がありますのでご注意ください。&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== 内容 ==&lt;br /&gt;
&lt;br /&gt;
基本的にはSFPUGのテスト内容に準じます。&lt;br /&gt;
&lt;br /&gt;
* コンパイルテスト&lt;br /&gt;
** 各種オプション付けて&lt;br /&gt;
** contribモジュール&lt;br /&gt;
** 外部モジュール&lt;br /&gt;
** 回帰テスト&lt;br /&gt;
* pgBenchテスト&lt;br /&gt;
** 8.4 vs. 9.0&lt;br /&gt;
* 新機能テスト （[http://lets.postgresql.jp/documents/technical/9.0/1 新機能紹介ページ]）&lt;br /&gt;
** ホットスタンバイ&lt;br /&gt;
** ストリーミングレプリケーション&lt;br /&gt;
** 除外制約&lt;br /&gt;
** LISTEN/NOTIFY&lt;br /&gt;
** DO文（各種言語で）&lt;br /&gt;
** 追加されたウィンドウ関数フレーム&lt;br /&gt;
** その他募集中&lt;br /&gt;
* データベース移行テスト データの用意もお願いします！&lt;br /&gt;
* アプリケーション移行テスト&lt;br /&gt;
** MediaWiki&lt;br /&gt;
** Slony&lt;br /&gt;
** Bucardo&lt;br /&gt;
** pgsnmpd&lt;br /&gt;
** pgpool&lt;br /&gt;
** textsearch_senna&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ドライバ&lt;br /&gt;
** Java&lt;br /&gt;
** Python&lt;br /&gt;
*** psycopg2&lt;br /&gt;
** Perl&lt;br /&gt;
*** DBD::Pg&lt;br /&gt;
** R&lt;br /&gt;
** Ruby&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ORMツール&lt;br /&gt;
** SQLAlchemy&lt;br /&gt;
** Django&lt;br /&gt;
** Hibernate&lt;br /&gt;
** その他募集中&lt;br /&gt;
&lt;br /&gt;
9を先取りして勉強することができます。記事等観てもぱっとわからない機能も隣の人が教えてくれます。また、PostgreSQLの今後の開発や普段疑問に思っていることなどについて自由にディスカッションできます。たぶん飲みながらやるのでぐだぐだになりそうです。&lt;br /&gt;
&lt;br /&gt;
== 場所 ==&lt;br /&gt;
フォルシア株式会社 会議室&lt;br /&gt;
&lt;br /&gt;
東京都新宿区新宿4丁目3-25 オリックス新宿ビル9階&lt;br /&gt;
[http://maps.google.co.jp/maps?f=q&amp;amp;hl=ja&amp;amp;geocode=&amp;amp;time=&amp;amp;date=&amp;amp;ttype=&amp;amp;q=%93%8C%8B%9E%93s%90V%8Fh%8B%E6%90V%8Fh%82S%92%9A%96%DA%82R-%82Q%82T&amp;amp;ie=UTF8&amp;amp;ll=35.689321,139.704277&amp;amp;spn=0.010386,0.013776&amp;amp;z=14&amp;amp;iwloc=addr&amp;amp;om=1&amp;amp;source=embed Google Map]&lt;br /&gt;
&lt;br /&gt;
新宿駅南口徒歩3分&lt;br /&gt;
東京メトロ新宿3丁目駅徒歩1分&lt;br /&gt;
&lt;br /&gt;
== 時間 ==&lt;br /&gt;
4月4日 午前3時～午前10時（日本時間）&lt;br /&gt;
※サンフランシスコ時間4月3日午前11時～午後6時で行われるTestに合わせています。&lt;br /&gt;
&lt;br /&gt;
時間が時間なので前日からのスタンバイあり&lt;br /&gt;
&lt;br /&gt;
== 食事 ==&lt;br /&gt;
軽食を用意します。持ち込み（飲食）歓迎。徒歩圏内でも調達可能。&lt;br /&gt;
&lt;br /&gt;
== 持ち物 ==&lt;br /&gt;
ラップトップ持参。インターネット環境（DHCP）は用意します。Wi-fiに対応できるかは調整中。各自テスト環境を外部サーバに用意できれば尚可。&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ &lt;br /&gt;
&#039;&#039;&#039;テスト環境&#039;&#039;&#039;&lt;br /&gt;
| &#039;&#039;&#039;所有者&#039;&#039;&#039; || &#039;&#039;&#039;アーキテクチャ&#039;&#039;&#039; || &#039;&#039;&#039;OS&#039;&#039;&#039; || &#039;&#039;&#039;IPアドレス&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || Red Hat Enterprise Linux 5.4 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || CentOS 5.3 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32 (VM) || FreeBSD 6.4 || （外部リモート）&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86_32  || MacOS X 10.5.8 || x.x.x.x&lt;br /&gt;
|-&lt;br /&gt;
| 永安 || x86 || 未定 || （Amazon EC2）&lt;br /&gt;
| 原田 || x64 || Windows || Amazon EC2&lt;br /&gt;
| 原田 || x86,x64 || Linux(some distros) x N || Amazon EC2&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== 参加者一覧 ==&lt;br /&gt;
&lt;br /&gt;
ATNDを参照ください。&lt;br /&gt;
http://atnd.org/events/3785&lt;br /&gt;
&lt;br /&gt;
== その他 ==&lt;br /&gt;
* TwitterでSFPUGと連携します（したいです）&lt;br /&gt;
* Ustreamできるかどうか検討中。東京にいない人も参加するなら必須？機器を用意できる方歓迎。&lt;br /&gt;
* ライトニングトーク？&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10286</id>
		<title>TestFest For 9 JP</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10286"/>
		<updated>2010-03-20T13:30:31Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* 場所 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== 概要 ==&lt;br /&gt;
PostgreSQL 9のベータリリースに合わせて、Hackathon形式で集中テストを行います。同日にサンフランシスコで行われる[[SFPUG_Beta_Test_Day]]と連携します。&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;以下は現在時点での情報です。変更になる可能性がありますのでご注意ください。&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== 内容 ==&lt;br /&gt;
&lt;br /&gt;
基本的にはSFPUGのテスト内容に準じます。&lt;br /&gt;
&lt;br /&gt;
* コンパイルテスト&lt;br /&gt;
** 各種オプション付けて&lt;br /&gt;
** contribモジュール&lt;br /&gt;
** 外部モジュール&lt;br /&gt;
** 回帰テスト&lt;br /&gt;
* pgBenchテスト&lt;br /&gt;
** 8.4 vs. 9.0&lt;br /&gt;
* 新機能テスト （[http://lets.postgresql.jp/documents/technical/9.0/1 新機能紹介ページ]）&lt;br /&gt;
** ホットスタンバイ&lt;br /&gt;
** ストリーミングレプリケーション&lt;br /&gt;
** 除外制約&lt;br /&gt;
** LISTEN/NOTIFY&lt;br /&gt;
** DO文（各種言語で）&lt;br /&gt;
** 追加されたウィンドウ関数フレーム&lt;br /&gt;
** その他募集中&lt;br /&gt;
* データベース移行テスト データの用意もお願いします！&lt;br /&gt;
* アプリケーション移行テスト&lt;br /&gt;
** MediaWiki&lt;br /&gt;
** Slony&lt;br /&gt;
** Bucardo&lt;br /&gt;
** pgsnmpd&lt;br /&gt;
** pgpool&lt;br /&gt;
** textsearch_senna&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ドライバ&lt;br /&gt;
** Java&lt;br /&gt;
** Python&lt;br /&gt;
*** psycopg2&lt;br /&gt;
** Perl&lt;br /&gt;
*** DBD::Pg&lt;br /&gt;
** R&lt;br /&gt;
** Ruby&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ORMツール&lt;br /&gt;
** SQLAlchemy&lt;br /&gt;
** Django&lt;br /&gt;
** Hibernate&lt;br /&gt;
** その他募集中&lt;br /&gt;
&lt;br /&gt;
9を先取りして勉強することができます。記事等観てもぱっとわからない機能も隣の人が教えてくれます。また、PostgreSQLの今後の開発や普段疑問に思っていることなどについて自由にディスカッションできます。たぶん飲みながらやるのでぐだぐだになりそうです。&lt;br /&gt;
&lt;br /&gt;
== 場所 ==&lt;br /&gt;
フォルシア株式会社 会議室&lt;br /&gt;
&lt;br /&gt;
東京都新宿区新宿4丁目3-25 オリックス新宿ビル9階&lt;br /&gt;
[http://maps.google.co.jp/maps?f=q&amp;amp;hl=ja&amp;amp;geocode=&amp;amp;time=&amp;amp;date=&amp;amp;ttype=&amp;amp;q=%93%8C%8B%9E%93s%90V%8Fh%8B%E6%90V%8Fh%82S%92%9A%96%DA%82R-%82Q%82T&amp;amp;ie=UTF8&amp;amp;ll=35.689321,139.704277&amp;amp;spn=0.010386,0.013776&amp;amp;z=14&amp;amp;iwloc=addr&amp;amp;om=1&amp;amp;source=embed Google Map]&lt;br /&gt;
&lt;br /&gt;
新宿駅南口徒歩3分&lt;br /&gt;
東京メトロ新宿3丁目駅徒歩1分&lt;br /&gt;
&lt;br /&gt;
== 時間 ==&lt;br /&gt;
4月4日 午前3時～午前10時（日本時間）&lt;br /&gt;
※サンフランシスコ時間4月3日午前11時～午後6時で行われるTestに合わせています。&lt;br /&gt;
&lt;br /&gt;
時間が時間なので前日からのスタンバイあり&lt;br /&gt;
&lt;br /&gt;
== 食事 ==&lt;br /&gt;
軽食を用意します。持ち込み（飲食）歓迎。徒歩圏内でも調達可能。&lt;br /&gt;
&lt;br /&gt;
== 持ち物 ==&lt;br /&gt;
ラップトップ持参。インターネット環境（DHCP）は用意します。Wi-fiに対応できるかは調整中。各自テスト環境を外部サーバに用意できれば尚可。&lt;br /&gt;
&lt;br /&gt;
== その他 ==&lt;br /&gt;
* TwitterでSFPUGと連携します（したいです）&lt;br /&gt;
* Ustreamできるかどうか検討中。東京にいない人も参加するなら必須？機器を用意できる方歓迎。&lt;br /&gt;
* ライトニングトーク？&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10285</id>
		<title>TestFest For 9 JP</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10285"/>
		<updated>2010-03-20T13:29:37Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* 内容 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== 概要 ==&lt;br /&gt;
PostgreSQL 9のベータリリースに合わせて、Hackathon形式で集中テストを行います。同日にサンフランシスコで行われる[[SFPUG_Beta_Test_Day]]と連携します。&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;以下は現在時点での情報です。変更になる可能性がありますのでご注意ください。&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== 内容 ==&lt;br /&gt;
&lt;br /&gt;
基本的にはSFPUGのテスト内容に準じます。&lt;br /&gt;
&lt;br /&gt;
* コンパイルテスト&lt;br /&gt;
** 各種オプション付けて&lt;br /&gt;
** contribモジュール&lt;br /&gt;
** 外部モジュール&lt;br /&gt;
** 回帰テスト&lt;br /&gt;
* pgBenchテスト&lt;br /&gt;
** 8.4 vs. 9.0&lt;br /&gt;
* 新機能テスト （[http://lets.postgresql.jp/documents/technical/9.0/1 新機能紹介ページ]）&lt;br /&gt;
** ホットスタンバイ&lt;br /&gt;
** ストリーミングレプリケーション&lt;br /&gt;
** 除外制約&lt;br /&gt;
** LISTEN/NOTIFY&lt;br /&gt;
** DO文（各種言語で）&lt;br /&gt;
** 追加されたウィンドウ関数フレーム&lt;br /&gt;
** その他募集中&lt;br /&gt;
* データベース移行テスト データの用意もお願いします！&lt;br /&gt;
* アプリケーション移行テスト&lt;br /&gt;
** MediaWiki&lt;br /&gt;
** Slony&lt;br /&gt;
** Bucardo&lt;br /&gt;
** pgsnmpd&lt;br /&gt;
** pgpool&lt;br /&gt;
** textsearch_senna&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ドライバ&lt;br /&gt;
** Java&lt;br /&gt;
** Python&lt;br /&gt;
*** psycopg2&lt;br /&gt;
** Perl&lt;br /&gt;
*** DBD::Pg&lt;br /&gt;
** R&lt;br /&gt;
** Ruby&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ORMツール&lt;br /&gt;
** SQLAlchemy&lt;br /&gt;
** Django&lt;br /&gt;
** Hibernate&lt;br /&gt;
** その他募集中&lt;br /&gt;
&lt;br /&gt;
9を先取りして勉強することができます。記事等観てもぱっとわからない機能も隣の人が教えてくれます。また、PostgreSQLの今後の開発や普段疑問に思っていることなどについて自由にディスカッションできます。たぶん飲みながらやるのでぐだぐだになりそうです。&lt;br /&gt;
&lt;br /&gt;
== 場所 ==&lt;br /&gt;
フォルシア株式会社 会議室&lt;br /&gt;
&lt;br /&gt;
東京都新宿区新宿4丁目3-25 オリックス新宿ビル9階&lt;br /&gt;
[http://maps.google.co.jp/maps?f=q&amp;amp;hl=ja&amp;amp;geocode=&amp;amp;time=&amp;amp;date=&amp;amp;ttype=&amp;amp;q=%93%8C%8B%9E%93s%90V%8Fh%8B%E6%90V%8Fh%82S%92%9A%96%DA%82R-%82Q%82T&amp;amp;ie=UTF8&amp;amp;ll=35.689321,139.704277&amp;amp;spn=0.010386,0.013776&amp;amp;z=14&amp;amp;iwloc=addr&amp;amp;om=1&amp;amp;source=embed]&lt;br /&gt;
&lt;br /&gt;
新宿駅南口徒歩3分&lt;br /&gt;
東京メトロ新宿3丁目駅徒歩1分&lt;br /&gt;
&lt;br /&gt;
== 時間 ==&lt;br /&gt;
4月4日 午前3時～午前10時（日本時間）&lt;br /&gt;
※サンフランシスコ時間4月3日午前11時～午後6時で行われるTestに合わせています。&lt;br /&gt;
&lt;br /&gt;
時間が時間なので前日からのスタンバイあり&lt;br /&gt;
&lt;br /&gt;
== 食事 ==&lt;br /&gt;
軽食を用意します。持ち込み（飲食）歓迎。徒歩圏内でも調達可能。&lt;br /&gt;
&lt;br /&gt;
== 持ち物 ==&lt;br /&gt;
ラップトップ持参。インターネット環境（DHCP）は用意します。Wi-fiに対応できるかは調整中。各自テスト環境を外部サーバに用意できれば尚可。&lt;br /&gt;
&lt;br /&gt;
== その他 ==&lt;br /&gt;
* TwitterでSFPUGと連携します（したいです）&lt;br /&gt;
* Ustreamできるかどうか検討中。東京にいない人も参加するなら必須？機器を用意できる方歓迎。&lt;br /&gt;
* ライトニングトーク？&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10284</id>
		<title>TestFest For 9 JP</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=TestFest_For_9_JP&amp;diff=10284"/>
		<updated>2010-03-20T13:26:57Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: New page: == 概要 == PostgreSQL 9のベータリリースに合わせて、Hackathon形式で集中テストを行います。同日にサンフランシスコで行われる[[SFPUG_Beta_Test_Day]...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== 概要 ==&lt;br /&gt;
PostgreSQL 9のベータリリースに合わせて、Hackathon形式で集中テストを行います。同日にサンフランシスコで行われる[[SFPUG_Beta_Test_Day]]と連携します。&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;以下は現在時点での情報です。変更になる可能性がありますのでご注意ください。&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== 内容 ==&lt;br /&gt;
&lt;br /&gt;
基本的にはSFPUGのテスト内容に準じます。&lt;br /&gt;
&lt;br /&gt;
* コンパイルテスト&lt;br /&gt;
** 各種オプション付けて&lt;br /&gt;
** contribモジュール&lt;br /&gt;
** 外部モジュール&lt;br /&gt;
** 回帰テスト&lt;br /&gt;
* pgBenchテスト&lt;br /&gt;
** 8.4 vs. 9.0&lt;br /&gt;
* 新機能テスト （[http://lets.postgresql.jp/documents/technical/9.0/1]）&lt;br /&gt;
** ホットスタンバイ&lt;br /&gt;
** ストリーミングレプリケーション&lt;br /&gt;
** 除外制約&lt;br /&gt;
** LISTEN/NOTIFY&lt;br /&gt;
** DO文（各種言語で）&lt;br /&gt;
** 追加されたウィンドウ関数フレーム&lt;br /&gt;
** その他募集中&lt;br /&gt;
* データベース移行テスト データの用意もお願いします！&lt;br /&gt;
* アプリケーション移行テスト&lt;br /&gt;
** MediaWiki&lt;br /&gt;
** Slony&lt;br /&gt;
** Bucardo&lt;br /&gt;
** pgsnmpd&lt;br /&gt;
** pgpool&lt;br /&gt;
** textsearch_senna&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ドライバ&lt;br /&gt;
** Java&lt;br /&gt;
** Python&lt;br /&gt;
*** psycopg2&lt;br /&gt;
** Perl&lt;br /&gt;
*** DBD::Pg&lt;br /&gt;
** R&lt;br /&gt;
** Ruby&lt;br /&gt;
** その他募集中&lt;br /&gt;
* ORMツール&lt;br /&gt;
** SQLAlchemy&lt;br /&gt;
** Django&lt;br /&gt;
** Hibernate&lt;br /&gt;
** その他募集中&lt;br /&gt;
&lt;br /&gt;
9を先取りして勉強することができます。記事等観てもぱっとわからない機能も隣の人が教えてくれます。また、PostgreSQLの今後の開発や普段疑問に思っていることなどについて自由にディスカッションできます。たぶん飲みながらやるのでぐだぐだになりそうです。&lt;br /&gt;
&lt;br /&gt;
== 場所 ==&lt;br /&gt;
フォルシア株式会社 会議室&lt;br /&gt;
&lt;br /&gt;
東京都新宿区新宿4丁目3-25 オリックス新宿ビル9階&lt;br /&gt;
[http://maps.google.co.jp/maps?f=q&amp;amp;hl=ja&amp;amp;geocode=&amp;amp;time=&amp;amp;date=&amp;amp;ttype=&amp;amp;q=%93%8C%8B%9E%93s%90V%8Fh%8B%E6%90V%8Fh%82S%92%9A%96%DA%82R-%82Q%82T&amp;amp;ie=UTF8&amp;amp;ll=35.689321,139.704277&amp;amp;spn=0.010386,0.013776&amp;amp;z=14&amp;amp;iwloc=addr&amp;amp;om=1&amp;amp;source=embed]&lt;br /&gt;
&lt;br /&gt;
新宿駅南口徒歩3分&lt;br /&gt;
東京メトロ新宿3丁目駅徒歩1分&lt;br /&gt;
&lt;br /&gt;
== 時間 ==&lt;br /&gt;
4月4日 午前3時～午前10時（日本時間）&lt;br /&gt;
※サンフランシスコ時間4月3日午前11時～午後6時で行われるTestに合わせています。&lt;br /&gt;
&lt;br /&gt;
時間が時間なので前日からのスタンバイあり&lt;br /&gt;
&lt;br /&gt;
== 食事 ==&lt;br /&gt;
軽食を用意します。持ち込み（飲食）歓迎。徒歩圏内でも調達可能。&lt;br /&gt;
&lt;br /&gt;
== 持ち物 ==&lt;br /&gt;
ラップトップ持参。インターネット環境（DHCP）は用意します。Wi-fiに対応できるかは調整中。各自テスト環境を外部サーバに用意できれば尚可。&lt;br /&gt;
&lt;br /&gt;
== その他 ==&lt;br /&gt;
* TwitterでSFPUGと連携します（したいです）&lt;br /&gt;
* Ustreamできるかどうか検討中。東京にいない人も参加するなら必須？機器を用意できる方歓迎。&lt;br /&gt;
* ライトニングトーク？&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=SQL2008_windowing_queries&amp;diff=5053</id>
		<title>SQL2008 windowing queries</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=SQL2008_windowing_queries&amp;diff=5053"/>
		<updated>2009-03-06T14:05:55Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;strong class=&amp;quot;two&amp;quot;&amp;gt;What is SQL:2003 windowing queries?&amp;lt;/strong&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;strong&amp;gt;SQL&amp;lt;/strong&amp;gt; is a very capable language and there are very few questions that it cannot answer. However, the performance of some of these queries is not what it should be -&lt;br /&gt;
nor is the query itself easy to write in the first place. Some of the things that are hard to do in straight SQL are actually very commonly requested operations, including:&lt;br /&gt;
&lt;br /&gt;
;Calculate a running total: Show the cumulative salary within a department row by row, with each row including a summation of the prior rows&#039; salary.&lt;br /&gt;
;Find percentages within a group: Show the percentage of the total salary paid to an individual in a certain department. Take their salary and divide it by the sum of the salary in the department.&lt;br /&gt;
;Top-N queries: Find the top N highest-paid people or the top N sales by region.&lt;br /&gt;
;Compute a moving average: Average the current row&#039;s value and the previous N rows values together.&lt;br /&gt;
;Perform ranking queries: Show the relative rank of an individual&#039;s salary within their department.&lt;br /&gt;
&lt;br /&gt;
Both the &#039;&#039;Top-N&#039;&#039; and ranking queries could perhaps be implemented by simply having a result row number be returned (after sorting). The row number can then be used to calculate positional-based info. &lt;br /&gt;
&lt;br /&gt;
Analytic functions, are designed to address these issues. They add extensions&lt;br /&gt;
to the SQL language that not only make these operations easier to code; they make them faster than could be achieved with the pure SQL approach. These extensions are currently under review by the ANSI SQL committee for inclusion in the SQL specification.&lt;br /&gt;
&lt;br /&gt;
The syntax of the analytic function is rather straightforward in appearance,&lt;br /&gt;
but looks can be deceiving.&lt;br /&gt;
It starts with:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
        FUNCTION_NAME(&amp;amp;lt;argument&amp;amp;gt;,&amp;amp;lt;argument&amp;amp;gt;,...)&lt;br /&gt;
        OVER&lt;br /&gt;
        (&amp;amp;lt;Partition-Clause&amp;amp;gt; &amp;amp;lt;Order-by-Clause&amp;amp;gt; &amp;amp;lt;Frame-Clause&amp;amp;gt;)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;The PARTITION BY clause logically breaks a single result set into N groups,&lt;br /&gt;
according to the criteria set by the partition expressions. The words &#039;partition&#039; and &#039;group&#039; are used synonymously.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;The ORDER BY clause specifies how the data is sorted within each group&lt;br /&gt;
(partition).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;The FRAME clause gives us a way to define a sliding or anchored window of&lt;br /&gt;
data, on which the analytic function will operate, within a group. This clause can be used to have the analytic function compute its value based on any arbitrary sliding or anchored window within a group.&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
This example, shows how to use the analytical function &amp;lt;strong&amp;gt;SUM&amp;lt;/strong&amp;gt; to perform a&lt;br /&gt;
cumulative sum. First, we fill some values in a table. The table is very simple and consists of the field &amp;lt;em&amp;gt;dt&amp;lt;/em&amp;gt; and &amp;lt;em&amp;gt;xy&amp;lt;/em&amp;gt; only. Note, that for a given date it is possible to insert multiple rows which is exactly what I do here. What I am interested is to extract the cumulative sum for each day in the table. That is, if I have three entries for the same date, for example 3, 4 and 5, I don&#039;t want the sum to only be 3+4+5 for each row, but 3 for the first row, 3+4 for the second row and 3+4+5 for the third row.&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
        create table sum_example (&lt;br /&gt;
                                 dt date,&lt;br /&gt;
                                 xy number&lt;br /&gt;
                                );&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
	insert into sum_example values (to_date(&#039;27.08.2001&#039;,&#039;DD.MM.YYYY&#039;),4);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;02.09.2001&#039;,&#039;DD.MM.YYYY&#039;),1);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;09.09.2001&#039;,&#039;DD.MM.YYYY&#039;),5);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;26.08.2001&#039;,&#039;DD.MM.YYYY&#039;),3);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;28.08.2001&#039;,&#039;DD.MM.YYYY&#039;),4);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;26.08.2001&#039;,&#039;DD.MM.YYYY&#039;),6);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;29.08.2001&#039;,&#039;DD.MM.YYYY&#039;),9);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;30.08.2001&#039;,&#039;DD.MM.YYYY&#039;),2);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;12.09.2001&#039;,&#039;DD.MM.YYYY&#039;),7);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;23.08.2001&#039;,&#039;DD.MM.YYYY&#039;),2);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;27.08.2001&#039;,&#039;DD.MM.YYYY&#039;),5);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;09.09.2001&#039;,&#039;DD.MM.YYYY&#039;),9);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;01.09.2001&#039;,&#039;DD.MM.YYYY&#039;),3);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;07.09.2001&#039;,&#039;DD.MM.YYYY&#039;),1);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;12.09.2001&#039;,&#039;DD.MM.YYYY&#039;),4);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;03.09.2001&#039;,&#039;DD.MM.YYYY&#039;),5);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;03.09.2001&#039;,&#039;DD.MM.YYYY&#039;),8);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;07.09.2001&#039;,&#039;DD.MM.YYYY&#039;),7);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;04.09.2001&#039;,&#039;DD.MM.YYYY&#039;),8);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;09.09.2001&#039;,&#039;DD.MM.YYYY&#039;),1);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;29.08.2001&#039;,&#039;DD.MM.YYYY&#039;),3);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;30.08.2001&#039;,&#039;DD.MM.YYYY&#039;),7);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;24.08.2001&#039;,&#039;DD.MM.YYYY&#039;),7);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;07.09.2001&#039;,&#039;DD.MM.YYYY&#039;),9);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;26.08.2001&#039;,&#039;DD.MM.YYYY&#039;),2);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;09.09.2001&#039;,&#039;DD.MM.YYYY&#039;),8);&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
        select dt,&lt;br /&gt;
               sum(xy) over (partition by trunc(dt) order by dt rows between &lt;br /&gt;
                  unbounded preceding and current row) s,&lt;br /&gt;
               xy&lt;br /&gt;
        from sum_example;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
The the analytical function:&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
        sum(xy) over (partition by trunc(dt) order by dt rows between unbounded preceding and current row)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
The select statement will return:&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
23/08/01          2          2&lt;br /&gt;
24/08/01          7          7&lt;br /&gt;
26/08/01          3          3&lt;br /&gt;
26/08/01          5          2&lt;br /&gt;
26/08/01         11          6&lt;br /&gt;
27/08/01          4          4&lt;br /&gt;
27/08/01          9          5&lt;br /&gt;
28/08/01          4          4&lt;br /&gt;
29/08/01          3          3&lt;br /&gt;
29/08/01         12          9&lt;br /&gt;
30/08/01          2          2&lt;br /&gt;
30/08/01          9          7&lt;br /&gt;
01/09/01          3          3&lt;br /&gt;
02/09/01          1          1&lt;br /&gt;
03/09/01          5          5&lt;br /&gt;
03/09/01         13          8&lt;br /&gt;
04/09/01          8          8&lt;br /&gt;
07/09/01          9          9&lt;br /&gt;
07/09/01         16          7&lt;br /&gt;
07/09/01         17          1&lt;br /&gt;
09/09/01          5          5&lt;br /&gt;
09/09/01         14          9&lt;br /&gt;
09/09/01         22          8&lt;br /&gt;
09/09/01         23          1&lt;br /&gt;
12/09/01          4          4&lt;br /&gt;
12/09/01         11          7&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
The third column correspondents to xy (the values inserted with the insert&lt;br /&gt;
into ... above). The interesting column is the second. For example on the 26th of August in 2001,&lt;br /&gt;
the first row for that date&lt;br /&gt;
is 3 (equals xy), the second is 5 (equals xy+3) and the third is 11 (equals&lt;br /&gt;
xy+3+5).&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;strong&amp;gt;A list of analytic functions used in windowing queries &amp;lt;/strong&amp;gt; : &lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;AVG (&amp;amp;lt;distinct|all&amp;amp;gt; expression )&lt;br /&gt;
Used to compute an average of an expression within a group and window.&lt;br /&gt;
Distinct may be used to find the average of the values in a group after duplicates have been removed.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;CORR (expression, expression)&lt;br /&gt;
Returns the coefficient of correlation of a pair of expressions that return&lt;br /&gt;
numbers. It is shorthand for:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;COVAR_POP(expr1, expr2) /&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;STDDEV_POP(expr1) * STDDEV_POP(expr2)).&lt;br /&gt;
Statistically speaking, a correlation is the strength of an association between&lt;br /&gt;
variables. An association between variables means that the value of one variable can be predicted, to some extent, by the value of the other. The correlation coefficient gives the strength of the association by returning a number&lt;br /&gt;
between -1 (strong inverse correlation) and 1 (strong correlation). A value of&lt;br /&gt;
0 would indicate no correlation.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;COUNT (&amp;amp;lt;distinct&amp;amp;gt; &amp;amp;lt;*&amp;amp;gt; &amp;amp;lt;expression&amp;amp;gt;)&lt;br /&gt;
This will count occurrences within a group. If you specify * or some non-null&lt;br /&gt;
constant, count will count all rows. If you specify an expression, count returns the count of non-null evaluations of expression.&lt;br /&gt;
You may use the DISTINCT modifier to count occurrences of rows in a group after&lt;br /&gt;
duplicates have been removed.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;COVAR_POP (expression, expression)&lt;br /&gt;
This returns the population covariance of a pair of expressions that return numbers.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;COVAR_SAMP (expression, expression)&lt;br /&gt;
 This returns the sample covariance of a pair of expressions that return&lt;br /&gt;
numbers.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;CUME_DIST&lt;br /&gt;
 This computes the relative position of a row in a group. CUME_DIST will always&lt;br /&gt;
return a number greater then 0 and less then or equal to 1. This number represents the &#039;position&#039; of the row in the group of N rows. In a group of three rows, the cumulate distribution values returned would be 1/3, 2/3, and 3/3 for example.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;DENSE_RANK&lt;br /&gt;
 This function computes the relative rank of each row returned from a query&lt;br /&gt;
with respect to the other rows, based on the values of the expressions in the ORDER BY clause. The data within a group is sorted by the ORDER BY clause and then a numeric ranking is assigned to each row in turn starting with 1 and&lt;br /&gt;
continuing on up. The rank is incremented every time the values of the ORDER BY&lt;br /&gt;
expressions change.&lt;br /&gt;
Rows with equal values receive the same rank (nulls are considered equal in&lt;br /&gt;
this comparison). A dense rank returns a ranking number without any gaps. This is in comparison to RANK below.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;FIRST_VALUE&lt;br /&gt;
 This simply returns the first value from a group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;LAG (expression, &amp;amp;lt;offset&amp;amp;gt;, &amp;amp;lt;default&amp;amp;gt;)&lt;br /&gt;
 LAG gives you access to other rows in a resultset without doing a self-join.&lt;br /&gt;
It allows you to treat the cursor as if it were an array in effect. You can reference rows that come before the current row in a given group. This would allow you to select &#039;the previous rows&#039; from a group along with the current&lt;br /&gt;
row. See LEAD for how to get &#039;the next rows&#039;.&lt;br /&gt;
Offset is a positive integer that defaults to 1 (the previous row). Default is&lt;br /&gt;
the value to be returned if the index is out of range of the window (for the first row in a group, the default will be returned)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;LAST_VALUE&lt;br /&gt;
 This simply returns the last value from a group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;LEAD (expression, &amp;amp;lt;offset&amp;amp;gt;, &amp;amp;lt;default&amp;amp;gt;)&lt;br /&gt;
 LEAD is the opposite of LAG. Whereas LAG gives you access to the a row preceding yours in a group - LEAD gives you access to the a row that comes after your row.&lt;br /&gt;
Offset is a positive integer that defaults to 1 (the next row). Default is the&lt;br /&gt;
value to be returned if the index is out of range of the window (for the last row in a group, the default will be returned).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;MAX(expression)&lt;br /&gt;
 Finds the maximum value of expression within a window of a group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;MIN(expression)&lt;br /&gt;
 Finds the minimum value of expression within a window of a group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;NTILE (expression)&lt;br /&gt;
 Divides a group into &#039;value of expression&#039; buckets.&lt;br /&gt;
For example; if expression = 4, then each row in the group would be assigned a&lt;br /&gt;
number from 1 to 4 putting it into a percentile. If the group had 20 rows in it, the first 5 would be assigned 1, the next 5 would be assigned 2 and so on. In the event the cardinality of the group is not evenly divisible by the&lt;br /&gt;
expression, the rows are distributed such that no percentile has more than 1&lt;br /&gt;
row more then any other percentile in that group and the lowest percentiles are the ones that will have &#039;extra&#039; rows. For example, using expression = 4 again and the number of rows = 21, percentile = 1 will have 6 rows, percentile =&lt;br /&gt;
2 will have 5, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;PERCENT_RANK&lt;br /&gt;
 This is similar to the CUME_DIST (cumulative distribution) function. For a&lt;br /&gt;
given row in a group, it calculates the rank of that row minus 1, divided by 1 less than the number of rows being evaluated in the group. This function will always return values from 0 to 1 inclusive.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;RANK&lt;br /&gt;
 This function computes the relative rank of each row returned from a query&lt;br /&gt;
with respect to the other rows, based on the values of the expressions in the ORDER BY clause. The data within a group is sorted by the ORDER BY clause and then a numeric ranking is assigned to each row in turn starting with 1 and&lt;br /&gt;
continuing on up. Rows with the same values of the ORDER BY expressions receive&lt;br /&gt;
the same rank; however, if two rows do receive the same rank the rank numbers will subsequently &#039;skip&#039;. If two rows are number 1, there will be no number 2 - rank will assign the value of 3 to the next row in the group.&lt;br /&gt;
This is in contrast to DENSE_RANK, which does not skip values.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;RATIO_TO_REPORT (expression)&lt;br /&gt;
 This function computes the value of expression / (sum(expression)) over the&lt;br /&gt;
group. This gives you the percentage of the total the current row contributes to the sum(expression).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;REGR_ xxxxxxx (expression, expression)&lt;br /&gt;
 These linear regression functions fit an ordinary-least-squares regression&lt;br /&gt;
line to a pair of expressions. There are different regression functions available for use.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;ROW_NUMBER&lt;br /&gt;
 Returns the offset of a row in an ordered group. Can be used to sequentially&lt;br /&gt;
number rows, ordered by certain criteria.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;STDDEV (expression)&lt;br /&gt;
 Computes the standard deviation of the current row with respect to the group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;STDDEV_POP (expression)&lt;br /&gt;
 This function computes the population standard deviation and returns the&lt;br /&gt;
square root of the population variance. Its return value is same as the square root of the VAR_POP function.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;STDDEV_SAMP (expression)&lt;br /&gt;
 This function computes the cumulative sample standard deviation and returns&lt;br /&gt;
the square root of the sample variance. This function returns the same value as the square root of the VAR_SAMP function would.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;SUM(expression)&lt;br /&gt;
 This function computes the cumulative sum of expression in a group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;VAR_POP (expression)&lt;br /&gt;
 This function returns the population variance of a non-null set of numbers&lt;br /&gt;
(nulls are ignored). VAR_POP function makes the following calculation for us:&lt;br /&gt;
(SUM(expr*expr) - SUM(expr)*SUM(expr) / COUNT(expr)) / COUNT(expr)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;VAR_SAMP (expression)&lt;br /&gt;
 This function returns the sample variance of a non-null set of numbers (nulls&lt;br /&gt;
in the set are ignored). This function makes the following calculation for us:&lt;br /&gt;
(SUM(expr*expr) - SUM(expr)*SUM(expr) / COUNT(expr)) / (COUNT(expr) - 1)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;VARIANCE (expression)&lt;br /&gt;
 This function returns the variance of expression.&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
 Most used functions to improve some performance :&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
SUM, RANK, DENSE_RANK, ROW_NUMBER, LAG, LEAD, FIRST_VALUE, LAST_VALUE, NTH_VALUE&amp;lt;/ul&amp;gt;&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=SQL2008_windowing_queries&amp;diff=4917</id>
		<title>SQL2008 windowing queries</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=SQL2008_windowing_queries&amp;diff=4917"/>
		<updated>2009-03-02T14:54:21Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;strong class=&amp;quot;two&amp;quot;&amp;gt;What is SQL:2003 windowing queries?&amp;lt;/strong&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;strong&amp;gt;SQL&amp;lt;/strong&amp;gt; is a very capable language and there are very few questions that it cannot answer. However, the performance of some of these queries is not what it should be -&lt;br /&gt;
nor is the query itself easy to write in the first place. Some of the things that are hard to do in straight SQL are actually very commonly requested operations, including:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Calculate a running total - Show the cumulative salary within a department row&lt;br /&gt;
by row, with each row including a summation of the prior rows&#039; salary.&lt;br /&gt;
&amp;lt;li&amp;gt;Find percentages within a group - Show the percentage of the total salary paid&lt;br /&gt;
to an individual in a certain department. Take their salary and divide it by the sum of the salary in the department.&lt;br /&gt;
&amp;lt;li&amp;gt;Top-N queries - Find the top N highest-paid people or the top N sales by&lt;br /&gt;
region.&lt;br /&gt;
&amp;lt;li&amp;gt;Compute a moving average - Average the current row&#039;s value and the previous N&lt;br /&gt;
rows values together.&lt;br /&gt;
&amp;lt;li&amp;gt;Perform ranking queries - Show the relative rank of an individual&#039;s salary&lt;br /&gt;
within their department.&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Both the &amp;amp;quot;Top-N&amp;amp;quot; and ranking queries could perhaps be implemented by simply having a result row number be returned (after sorting). The row number can then be used to calculate positional-based info. &lt;br /&gt;
&lt;br /&gt;
Analytic functions, are designed to address these issues. They add extensions&lt;br /&gt;
to the SQL language that not only make these operations easier to code; they make them faster than could be achieved with the pure SQL approach. These extensions are currently under review by the ANSI SQL committee for inclusion in the SQL specification.&lt;br /&gt;
&lt;br /&gt;
The syntax of the analytic function is rather straightforward in appearance,&lt;br /&gt;
but looks can be deceiving.&lt;br /&gt;
It starts with:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
        FUNCTION_NAME(&amp;amp;lt;argument&amp;amp;gt;,&amp;amp;lt;argument&amp;amp;gt;,...)&lt;br /&gt;
        OVER&lt;br /&gt;
        (&amp;amp;lt;Partition-Clause&amp;amp;gt; &amp;amp;lt;Order-by-Clause&amp;amp;gt; &amp;amp;lt;Frame-Clause&amp;amp;gt;)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;The PARTITION BY clause logically breaks a single result set into N groups,&lt;br /&gt;
according to the criteria set by the partition expressions. The words &#039;partition&#039; and &#039;group&#039; are used synonymously.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;The ORDER BY clause specifies how the data is sorted within each group&lt;br /&gt;
(partition).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;The FRAME clause gives us a way to define a sliding or anchored window of&lt;br /&gt;
data, on which the analytic function will operate, within a group. This clause can be used to have the analytic function compute its value based on any arbitrary sliding or anchored window within a group.&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
This example, shows how to use the analytical function &amp;lt;strong&amp;gt;SUM&amp;lt;/strong&amp;gt; to perform a&lt;br /&gt;
cumulative sum. First, we fill some values in a table. The table is very simple and consists of the field &amp;lt;em&amp;gt;dt&amp;lt;/em&amp;gt; and &amp;lt;em&amp;gt;xy&amp;lt;/em&amp;gt; only. Note, that for a given date it is possible to insert multiple rows which is exactly what I do here. What I am interested is to extract the cumulative sum for each day in the table. That is, if I have three entries for the same date, for example 3, 4 and 5, I don&#039;t want the sum to only be 3+4+5 for each row, but 3 for the first row, 3+4 for the second row and 3+4+5 for the third row.&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
        create table sum_example (&lt;br /&gt;
                                 dt date,&lt;br /&gt;
                                 xy number&lt;br /&gt;
                                );&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
	insert into sum_example values (to_date(&#039;27.08.2001&#039;,&#039;DD.MM.YYYY&#039;),4);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;02.09.2001&#039;,&#039;DD.MM.YYYY&#039;),1);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;09.09.2001&#039;,&#039;DD.MM.YYYY&#039;),5);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;26.08.2001&#039;,&#039;DD.MM.YYYY&#039;),3);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;28.08.2001&#039;,&#039;DD.MM.YYYY&#039;),4);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;26.08.2001&#039;,&#039;DD.MM.YYYY&#039;),6);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;29.08.2001&#039;,&#039;DD.MM.YYYY&#039;),9);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;30.08.2001&#039;,&#039;DD.MM.YYYY&#039;),2);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;12.09.2001&#039;,&#039;DD.MM.YYYY&#039;),7);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;23.08.2001&#039;,&#039;DD.MM.YYYY&#039;),2);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;27.08.2001&#039;,&#039;DD.MM.YYYY&#039;),5);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;09.09.2001&#039;,&#039;DD.MM.YYYY&#039;),9);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;01.09.2001&#039;,&#039;DD.MM.YYYY&#039;),3);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;07.09.2001&#039;,&#039;DD.MM.YYYY&#039;),1);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;12.09.2001&#039;,&#039;DD.MM.YYYY&#039;),4);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;03.09.2001&#039;,&#039;DD.MM.YYYY&#039;),5);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;03.09.2001&#039;,&#039;DD.MM.YYYY&#039;),8);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;07.09.2001&#039;,&#039;DD.MM.YYYY&#039;),7);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;04.09.2001&#039;,&#039;DD.MM.YYYY&#039;),8);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;09.09.2001&#039;,&#039;DD.MM.YYYY&#039;),1);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;29.08.2001&#039;,&#039;DD.MM.YYYY&#039;),3);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;30.08.2001&#039;,&#039;DD.MM.YYYY&#039;),7);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;24.08.2001&#039;,&#039;DD.MM.YYYY&#039;),7);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;07.09.2001&#039;,&#039;DD.MM.YYYY&#039;),9);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;26.08.2001&#039;,&#039;DD.MM.YYYY&#039;),2);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;09.09.2001&#039;,&#039;DD.MM.YYYY&#039;),8);&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
        select dt,&lt;br /&gt;
               sum(xy) over (partition by trunc(dt) order by dt rows between &lt;br /&gt;
                  unbounded preceding and current row) s,&lt;br /&gt;
               xy&lt;br /&gt;
        from sum_example;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
The the analytical function:&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
        sum(xy) over (partition by trunc(dt) order by dt rows between unbounded preceding and current row)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
The select statement will return:&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
23/08/01          2          2&lt;br /&gt;
24/08/01          7          7&lt;br /&gt;
26/08/01          3          3&lt;br /&gt;
26/08/01          5          2&lt;br /&gt;
26/08/01         11          6&lt;br /&gt;
27/08/01          4          4&lt;br /&gt;
27/08/01          9          5&lt;br /&gt;
28/08/01          4          4&lt;br /&gt;
29/08/01          3          3&lt;br /&gt;
29/08/01         12          9&lt;br /&gt;
30/08/01          2          2&lt;br /&gt;
30/08/01          9          7&lt;br /&gt;
01/09/01          3          3&lt;br /&gt;
02/09/01          1          1&lt;br /&gt;
03/09/01          5          5&lt;br /&gt;
03/09/01         13          8&lt;br /&gt;
04/09/01          8          8&lt;br /&gt;
07/09/01          9          9&lt;br /&gt;
07/09/01         16          7&lt;br /&gt;
07/09/01         17          1&lt;br /&gt;
09/09/01          5          5&lt;br /&gt;
09/09/01         14          9&lt;br /&gt;
09/09/01         22          8&lt;br /&gt;
09/09/01         23          1&lt;br /&gt;
12/09/01          4          4&lt;br /&gt;
12/09/01         11          7&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
The third column correspondents to xy (the values inserted with the insert&lt;br /&gt;
into ... above). The interesting column is the second. For example on the 26th of August in 2001,&lt;br /&gt;
the first row for that date&lt;br /&gt;
is 3 (equals xy), the second is 5 (equals xy+3) and the third is 11 (equals&lt;br /&gt;
xy+3+5).&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;strong&amp;gt;A list of analytic functions used in windowing queries &amp;lt;/strong&amp;gt; : &lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;AVG (&amp;amp;lt;distinct|all&amp;amp;gt; expression )&lt;br /&gt;
Used to compute an average of an expression within a group and window.&lt;br /&gt;
Distinct may be used to find the average of the values in a group after duplicates have been removed.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;CORR (expression, expression)&lt;br /&gt;
Returns the coefficient of correlation of a pair of expressions that return&lt;br /&gt;
numbers. It is shorthand for:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;COVAR_POP(expr1, expr2) /&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;STDDEV_POP(expr1) * STDDEV_POP(expr2)).&lt;br /&gt;
Statistically speaking, a correlation is the strength of an association between&lt;br /&gt;
variables. An association between variables means that the value of one variable can be predicted, to some extent, by the value of the other. The correlation coefficient gives the strength of the association by returning a number&lt;br /&gt;
between -1 (strong inverse correlation) and 1 (strong correlation). A value of&lt;br /&gt;
0 would indicate no correlation.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;COUNT (&amp;amp;lt;distinct&amp;amp;gt; &amp;amp;lt;*&amp;amp;gt; &amp;amp;lt;expression&amp;amp;gt;)&lt;br /&gt;
This will count occurrences within a group. If you specify * or some non-null&lt;br /&gt;
constant, count will count all rows. If you specify an expression, count returns the count of non-null evaluations of expression.&lt;br /&gt;
You may use the DISTINCT modifier to count occurrences of rows in a group after&lt;br /&gt;
duplicates have been removed.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;COVAR_POP (expression, expression)&lt;br /&gt;
This returns the population covariance of a pair of expressions that return numbers.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;COVAR_SAMP (expression, expression)&lt;br /&gt;
 This returns the sample covariance of a pair of expressions that return&lt;br /&gt;
numbers.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;CUME_DIST&lt;br /&gt;
 This computes the relative position of a row in a group. CUME_DIST will always&lt;br /&gt;
return a number greater then 0 and less then or equal to 1. This number represents the &#039;position&#039; of the row in the group of N rows. In a group of three rows, the cumulate distribution values returned would be 1/3, 2/3, and 3/3 for example.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;DENSE_RANK&lt;br /&gt;
 This function computes the relative rank of each row returned from a query&lt;br /&gt;
with respect to the other rows, based on the values of the expressions in the ORDER BY clause. The data within a group is sorted by the ORDER BY clause and then a numeric ranking is assigned to each row in turn starting with 1 and&lt;br /&gt;
continuing on up. The rank is incremented every time the values of the ORDER BY&lt;br /&gt;
expressions change.&lt;br /&gt;
Rows with equal values receive the same rank (nulls are considered equal in&lt;br /&gt;
this comparison). A dense rank returns a ranking number without any gaps. This is in comparison to RANK below.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;FIRST_VALUE&lt;br /&gt;
 This simply returns the first value from a group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;LAG (expression, &amp;amp;lt;offset&amp;amp;gt;, &amp;amp;lt;default&amp;amp;gt;)&lt;br /&gt;
 LAG gives you access to other rows in a resultset without doing a self-join.&lt;br /&gt;
It allows you to treat the cursor as if it were an array in effect. You can reference rows that come before the current row in a given group. This would allow you to select &#039;the previous rows&#039; from a group along with the current&lt;br /&gt;
row. See LEAD for how to get &#039;the next rows&#039;.&lt;br /&gt;
Offset is a positive integer that defaults to 1 (the previous row). Default is&lt;br /&gt;
the value to be returned if the index is out of range of the window (for the first row in a group, the default will be returned)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;LAST_VALUE&lt;br /&gt;
 This simply returns the last value from a group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;LEAD (expression, &amp;amp;lt;offset&amp;amp;gt;, &amp;amp;lt;default&amp;amp;gt;)&lt;br /&gt;
 LEAD is the opposite of LAG. Whereas LAG gives you access to the a row preceding yours in a group - LEAD gives you access to the a row that comes after your row.&lt;br /&gt;
Offset is a positive integer that defaults to 1 (the next row). Default is the&lt;br /&gt;
value to be returned if the index is out of range of the window (for the last row in a group, the default will be returned).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;MAX(expression)&lt;br /&gt;
 Finds the maximum value of expression within a window of a group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;MIN(expression)&lt;br /&gt;
 Finds the minimum value of expression within a window of a group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;NTILE (expression)&lt;br /&gt;
 Divides a group into &#039;value of expression&#039; buckets.&lt;br /&gt;
For example; if expression = 4, then each row in the group would be assigned a&lt;br /&gt;
number from 1 to 4 putting it into a percentile. If the group had 20 rows in it, the first 5 would be assigned 1, the next 5 would be assigned 2 and so on. In the event the cardinality of the group is not evenly divisible by the&lt;br /&gt;
expression, the rows are distributed such that no percentile has more than 1&lt;br /&gt;
row more then any other percentile in that group and the lowest percentiles are the ones that will have &#039;extra&#039; rows. For example, using expression = 4 again and the number of rows = 21, percentile = 1 will have 6 rows, percentile =&lt;br /&gt;
2 will have 5, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;PERCENT_RANK&lt;br /&gt;
 This is similar to the CUME_DIST (cumulative distribution) function. For a&lt;br /&gt;
given row in a group, it calculates the rank of that row minus 1, divided by 1 less than the number of rows being evaluated in the group. This function will always return values from 0 to 1 inclusive.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;RANK&lt;br /&gt;
 This function computes the relative rank of each row returned from a query&lt;br /&gt;
with respect to the other rows, based on the values of the expressions in the ORDER BY clause. The data within a group is sorted by the ORDER BY clause and then a numeric ranking is assigned to each row in turn starting with 1 and&lt;br /&gt;
continuing on up. Rows with the same values of the ORDER BY expressions receive&lt;br /&gt;
the same rank; however, if two rows do receive the same rank the rank numbers will subsequently &#039;skip&#039;. If two rows are number 1, there will be no number 2 - rank will assign the value of 3 to the next row in the group.&lt;br /&gt;
This is in contrast to DENSE_RANK, which does not skip values.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;RATIO_TO_REPORT (expression)&lt;br /&gt;
 This function computes the value of expression / (sum(expression)) over the&lt;br /&gt;
group. This gives you the percentage of the total the current row contributes to the sum(expression).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;REGR_ xxxxxxx (expression, expression)&lt;br /&gt;
 These linear regression functions fit an ordinary-least-squares regression&lt;br /&gt;
line to a pair of expressions. There are different regression functions available for use.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;ROW_NUMBER&lt;br /&gt;
 Returns the offset of a row in an ordered group. Can be used to sequentially&lt;br /&gt;
number rows, ordered by certain criteria.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;STDDEV (expression)&lt;br /&gt;
 Computes the standard deviation of the current row with respect to the group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;STDDEV_POP (expression)&lt;br /&gt;
 This function computes the population standard deviation and returns the&lt;br /&gt;
square root of the population variance. Its return value is same as the square root of the VAR_POP function.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;STDDEV_SAMP (expression)&lt;br /&gt;
 This function computes the cumulative sample standard deviation and returns&lt;br /&gt;
the square root of the sample variance. This function returns the same value as the square root of the VAR_SAMP function would.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;SUM(expression)&lt;br /&gt;
 This function computes the cumulative sum of expression in a group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;VAR_POP (expression)&lt;br /&gt;
 This function returns the population variance of a non-null set of numbers&lt;br /&gt;
(nulls are ignored). VAR_POP function makes the following calculation for us:&lt;br /&gt;
(SUM(expr*expr) - SUM(expr)*SUM(expr) / COUNT(expr)) / COUNT(expr)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;VAR_SAMP (expression)&lt;br /&gt;
 This function returns the sample variance of a non-null set of numbers (nulls&lt;br /&gt;
in the set are ignored). This function makes the following calculation for us:&lt;br /&gt;
(SUM(expr*expr) - SUM(expr)*SUM(expr) / COUNT(expr)) / (COUNT(expr) - 1)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;VARIANCE (expression)&lt;br /&gt;
 This function returns the variance of expression.&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
 Most used functions to improve some performance :&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
SUM, RANK, DENSE_RANK, ROW_NUMBER, LAG, LEAD, FIRST_VALUE, LAST_VALUE&amp;lt;/ul&amp;gt;&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=SQL2008_windowing_queries&amp;diff=4916</id>
		<title>SQL2008 windowing queries</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=SQL2008_windowing_queries&amp;diff=4916"/>
		<updated>2009-03-02T14:52:32Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;strong class=&amp;quot;two&amp;quot;&amp;gt;What is SQL:2003 windowing queries?&amp;lt;/strong&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&amp;lt;strong&amp;gt;SQL&amp;lt;/strong&amp;gt; is a very capable language and there are very few questions that it cannot answer. However, the performance of some of these queries is not what it should be -&lt;br /&gt;
nor is the query itself easy to write in the first place. Some of the things that are hard to do in straight SQL are actually very commonly requested operations, including:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Calculate a running total - Show the cumulative salary within a department row&lt;br /&gt;
by row, with each row including a summation of the prior rows&#039; salary.&lt;br /&gt;
&amp;lt;li&amp;gt;Find percentages within a group - Show the percentage of the total salary paid&lt;br /&gt;
to an individual in a certain department. Take their salary and divide it by the sum of the salary in the department.&lt;br /&gt;
&amp;lt;li&amp;gt;Top-N queries - Find the top N highest-paid people or the top N sales by&lt;br /&gt;
region.&lt;br /&gt;
&amp;lt;li&amp;gt;Compute a moving average - Average the current row&#039;s value and the previous N&lt;br /&gt;
rows values together.&lt;br /&gt;
&amp;lt;li&amp;gt;Perform ranking queries - Show the relative rank of an individual&#039;s salary&lt;br /&gt;
within their department.&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Both the &amp;amp;quot;Top-N&amp;amp;quot; and ranking queries could perhaps be implemented by simply having a result row number be returned (after sorting). The row number can then be used to calculate positional-based info. &lt;br /&gt;
&lt;br /&gt;
Analytic functions, are designed to address these issues. They add extensions&lt;br /&gt;
to the SQL language that not only make these operations easier to code; they make them faster than could be achieved with the pure SQL approach. These extensions are currently under review by the ANSI SQL committee for inclusion in the SQL specification.&lt;br /&gt;
&lt;br /&gt;
The syntax of the analytic function is rather straightforward in appearance,&lt;br /&gt;
but looks can be deceiving.&lt;br /&gt;
It starts with:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
        FUNCTION_NAME(&amp;amp;lt;argument&amp;amp;gt;,&amp;amp;lt;argument&amp;amp;gt;,...)&lt;br /&gt;
        OVER&lt;br /&gt;
        (&amp;amp;lt;Partition-Clause&amp;amp;gt; &amp;amp;lt;Order-by-Clause&amp;amp;gt; &amp;amp;lt;Frame Clause&amp;amp;gt;)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;The PARTITION BY clause logically breaks a single result set into N groups,&lt;br /&gt;
according to the criteria set by the partition expressions. The words &#039;partition&#039; and &#039;group&#039; are used synonymously.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;The ORDER BY clause specifies how the data is sorted within each group&lt;br /&gt;
(partition).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;The WINDOWING clause gives us a way to define a sliding or anchored window of&lt;br /&gt;
data, on which the analytic function will operate, within a group. This clause can be used to have the analytic function compute its value based on any arbitrary sliding or anchored window within a group.&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
This example, shows how to use the analytical function &amp;lt;strong&amp;gt;SUM&amp;lt;/strong&amp;gt; to perform a&lt;br /&gt;
cumulative sum. First, we fill some values in a table. The table is very simple and consists of the field &amp;lt;em&amp;gt;dt&amp;lt;/em&amp;gt; and &amp;lt;em&amp;gt;xy&amp;lt;/em&amp;gt; only. Note, that for a given date it is possible to insert multiple rows which is exactly what I do here. What I am interested is to extract the cumulative sum for each day in the table. That is, if I have three entries for the same date, for example 3, 4 and 5, I don&#039;t want the sum to only be 3+4+5 for each row, but 3 for the first row, 3+4 for the second row and 3+4+5 for the third row.&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
        create table sum_example (&lt;br /&gt;
                                 dt date,&lt;br /&gt;
                                 xy number&lt;br /&gt;
                                );&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
	insert into sum_example values (to_date(&#039;27.08.2001&#039;,&#039;DD.MM.YYYY&#039;),4);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;02.09.2001&#039;,&#039;DD.MM.YYYY&#039;),1);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;09.09.2001&#039;,&#039;DD.MM.YYYY&#039;),5);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;26.08.2001&#039;,&#039;DD.MM.YYYY&#039;),3);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;28.08.2001&#039;,&#039;DD.MM.YYYY&#039;),4);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;26.08.2001&#039;,&#039;DD.MM.YYYY&#039;),6);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;29.08.2001&#039;,&#039;DD.MM.YYYY&#039;),9);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;30.08.2001&#039;,&#039;DD.MM.YYYY&#039;),2);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;12.09.2001&#039;,&#039;DD.MM.YYYY&#039;),7);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;23.08.2001&#039;,&#039;DD.MM.YYYY&#039;),2);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;27.08.2001&#039;,&#039;DD.MM.YYYY&#039;),5);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;09.09.2001&#039;,&#039;DD.MM.YYYY&#039;),9);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;01.09.2001&#039;,&#039;DD.MM.YYYY&#039;),3);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;07.09.2001&#039;,&#039;DD.MM.YYYY&#039;),1);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;12.09.2001&#039;,&#039;DD.MM.YYYY&#039;),4);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;03.09.2001&#039;,&#039;DD.MM.YYYY&#039;),5);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;03.09.2001&#039;,&#039;DD.MM.YYYY&#039;),8);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;07.09.2001&#039;,&#039;DD.MM.YYYY&#039;),7);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;04.09.2001&#039;,&#039;DD.MM.YYYY&#039;),8);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;09.09.2001&#039;,&#039;DD.MM.YYYY&#039;),1);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;29.08.2001&#039;,&#039;DD.MM.YYYY&#039;),3);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;30.08.2001&#039;,&#039;DD.MM.YYYY&#039;),7);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;24.08.2001&#039;,&#039;DD.MM.YYYY&#039;),7);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;07.09.2001&#039;,&#039;DD.MM.YYYY&#039;),9);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;26.08.2001&#039;,&#039;DD.MM.YYYY&#039;),2);&lt;br /&gt;
	insert into sum_example values (to_date(&#039;09.09.2001&#039;,&#039;DD.MM.YYYY&#039;),8);&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
        select dt,&lt;br /&gt;
               sum(xy) over (partition by trunc(dt) order by dt rows between &lt;br /&gt;
                  unbounded preceding and current row) s,&lt;br /&gt;
               xy&lt;br /&gt;
        from sum_example;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
The the analytical function:&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
        sum(xy) over (partition by trunc(dt) order by dt rows between unbounded preceding and current row)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
The select statement will return:&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
23/08/01          2          2&lt;br /&gt;
24/08/01          7          7&lt;br /&gt;
26/08/01          3          3&lt;br /&gt;
26/08/01          5          2&lt;br /&gt;
26/08/01         11          6&lt;br /&gt;
27/08/01          4          4&lt;br /&gt;
27/08/01          9          5&lt;br /&gt;
28/08/01          4          4&lt;br /&gt;
29/08/01          3          3&lt;br /&gt;
29/08/01         12          9&lt;br /&gt;
30/08/01          2          2&lt;br /&gt;
30/08/01          9          7&lt;br /&gt;
01/09/01          3          3&lt;br /&gt;
02/09/01          1          1&lt;br /&gt;
03/09/01          5          5&lt;br /&gt;
03/09/01         13          8&lt;br /&gt;
04/09/01          8          8&lt;br /&gt;
07/09/01          9          9&lt;br /&gt;
07/09/01         16          7&lt;br /&gt;
07/09/01         17          1&lt;br /&gt;
09/09/01          5          5&lt;br /&gt;
09/09/01         14          9&lt;br /&gt;
09/09/01         22          8&lt;br /&gt;
09/09/01         23          1&lt;br /&gt;
12/09/01          4          4&lt;br /&gt;
12/09/01         11          7&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
The third column correspondents to xy (the values inserted with the insert&lt;br /&gt;
into ... above). The interesting column is the second. For example on the 26th of August in 2001,&lt;br /&gt;
the first row for that date&lt;br /&gt;
is 3 (equals xy), the second is 5 (equals xy+3) and the third is 11 (equals&lt;br /&gt;
xy+3+5).&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;strong&amp;gt;A list of analytic functions used in windowing queries &amp;lt;/strong&amp;gt; : &lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;AVG (&amp;amp;lt;distinct|all&amp;amp;gt; expression )&lt;br /&gt;
Used to compute an average of an expression within a group and window.&lt;br /&gt;
Distinct may be used to find the average of the values in a group after duplicates have been removed.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;CORR (expression, expression)&lt;br /&gt;
Returns the coefficient of correlation of a pair of expressions that return&lt;br /&gt;
numbers. It is shorthand for:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;COVAR_POP(expr1, expr2) /&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;STDDEV_POP(expr1) * STDDEV_POP(expr2)).&lt;br /&gt;
Statistically speaking, a correlation is the strength of an association between&lt;br /&gt;
variables. An association between variables means that the value of one variable can be predicted, to some extent, by the value of the other. The correlation coefficient gives the strength of the association by returning a number&lt;br /&gt;
between -1 (strong inverse correlation) and 1 (strong correlation). A value of&lt;br /&gt;
0 would indicate no correlation.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;COUNT (&amp;amp;lt;distinct&amp;amp;gt; &amp;amp;lt;*&amp;amp;gt; &amp;amp;lt;expression&amp;amp;gt;)&lt;br /&gt;
This will count occurrences within a group. If you specify * or some non-null&lt;br /&gt;
constant, count will count all rows. If you specify an expression, count returns the count of non-null evaluations of expression.&lt;br /&gt;
You may use the DISTINCT modifier to count occurrences of rows in a group after&lt;br /&gt;
duplicates have been removed.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;COVAR_POP (expression, expression)&lt;br /&gt;
This returns the population covariance of a pair of expressions that return numbers.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;COVAR_SAMP (expression, expression)&lt;br /&gt;
 This returns the sample covariance of a pair of expressions that return&lt;br /&gt;
numbers.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;CUME_DIST&lt;br /&gt;
 This computes the relative position of a row in a group. CUME_DIST will always&lt;br /&gt;
return a number greater then 0 and less then or equal to 1. This number represents the &#039;position&#039; of the row in the group of N rows. In a group of three rows, the cumulate distribution values returned would be 1/3, 2/3, and 3/3 for example.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;DENSE_RANK&lt;br /&gt;
 This function computes the relative rank of each row returned from a query&lt;br /&gt;
with respect to the other rows, based on the values of the expressions in the ORDER BY clause. The data within a group is sorted by the ORDER BY clause and then a numeric ranking is assigned to each row in turn starting with 1 and&lt;br /&gt;
continuing on up. The rank is incremented every time the values of the ORDER BY&lt;br /&gt;
expressions change.&lt;br /&gt;
Rows with equal values receive the same rank (nulls are considered equal in&lt;br /&gt;
this comparison). A dense rank returns a ranking number without any gaps. This is in comparison to RANK below.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;FIRST_VALUE&lt;br /&gt;
 This simply returns the first value from a group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;LAG (expression, &amp;amp;lt;offset&amp;amp;gt;, &amp;amp;lt;default&amp;amp;gt;)&lt;br /&gt;
 LAG gives you access to other rows in a resultset without doing a self-join.&lt;br /&gt;
It allows you to treat the cursor as if it were an array in effect. You can reference rows that come before the current row in a given group. This would allow you to select &#039;the previous rows&#039; from a group along with the current&lt;br /&gt;
row. See LEAD for how to get &#039;the next rows&#039;.&lt;br /&gt;
Offset is a positive integer that defaults to 1 (the previous row). Default is&lt;br /&gt;
the value to be returned if the index is out of range of the window (for the first row in a group, the default will be returned)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;LAST_VALUE&lt;br /&gt;
 This simply returns the last value from a group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;LEAD (expression, &amp;amp;lt;offset&amp;amp;gt;, &amp;amp;lt;default&amp;amp;gt;)&lt;br /&gt;
 LEAD is the opposite of LAG. Whereas LAG gives you access to the a row preceding yours in a group - LEAD gives you access to the a row that comes after your row.&lt;br /&gt;
Offset is a positive integer that defaults to 1 (the next row). Default is the&lt;br /&gt;
value to be returned if the index is out of range of the window (for the last row in a group, the default will be returned).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;MAX(expression)&lt;br /&gt;
 Finds the maximum value of expression within a window of a group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;MIN(expression)&lt;br /&gt;
 Finds the minimum value of expression within a window of a group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;NTILE (expression)&lt;br /&gt;
 Divides a group into &#039;value of expression&#039; buckets.&lt;br /&gt;
For example; if expression = 4, then each row in the group would be assigned a&lt;br /&gt;
number from 1 to 4 putting it into a percentile. If the group had 20 rows in it, the first 5 would be assigned 1, the next 5 would be assigned 2 and so on. In the event the cardinality of the group is not evenly divisible by the&lt;br /&gt;
expression, the rows are distributed such that no percentile has more than 1&lt;br /&gt;
row more then any other percentile in that group and the lowest percentiles are the ones that will have &#039;extra&#039; rows. For example, using expression = 4 again and the number of rows = 21, percentile = 1 will have 6 rows, percentile =&lt;br /&gt;
2 will have 5, and so on.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;PERCENT_RANK&lt;br /&gt;
 This is similar to the CUME_DIST (cumulative distribution) function. For a&lt;br /&gt;
given row in a group, it calculates the rank of that row minus 1, divided by 1 less than the number of rows being evaluated in the group. This function will always return values from 0 to 1 inclusive.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;RANK&lt;br /&gt;
 This function computes the relative rank of each row returned from a query&lt;br /&gt;
with respect to the other rows, based on the values of the expressions in the ORDER BY clause. The data within a group is sorted by the ORDER BY clause and then a numeric ranking is assigned to each row in turn starting with 1 and&lt;br /&gt;
continuing on up. Rows with the same values of the ORDER BY expressions receive&lt;br /&gt;
the same rank; however, if two rows do receive the same rank the rank numbers will subsequently &#039;skip&#039;. If two rows are number 1, there will be no number 2 - rank will assign the value of 3 to the next row in the group.&lt;br /&gt;
This is in contrast to DENSE_RANK, which does not skip values.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;RATIO_TO_REPORT (expression)&lt;br /&gt;
 This function computes the value of expression / (sum(expression)) over the&lt;br /&gt;
group. This gives you the percentage of the total the current row contributes to the sum(expression).&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;REGR_ xxxxxxx (expression, expression)&lt;br /&gt;
 These linear regression functions fit an ordinary-least-squares regression&lt;br /&gt;
line to a pair of expressions. There are different regression functions available for use.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;ROW_NUMBER&lt;br /&gt;
 Returns the offset of a row in an ordered group. Can be used to sequentially&lt;br /&gt;
number rows, ordered by certain criteria.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;STDDEV (expression)&lt;br /&gt;
 Computes the standard deviation of the current row with respect to the group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;STDDEV_POP (expression)&lt;br /&gt;
 This function computes the population standard deviation and returns the&lt;br /&gt;
square root of the population variance. Its return value is same as the square root of the VAR_POP function.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;STDDEV_SAMP (expression)&lt;br /&gt;
 This function computes the cumulative sample standard deviation and returns&lt;br /&gt;
the square root of the sample variance. This function returns the same value as the square root of the VAR_SAMP function would.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;SUM(expression)&lt;br /&gt;
 This function computes the cumulative sum of expression in a group.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;VAR_POP (expression)&lt;br /&gt;
 This function returns the population variance of a non-null set of numbers&lt;br /&gt;
(nulls are ignored). VAR_POP function makes the following calculation for us:&lt;br /&gt;
(SUM(expr*expr) - SUM(expr)*SUM(expr) / COUNT(expr)) / COUNT(expr)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;VAR_SAMP (expression)&lt;br /&gt;
 This function returns the sample variance of a non-null set of numbers (nulls&lt;br /&gt;
in the set are ignored). This function makes the following calculation for us:&lt;br /&gt;
(SUM(expr*expr) - SUM(expr)*SUM(expr) / COUNT(expr)) / (COUNT(expr) - 1)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;li&amp;gt;VARIANCE (expression)&lt;br /&gt;
 This function returns the variance of expression.&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
 Most used functions to improve some performance :&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
SUM, RANK, DENSE_RANK, ROW_NUMBER, LAG, LEAD, FIRST_VALUE, LAST_VALUE&amp;lt;/ul&amp;gt;&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=CommitFest_2008-11&amp;diff=3485</id>
		<title>CommitFest 2008-11</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=CommitFest_2008-11&amp;diff=3485"/>
		<updated>2008-11-12T09:55:02Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* SQL language features */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__TOC__&lt;br /&gt;
&lt;br /&gt;
This is the page for the CommitFest starting &#039;&#039;&#039;2008 November&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Managers for this CommitFest are Josh Berkus (josh-at-agliodbs-com) and Dave Page (dpage-at-pgadmin-org).&lt;br /&gt;
&lt;br /&gt;
{{CommitFestCurrent}}&lt;br /&gt;
&lt;br /&gt;
== Pending patches ==&lt;br /&gt;
{{CommitFestSectionNew}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
=== SE-PostgreSQL and related ===&lt;br /&gt;
&lt;br /&gt;
{{patch|4863B3DA.8030209@kaigai.gr.jp|SE-PostgreSQL patches|Kaigai Kohei}}&lt;br /&gt;
{{comment|KaiGai|[[SEPostgreSQL]] is a draft of comprehensive document}}&lt;br /&gt;
{{comment|KaiGai|{{messageLink|49180B32.5030308@ak.jp.nec.com|The latest patches to be reviewed (r1206)}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20080901063855.GJ16005@tamriel.snowman.net|Column-level Permissions|Stephen Frost|status=Pending Review|reviewers=Markus Wanner}}&lt;br /&gt;
{{comment|Stephen Frost|Updated patch {{messageLink|20080902221823.GL16005@tamriel.snowman.net|here}}}}&lt;br /&gt;
{{review|48DB48AC.5010400@bluegap.ch|Markus Wanner|Awaiting updated patch.}}&lt;br /&gt;
{{comment|Stephen Frost|Updated patch, again, {{messageLink|20081102034517.GR4452@tamriel.snowman.net|here}}}}&lt;br /&gt;
{{comment|Stephen Frost|Updated patch, fixes case where unprivileged user can get row count, {{messageLink|20081102131332.GU4452@tamriel.snowman.net|here}}}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Recovery, Replication, Hot Standby ===&lt;br /&gt;
&lt;br /&gt;
{{patch|1220213074.4371.173.camel@ebony.2ndQuadrant|Infrastructure changes for recovery|status=Pending Review|Simon Riggs|reviewers=Tom Lane, Heikki Linnakangas}} &lt;br /&gt;
{{comment|sriggs| important patch for other work}}&lt;br /&gt;
{{comment|tgl|some comments {{messageLink|1905.1220895241@sss.pgh.pa.us|here}}}}&lt;br /&gt;
{{comment|tgl|updated patch {{messageLink|1221080797.3913.768.camel@ebony.2ndQuadrant|here}}, still being tested}}&lt;br /&gt;
{{comment|tgl|Simon found {{messageLink|1221725145.3913.2315.camel@ebony.2ndQuadrant|some issues}}}}&lt;br /&gt;
{{comment|tgl|{{messageLink|1222184541.4445.400.camel@ebony.2ndQuadrant|patch v7}} here}}&lt;br /&gt;
{{comment|tgl|it&#039;s still got {{messageLink|28973.1222381719@sss.pgh.pa.us|issues}}}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1222815151.4445.1397.camel@ebony.2ndQuadrant|patch v8}} here}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1223472898.4747.310.camel@ebony.2ndQuadrant|patch v9}} here, in response to {{messageLink|48EC9CC5.6060803@enterprisedb.com|Heikki&#039;s review}}}}&lt;br /&gt;
{{comment|sriggs|some issues overlooked, fixed as part of Hot Standby patch only at present}}&lt;br /&gt;
{{comment|sriggs|do we want this split out again as a separate patch for easier review?}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1225557138.3971.673.camel@ebony.2ndQuadrant|Hot Standby - queries during archive recovery|status=Pending Review|Simon Riggs}}&lt;br /&gt;
{{comment|sriggs| v5d now available, fixing all Mark&#039;s reported issues. Main parts are fully reviewable}}&lt;br /&gt;
{{comment|sriggs| Wiki contains dynamically updated list of outstanding items [[Hot_Standby]] }}&lt;br /&gt;
&lt;br /&gt;
{{patch|1223472186.4747.301.camel@ebony.2ndQuadrant|pg_stop_backup wait bug fix|Simon Riggs}}&lt;br /&gt;
{{comment|Robert Haas|sriggs extracted this from recovery infrastructure patch per {{messageLink|48EC9CC5.6060803@enterprisedb.com|Heikki&#039;s suggestion}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1220174867.4371.107.camel@ebony.2ndQuadrant|rmgr hooks and contrib/rmgr_hook|status=Waiting on dependencies|Simon Riggs}} &lt;br /&gt;
{{comment|sriggs| deferrable, if required}}&lt;br /&gt;
{{comment|tgl|I think the plan is for this to wait till &amp;quot;infrastructure&amp;quot; patch goes in}}&lt;br /&gt;
&lt;br /&gt;
{{patch|3f0b79eb0810310436w360f0afdy76ff1499b177ce0d@mail.gmail.com|Synchronous log-shipping replication|Masao Fujii|reviewers=Heikki Linnakangas, Simon Riggs}}&lt;br /&gt;
{{comment|fujii|{{messageLink|3f0b79eb0811040404r799d3170v5bb9f201000f1771@mail.gmail.com|signal handling patch v2}} here}}&lt;br /&gt;
{{comment|fujii|{{messageLink|3f0b79eb0811050617o3237130awb4aec1d3a2daacab@mail.gmail.com|walsender process patch v1}} here}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Upgrade-in-place and related issues === &lt;br /&gt;
&lt;br /&gt;
{{patch|490B7C1B.8050408@sun.com|In-place online upgrade|status=Waiting for new version|Zdenek Kotala|reviewers=Robert Haas}}&lt;br /&gt;
{{comment|Zdenek Kotala|This patch requires &amp;quot;htup and bufpage API clean up&amp;quot; and &amp;quot;HeapTuple version extension&amp;quot; patches. Git repository is [http://git.postgresql.org here] }}&lt;br /&gt;
{{review|603c8f070811022022x582a9cbdp60798a6b87910edf@mail.gmail.com|Robert Haas|preliminary comments, still need a clean diff}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48F1FC7E.1060406@sun.com|Extending pg_class info + more flexible TOAST chunk size|Zdenek Kotala|reviewers=Robert Haas|status=Waiting for new version}}&lt;br /&gt;
{{comment|tgl|seems it&#039;d be better to make TOAST chunks work like {{messageLink|490AB654.6040409@enterprisedb.com|this}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4909DFCE.1000702@sun.com|HeapTuple version extension + code cleanup|Zdenek Kotala|reviewers=Robert Haas|status=Waiting for new version}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== SQL language features ===&lt;br /&gt;
&lt;br /&gt;
{{patch|e08cc0400810270912u49a6ec83vc23984c01f368f76@mail.gmail.com|Window Functions|Hitoshi Harada|reviewers=Heikki Linnakangas, David Rowley}}&lt;br /&gt;
{{comment|Hitoshi Harada|updated patch is {{messageLink|e08cc0400810310721l22a6bb7kb6a300ce66443806@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Hitoshi Harada|updated patch is {{messageLink|e08cc0400811070746p43553f10s6bb09e98b7eafc3b@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Hitoshi Harada|updated patch is {{messageLink|e08cc0400811100548s1d31af73s888062c05c8512bd@mail.gmail.com|here}}, still some issues on {{messageLink|e08cc0400811100619w46a1b013x2051f6a8f2dad116@mail.gmail.com|ntile}} and {{messageLink|e08cc0400811100624o77744b15me1bc009b74d292c1@mail.gmail.com|nth_value}}}}&lt;br /&gt;
{{comment|Hitoshi Harada|updated patch is {{messageLink|e08cc0400811120146r3c47b320g8aac5e22c05c8829@mail.gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|162867790810170316l4eeecb0bq321dd771f8f4e661@mail.gmail.com|grouping sets|status=WIP|Pavel Stehule|reviewers=Ibrar Ahmed}}&lt;br /&gt;
{{comment|Pavel Stehule| doc and notes [[Grouping Sets]]}}&lt;br /&gt;
{{comment|Pavel Stehule| actualised patch  http://www.pgsql.cz/patches/gsets.diff.gz}}&lt;br /&gt;
&lt;br /&gt;
{{patch|162867790810260428p56d16352qa1ec5c4c5330f25c@mail.gmail.com|default values for function&#039;s parameters|Pavel Stehule|reviewers=Peter Eisentraut|status=WIP}}&lt;br /&gt;
{{comment|Pavel Stehule| fix known bugs, currently only doc should be finished}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070808070503jd7be083kcce3e16345affb08@mail.gmail.com|add columns via CREATE OR REPLACE VIEW|Robert Haas|reviewers=Bernd Helmle}}&lt;br /&gt;
{{comment|Robert Haas|some further justification of the proposed design {{messageLink|603c8f070808070956t1ab98dcdr933575eb096e4c28@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Robert Haas|questions about how to move forward {{messageLink|603c8f070810031839y7ce9a852o86effbab9fd6dd9b@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Robert Haas|a {{messageLink|482096EC.3000805@dunslane.net|similar feature request}} from Andrew Dunstan}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48EFA13C.2060407@frogthinker.org|Prepared transactions and temp tables|Emmanuel Cecchet|reviewers=Heikki Linnakangas}}&lt;br /&gt;
{{comment|tgl|new patch version {{messageLink|4914CD14.2060608@frogthinker.org|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4909726F.8000800@gmx.net|TABLE command|Peter Eisentraut|status=Waiting on author|reviewers=Unicron, Robert Haas}}&lt;br /&gt;
{{comment|Unicron|Patch {{messageLink|850603.14426.qm@web62408.mail.re1.yahoo.com|works per specification}}}}&lt;br /&gt;
{{review|603c8f070811081050k79926d12x6547ae72abaa41af@mail.gmail.com|Robert Haas|wrong non-terminal, needs doc and psql updates}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490AFC08.8040500@Sun.COM|Distinct types|Peter Eisentraut|status=Waiting on author}}&lt;br /&gt;
{{comment|Bernd Helmle|Patch needs further work regarding {{messageLink|17750.1225571886@sss.pgh.pa.us|indexing}}}}&lt;br /&gt;
{{comment|tgl|I don&#039;t think the {{messageLink|21942.1226084284@sss.pgh.pa.us|type-system behavior}} has been thought through properly}}&lt;br /&gt;
&lt;br /&gt;
{{patch|2849137C693B65CC8E86411C@imhotep.credativ.de|Automatic view update rules|status=WIP|Bernd Helmle|reviewers=Unicron,Robert Haas}}&lt;br /&gt;
{{comment|Bernd Helmle|New version with RETURNING support {{messageLink|94CF655A8D0DC7D5B4B81D8B@imhotep.credativ.de|here}}}}&lt;br /&gt;
{{comment|Wolf Wei|it can be built and executed successfully, automatic insert/update/delete on view based  on single table can work}}  &lt;br /&gt;
{{review|603c8f070811112006q906b3a6o59a66228b7fc997@mail.gmail.com|Robert Haas|fails regression tests, and a few other comments}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1225543926.8122.14.camel@huvostro|Enable pl/python to return records based on multiple OUT params|status=Waiting on author|Hannu Krosing}}&lt;br /&gt;
{{comment|Robert Haas|Hannu is {{messageLink|1225781532.7597.19.camel@huvostro|working on a new version}}}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Datatypes ===&lt;br /&gt;
&lt;br /&gt;
{{patch|20952F54-6730-49D8-99A3-1834697790B5@decibel.org|array_length|Jim C. Nasby|reviewers=Peter Eisentraut}}&lt;br /&gt;
{{comment|Robert Haas|I have {{messageLink|603c8f070811062006q4f20b2bq179d4d2ffec65690@mail.gmail.com|reimplemented this in C}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810151933p445978b3td481a5422a2aebf4@mail.gmail.com|array_agg/array_accum|Robert Haas|reviewers=Peter Eisentraut}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1225045937.4434.21.camel@localhost.localdomain|another version}} and {{messageLink|1225682527.1375.150.camel@jdavis|another one}} from Jeff Davis}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Indexes ===&lt;br /&gt;
&lt;br /&gt;
{{patch|490B07BA.6030109@sigaev.ru|GIN fast insert|Teodor Sigaev, Oleg Bartunov|reviewers=Jeff Davis}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490B3752.3010800@sigaev.ru|B-Tree emulation for GIN|status=WIP|Teodor Sigaev, Oleg Bartunov|reviewers=Jeff Davis}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081101000154.GO27872@fune|On-disk bitmap indexes|status=WIP|Gabriele Bartolini, Gianni Ciolli|reviewers=Greg Stark (more welcome!)}}&lt;br /&gt;
{{review|49130E72.1000803@sigaev.ru|Teodor Sigaev|several bugs}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Performance ===&lt;br /&gt;
&lt;br /&gt;
{{patch|6EEA43D22289484890D119821101B1DF2C1683@exchange20.mercury.ad.ubc.ca|Improve Performance of Multi-Batch Hash Join for Skewed Data Sets|Ramon Lawrence/Bryce Cutt|reviewers=Joshua Tolley}}&lt;br /&gt;
{{comment|Joshua Tolley|[http://archives.postgresql.org/pgsql-hackers/2008-11/msg00286.php] reports backend crash}}&lt;br /&gt;
{{comment|tgl|updated patch {{messageLink|1924d1180811051606w19aaf30du589e8ea10ea5534d@mail.gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|87ljw5c0lx.fsf@oxford.xeocode.com|posix_fadvise|Gregory Stark}}&lt;br /&gt;
&lt;br /&gt;
{{patch|a778a7260810280033n43f70d36x8c437eacf9a5461e@mail.gmail.com|Proposal of PITR performance improvement|Koichi Suzuki|reviewers=Simon Riggs}}&lt;br /&gt;
&lt;br /&gt;
{{patch|36e682920811021349h7202bdecpd7a45c8a8038465e@mail.gmail.com|Hash Join-Filter Pruning using Bloom Filters|status=WIP|Jonah Harris|reviewers=Kurt Harriman}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Improving admin experience ===&lt;br /&gt;
&lt;br /&gt;
{{patch|4905AE17.7090305@enterprisedb.com|Visibility map, partial vacuums|status=WIP|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081029183248.GE4331@alvh.no-ip.org|Block-level CRC checks|Alvaro Herrera|status=WIP}}&lt;br /&gt;
{{comment|alvherre|{{messageLink|20081107191140.GE5507@alvh.no-ip.org|updated patch}} here}}&lt;br /&gt;
&lt;br /&gt;
{{patch|c2ee6dbd0810100553gd328275ue2eb6e14bee70a8@mail.gmail.com|adding VERBOSE option to CLUSTER|Jim Cox|reviewers=Peter Eisentraut}}&lt;br /&gt;
&lt;br /&gt;
{{patch|a301bfd90810310750pf108c69x36499546f406650f@mail.gmail.com|Auto Partitioning Patch|Nikhil Sontakke|reviewers=Jaime Casanova}}&lt;br /&gt;
{{comment|jcasanov|some comments {{messageLink|3073cc9b0811052047o4ebe24b4vd0ab24fd3095d342@mail.gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1223379173.4747.145.camel@ebony.2ndQuadrant|Reducing some DDL Locks to ShareLock|status=Waiting on author|Simon Riggs|reviewers=Tom Lane}} &lt;br /&gt;
{{comment|tgl|{{messageLink|1223404726.4747.249.camel@ebony.2ndQuadrant|v6 patch here}}}}&lt;br /&gt;
{{comment|sriggs|agreed rework to implement pg_domain constraint, but the main patch still needs review}}&lt;br /&gt;
{{comment|tgl|I think we&#039;d decided to pass on the pg_constraint restructuring, at least for now}}&lt;br /&gt;
{{comment|tgl|partially applied, what&#039;s left is {{messageLink|17459.1226279911@sss.pgh.pa.us|here}}}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Connection management ===&lt;br /&gt;
&lt;br /&gt;
{{patch|48FC7E84.3080702@hagander.net|SSL cleanups/hostname verification|Magnus Hagander|reviewers=Alex Hunsaker}}&lt;br /&gt;
{{comment|Magnus|{{messageLink|491985B1.3090300@hagander.net|Updated patch}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49009D67.4040202@hagander.net|clientcert option for pg_hba|Magnus Hagander|reviewers=Unicron}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49076F39.1080502@hagander.net|regexp support in usermaps|Magnus Hagander|reviewers=Gianni Colli}}&lt;br /&gt;
{{comment|Magnus|{{messageLink|49198FA5.6020206@hagander.net|Updated patch}}}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Contrib modules ===&lt;br /&gt;
&lt;br /&gt;
{{patch|20081106171139.8D21.52131E4D@oss.ntt.co.jp|contrib infrastructures|Martin Pihlak, Takahiro Itagaki|reviewers=Jeff Davis, Matthew Wetmore}}&lt;br /&gt;
{{comment|Itagaki|contains {{messageLink|490A00A8.7050708@gmail.com|QueryDesc}}, {{messageLink|20081009165157.9BE4.52131E4D@oss.ntt.co.jp|explain}} and {{messageLink|20081027171917.ADD6.52131E4D@oss.ntt.co.jp|hooks}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081009165157.9BE4.52131E4D@oss.ntt.co.jp|contrib/auto_explain|status=Ready for committer|Takahiro Itagaki|reviewers=Jeff Davis}}&lt;br /&gt;
{{comment|Itagaki|{{messageLink|20081110173232.7F2B.52131E4D@oss.ntt.co.jp|latest patch version from author}}}}&lt;br /&gt;
{{comment|Jeff|{{messageLink|1226426084.3002.76.camel@jdavis|minor documentation edits by reviewer}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081011172450.3402.52131E4D@oss.ntt.co.jp|contrib/pg_stat_statements|Takahiro Itagaki|reviewers=Matthew Wetmore}}&lt;br /&gt;
{{comment|Itagaki|{{messageLink|20081027171917.ADD6.52131E4D@oss.ntt.co.jp|latest patch versions}}}}&lt;br /&gt;
{{comment|Itagaki|{{messageLink|1d709ecc0811011343lf65f58fjb2e96194f4c2ecc5@mail.gmail.com|comments}} from Vladimir}}&lt;br /&gt;
&lt;br /&gt;
{{patch|e4ccc24e0810222010p12bae2f4xa3a11cb2bc51bd89@mail.gmail.com|pg_standby support for compressed segments|Charles Duffy|reviewers=Simon Riggs}}&lt;br /&gt;
{{comment|Simon Riggs|Deferring review for a few weeks until we get a better picture of streaming replication requirements for 8.4}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.GSO.4.64.0811012101220.17619@westnet.com|Simple postgresql.conf wizard|Greg Smith|reviewers=Josh Berkus}}&lt;br /&gt;
{{comment|Greg Smith|{{messageLink|Pine.GSO.4.64.0811090226060.26272@westnet.com|Updated V2}}}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
=== Clients ===&lt;br /&gt;
&lt;br /&gt;
{{patch|200810271936.m9RJaGW09544@momjian.us|libpq callback unregistration|Bruce Momjian|reviewers=Magnus Hagander}}&lt;br /&gt;
{{comment|Magnus|Needs more work, comments {{messageLink|490EEF2D.2050703@hagander.net|here}}}}&lt;br /&gt;
{{comment|alvherre|Bruce posted a {{messageLink|200811050502.mA552TJ20677@momjian.us|new version}}, but it still {{messageLink|20081107201029.GF5507@alvh.no-ip.org|needs some work}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48F04B7C.3080303@benedekl.tvnetwork.hu|pg_dump roles support|Benedek Laszlo|reviewers=Ibrar Ahmed|Status=Waiting for Author}}&lt;br /&gt;
{{comment|alvherre|there&#039;s an {{messageLink|4912FA4E.1090000@benedekl.tvnetwork.hu|updated patch}}, and some extra {{messageLink|20081107202000.GG5507@alvh.no-ip.org|comments}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490878AC.1@dunslane.net|parallel restore|status=WIP|Andrew Dunstan|reviewers=Kenneth Marshall}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
{{patch|03c301c91737$be5a2a30$0e01a8c0@IBMC9A0F63B40D|Solve a problem of LC_TIME of windows|Hiroshi Saito}}&lt;br /&gt;
{{comment|tgl|updated version {{messageLink|2C940A1672E743439355545C5DB15786@HIRO57887DE653|here}}}}&lt;br /&gt;
{{comment|itagaki|comments and updated version {{messageLink|20081104094301.7EE8.52131E4D@oss.ntt.co.jp|here}}}}&lt;br /&gt;
{{comment|jcasanov|Itagaki sends a new version of the patch {{messageLink|20081111152112.B605.52131E4D@oss.ntt.co.jp|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|BLU110-W38CE0A22D467A8C3D9736CFF540@phx.gbl|Support PLUGINS lines in Makefiles, similar to MODULES|Asif Naeem}}&lt;br /&gt;
{{comment|Dave Page|This doesn&#039;t work with the edb-debugger plugin, which is the only such plugin around AFAIK. It needs to ignore comments on the PLUGINS line, and handle multiple targets (plugin_debugger, pldbgapi, targetinfo etc). Not sure if we want that complexity though.}}&lt;br /&gt;
{{comment|Heikki|Unix-makefile version: {{messageLink|BLU110-W57823CEB7DC113354471EFF3B0@phx.gbl|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48F53EC0.3020004@timbira.com|autovacuum and reloption|status=Waiting on author|Euler Taveira de Oliveira|reviewers=Alvaro Herrera}}&lt;br /&gt;
{{comment|Robert Haas|author is {{messageLink|491984F9.8070203@timbira.com|working on a new version}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49097338.2070700@gmail.com|SQL/MED compatible connection manager|Martin Pihlak|status=WIP}}&lt;br /&gt;
{{comment|Martin Pihlak|Updated patch {{messageLink|49142C02.8020706@gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081029164000.GL27466@fetter.org|pre-MED|David Fetter|reviewers=Alex Hunsaker|status=Waiting on author}}&lt;br /&gt;
{{comment|David Fetter|Updated patch {{messageLink|20081031144852.GF15545@fetter.org|here}}}}&lt;br /&gt;
{{review|34d269d40811031902p1d73d177w9f2e721ae169e8be@mail.gmail.com|alexhun|few questions and tgl had some constructive {{messageLink|24867.1225819435@sss.pgh.pa.us|comments}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|f205bb120810280833x340324d3m19a4f8aa65d822b@mail.gmail.com|FAQ_Solaris 1.28 to spanish|Emanuel CALVO FRANCO|reviewers=Peter Eisentraut}}&lt;br /&gt;
&lt;br /&gt;
{{CommitFestEndSection}}&lt;br /&gt;
&lt;br /&gt;
== Committed patches ==&lt;br /&gt;
{{CommitFestSectionNew}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20080803.114711.73374027.t-ishii@sraoss.co.jp|Common Table Expressions|Yoshiyuki Asaba|status=Committed 2008-10-04|reviewers=Jeff Davis}}&lt;br /&gt;
{{comment|David Fetter|README is {{messageLink|20080818.163852.105172778.t-ishii@sraoss.co.jp|here.}}}}&lt;br /&gt;
{{comment|David Fetter|Git repository is [http://git.postgresql.org/git/~davidfetter/cte/.git here.]}}&lt;br /&gt;
{{comment|David Fetter|[[CTEReadme]]}}&lt;br /&gt;
{{comment|David Fetter|[[CTESQLStandard| Fair Use from the draft SQL:2008 standard (WIP)]]}}&lt;br /&gt;
{{review|13449.1221589943@sss.pgh.pa.us|tgl|needs a good bit of work yet}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.GSO.4.64.0809152349440.19910@westnet.com|Add default_val to pg_settings|status=Committed 2008-10-06|Greg Smith|reviewers=Simon Riggs,Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081016102603.897D.52131E4D@oss.ntt.co.jp|Noisy _dosmaperror|status=Committed 2008-10-16|Takahiro Itagaki|reviewers=Tom Lane}}&lt;br /&gt;
&lt;br /&gt;
{{patch|b4e5ce320810151918g2acf69ebh9f80f4f2e1c203a0@mail.gmail.com|Memory leak on hashed agg rescan|status=Committed 2008-10-16|Neil Conway|reviewers=Tom Lane}}&lt;br /&gt;
{{review|10455.1224160007@sss.pgh.pa.us|Tom Lane|move some logic to separate function}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1223383838.4747.154.camel@ebony.2ndQuadrant|Atomic subtransaction commit|status=Committed 2008-10-20|Simon Riggs|reviewers=Alvaro Herrera}} &lt;br /&gt;
&lt;br /&gt;
{{patch|3327.1224535092@sss.pgh.pa.us|add placeholder variables to planner|status=Committed 2008-10-22|Tom Lane}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48E271C5.7010907@hagander.net|pg_hba options parsing|status=Committed 2008-10-23|Magnus Hagander|reviewers=Bruce Momjian}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|48F0DE8B.8030004@hagander.net|updated patch}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48FC3994.8040809@hagander.net|libpq ssl -&amp;gt; clear fallback looses error messages|status=Committed 2008-10-27|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905D22D.9040001@hagander.net|better hba parsing error messages|status=Committed 2008-10-27|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905A1DE.5030102@hagander.net|remove crypt authentication|status=Committed 2008-10-28|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905F515.3020208@gmx.net|Unicode escapes in literals|status=Committed 2008-10-29|Peter Eisentraut}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490A138E.80100@enterprisedb.com|User defined I/O conversion casts|status=Committed 2008-10-31|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49085327.5010608@enterprisedb.com|Updating FSM on recovery|status=Committed 2008-10-31|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.BSO.4.64.0810271955030.28764@leary.csoft.net|use new heap_(form/deform/modify)_tuple API|Kris Jurka|reviewers=Zdenek Kotala|status=Committed 2008-11-01}}&lt;br /&gt;
{{comment|Zdenek Kotala| It seems OK. Needs apply also {{messageLink|Pine.BSO.4.64.0810281721500.6833@leary.csoft.net|pfree patch.}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.BSO.4.64.0810281622240.9851@leary.csoft.net|don&#039;t use MAKE_PTR/OFFSET for shmem pointers|Kris Jurka|reviewers=Tom Lane|status=Committed 2008-11-02}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48C181D4.8030807@gmail.com|reducing statistics write overhead|Martin Pihlak|reviewers=Tom Lane|status=Committed 2008-11-02}}&lt;br /&gt;
{{comment|Martin Pihlak|Latest patch {{messageLink|48C594D8.6050504@gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|37ed240d0809030015u73b65b66v70fd76741317c6f5@mail.gmail.com|pg_typeof()|Brendan Jurd|reviewers=Kurt Harriman|status=Committed 2008-11-03}}&lt;br /&gt;
{{comment|Kurt Harriman|{{messageLink|http://archives.postgresql.org/pgsql-hackers/2008-11/msg00080.php|Updated patch}} is ready to commit if there is no objection}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.BSO.4.64.0810081931240.11647@leary.csoft.net|Fixes for psql describeOneTableDetails|Kris Jurka|reviewers=Tom Lane|status=Committed 2008-11-03}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48E22CF5.4050503@sun.com|PageGetTempPage cleanup |Zdenek Kotala|reviewers=Tom Lane|status=Committed 2008-11-03}}&lt;br /&gt;
{{comment|Zdenek Kotala|Original discussion {{messageLink|4938.1217862947@sss.pgh.pa.us|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810092009s1312d30bxc854cdfb5d9fed7e@mail.gmail.com|Allow the UUID type to accept non-standard formats|Robert Haas|reviewers=Peter Eisentraut|status=Committed 2008-11-03}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810101937n776c1e7cvd6a12345b0bbda28@mail.gmail.com|array_ndims|Robert Haas|reviewers=Peter Eisentraut|status=Committed 2008-11-04}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810282045g7fa6bdf9p53f03114d49643d7@mail.gmail.com|bulk inserts - keep most recent page pinned|Robert Haas|reviewers=Tom Lane|status=Committed 2008-11-06}}&lt;br /&gt;
{{comment|Robert Haas|based on work by Simon Riggs: [http://archives.postgresql.org/pgsql-hackers/2008-02/msg01080.php original idea],[http://archives.postgresql.org/pgsql-patches/2008-02/msg00140.php original patch], [http://archives.postgresql.org/pgsql-patches/2008-02/msg00154.php Tom Lane&#039;s comments]}}&lt;br /&gt;
{{comment|Robert Haas|Tom&#039;s comments on my [http://archives.postgresql.org/pgsql-hackers/2008-10/msg01276.php design proposal] are {{messageLink|17996.1225049097@sss.pgh.pa.us|here}}}}&lt;br /&gt;
{{comment|Robert Haas|patch {{messageLink|603c8f070811011023n202aea33w4da13b7d14f74134@mail.gmail.com|v2}}, adjusting for Heikki&#039;s changes to the ReadBuffer interface}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490394B7.6090503@lelarge.info|ALTER DATABASE SET TABLESPACE Statement|Guillaume Lelarge|reviewers=Bernd Helmle|status=Committed 2008-11-07}}&lt;br /&gt;
{{comment|Bernd Helmle|Syntax discussion and updated version {{messageLink|C0F6602797884925406AB88F@imhotep.credativ.de|here}}}}&lt;br /&gt;
{{comment|Guillaume Lelarge|Updated version with SET syntax {{messageLink|4910E46E.4010000@lelarge.info|here}}}}&lt;br /&gt;
{{comment|Bernd Helmle|Updated version from Guillaume {{messageLink|4912C88A.2070808@lelarge.info|here}}}}&lt;br /&gt;
{{comment|Guillaume Lelarge|Updated version {{messageLink|49140181.3000903@lelarge.info|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|0BD2E4E9-AF5A-4B4F-B546-027424EE8FAD@kineticode.com|Tests citext casts|David Wheeler|reviewers=&lt;br /&gt;
Kenneth Marshall|status=Committed 2008-11-07}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48D15471.6080305@cheapcomplexdevices.com|SQL Standard Interval output and IntervalStyle GUC|Ron Mayer|status=Committed 2008-11-08|reviewers=Brendan Jurd}}&lt;br /&gt;
{{comment|Ron Mayer|Early updates {{messageLink|48D52E48.406@cheapcomplexdevices.com|here}},   {{messageLink|48E49BDC.4090402@cheapcomplexdevices.com|here}}, and [http://0ape.com/postgres_interval_patches/ here]. Mostly related to GUC changes.}}&lt;br /&gt;
{{review|37ed240d0811032122u56db1959h91f53bbb9733c90d@mail.gmail.com|BJ|Bug in output, stylistic suggestions}}&lt;br /&gt;
{{comment|the mailing list|Feedback from {{messageLink|19477.1225814409@sss.pgh.pa.us|Tom L}} and {{messageLink|49101C94.EE98.0025.0@wicourts.gov|Kevin G}} about mixed-sign intervals}}&lt;br /&gt;
{{comment|Ron Mayer|Updated patch {{messageLink|4910B1DB.4000000.cheapcomplexdevices@com|here}} to fix -12:01:-30 bug and style suggestions from the review and to attempt to address feedback about mixed-sign intervals with doc updates.}}&lt;br /&gt;
{{review|37ed240d0811042102q78df5b86t2ff2092a75d371d7@mail.gmail.com|BJ|One last typo in docs but otherwise all good; review complete}}&lt;br /&gt;
{{review|28915.1226109473@sss.pgh.pa.us|Tom L|Tom pointed out issues with pg_dump and restore into databases with a different interval style}}&lt;br /&gt;
{{comment|Ron Mayer|{{messageLink|4915AC0A.9070608@cheapcomplexdevices.com|Speculating}} if an analogy with standard_conforming_strings applies to how we can handle dump/restore.}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48E4A30C.3000503@cheapcomplexdevices.com|status=Committed 2008-11-10|ISO 8601 interval literal input and output|Ron Mayer|reviewers=Brendan Jurd}}&lt;br /&gt;
{{comment|Ron Mayer|The initial (2003) version of this patch along with a thread which explains the feature a bit more can be found [http://archives.postgresql.org/pgsql-patches/2003-09/msg00103.php here].}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|490BA342.7010300@cheapcomplexdevices.com|latest version}}}}&lt;br /&gt;
{{review|37ed240d0811050750v11726fd1of441646f87b583da@mail.gmail.com|BJ|Code style and documentation suggestions}}&lt;br /&gt;
{{comment|Ron Mayer|Update here [http://0ape.com/postgres_interval_patches/ here] that fixes style &amp;amp; docs; as well as a bug where the ISO8601 spec wasn&#039;t quite followed (an optional field was treated as required by previous patches).}}&lt;br /&gt;
{{review|37ed240d0811062058n752c3880kb04feb85e355b524@mail.gmail.com|BJ|Query behaviour of &#039;P0001&#039;, final doc cleanup suggestions}}&lt;br /&gt;
{{comment|Ron Mayer|Update here [http://0ape.com/postgres_interval_patches/ here] that fixes &#039;P0001&#039; and updated docs.}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48CEDE68.7090501@cheapcomplexdevices.com|Interval rounding consistency|Ron Mayer|status=Committed 2008-11-11|reviewers=Brendan Jurd}}&lt;br /&gt;
{{comment|Ron Mayer|Patch 3 [http://0ape.com/postgres_interval_patches/ here] refactors the interval code to remove much of the copy&amp;amp;paste in DecodeInterval and EncodeInterval with the side effect of making interval rounding more consistent between styles.  This patch applies on top of the IntervalStyle patch and the ISO 8601 Interval patch.}}&lt;br /&gt;
{{review|37ed240d0811101214l4d4427d8jcdf64486fd254db9@mail.gmail.com|BJ|Code style cleanups, a couple queries}}&lt;br /&gt;
&lt;br /&gt;
{{CommitFestEndSection}}&lt;br /&gt;
&lt;br /&gt;
== Returned with Feedback ==&lt;br /&gt;
{{CommitFestSectionNew}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1225010283.21241.33.camel@localhost.localdomain|new correlation metric|Jeff Davis|reviewers=Brendan Jurd|status=Pending rework}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49086E4C.9030602@sun.com|htup and bufpage API clean up|Zdenek Kotala|reviewers=Robert Haas|status=Needs different approach}}&lt;br /&gt;
{{comment|Zdenek Kotala|New version is {{messageLink|490875FA.4020709@sun.com|here}}}}&lt;br /&gt;
{{review|603c8f070811031822q7d3b33f7x8576b7028f498cc4@mail.gmail.com|Robert Haas|proposed API seems too costly and fragile}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4909B326.507@enterprisedb.com|Optimizing COPY with memchr()|Heikki Linnakangas|status=WIP|reviewers=Robert Haas}}&lt;br /&gt;
{{comment|tgl|does this really need any more review at this point?}}&lt;br /&gt;
{{comment|Robert Haas|asked author for {{messageLink|603c8f070811081745v410d2ff5o4bd107d7fbb440f3@mail.gmail.com|a status update}}}}&lt;br /&gt;
{{comment|Robert Haas|will {{messageLink|491A1266.9090305@enterprisedb.com|not be ready for 8.4}}}}&lt;br /&gt;
&lt;br /&gt;
{{CommitFestEndSection}}&lt;br /&gt;
&lt;br /&gt;
== Round Robin Reviewers ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; cellspacing=&amp;quot;0&amp;quot; style=&amp;quot;width: 60%; border-collapse: collapse; border: 1px solid #ccc; font-size: 90%;&amp;quot;&lt;br /&gt;
|- style=&amp;quot;background: #eee;&amp;quot;&lt;br /&gt;
! width=&amp;quot;30%&amp;quot; | Name&lt;br /&gt;
!Status&lt;br /&gt;
!Reviewing&lt;br /&gt;
!Completed&lt;br /&gt;
|-&lt;br /&gt;
|Brendan Jurd || Available || 0 || 4&lt;br /&gt;
|-&lt;br /&gt;
|Jaime Casanova || Available || 1 || 1&lt;br /&gt;
|-&lt;br /&gt;
|Stephen Frost || Available 11/15 || 0 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Jeff Davis || Available || 2 || 1&lt;br /&gt;
|-&lt;br /&gt;
|Greg Stark || Unknown || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Abhijit Menon-Sen || Unknown || 0 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Alex Hunsaker || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Markus Wanner || Cherry-picking || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Ibrar Ahmed || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|D&#039;Arcy Cain || Unknown || 0 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Kenneth Marshall || Available || 1 || 1&lt;br /&gt;
|-&lt;br /&gt;
|Robert Haas || Available || 0 || 5&lt;br /&gt;
|-&lt;br /&gt;
|Matthew Wetmore || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Gianni Colli || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|&amp;quot;Unicron&amp;quot; || Available || 1 || 2&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=CommitFest_2008-11&amp;diff=3453</id>
		<title>CommitFest 2008-11</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=CommitFest_2008-11&amp;diff=3453"/>
		<updated>2008-11-10T14:42:19Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* SQL language features */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__TOC__&lt;br /&gt;
&lt;br /&gt;
This is the page for the CommitFest starting &#039;&#039;&#039;2008 November&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Managers for this CommitFest are Josh Berkus (josh-at-agliodbs-com) and Dave Page (dpage-at-pgadmin-org).&lt;br /&gt;
&lt;br /&gt;
{{CommitFestCurrent}}&lt;br /&gt;
&lt;br /&gt;
== Pending patches ==&lt;br /&gt;
{{CommitFestSectionNew}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
=== SE-PostgreSQL and related ===&lt;br /&gt;
&lt;br /&gt;
{{patch|4863B3DA.8030209@kaigai.gr.jp|SE-PostgreSQL patches|Kaigai Kohei}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|48F71E36.9010203@ak.jp.nec.com|latest version}}, now with 6 patches}}&lt;br /&gt;
{{comment|KaiGai|[[SEPostgreSQL]] is a draft of comprehensive document}}&lt;br /&gt;
{{comment|KaiGai|{{messageLink|49180B32.5030308@ak.jp.nec.com|The latest patches to be reviewed (r1206)}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20080901063855.GJ16005@tamriel.snowman.net|Column-level Permissions|Stephen Frost|status=Pending Review|reviewers=Markus Wanner}}&lt;br /&gt;
{{comment|Stephen Frost|Updated patch {{messageLink|20080902221823.GL16005@tamriel.snowman.net|here}}}}&lt;br /&gt;
{{review|48DB48AC.5010400@bluegap.ch|Markus Wanner|Awaiting updated patch.}}&lt;br /&gt;
{{comment|Stephen Frost|Updated patch, again, {{messageLink|20081102034517.GR4452@tamriel.snowman.net|here}}}}&lt;br /&gt;
{{comment|Stephen Frost|Updated patch, fixes case where unprivileged user can get row count, {{messageLink|20081102131332.GU4452@tamriel.snowman.net|here}}}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Recovery, Replication, Hot Standby ===&lt;br /&gt;
&lt;br /&gt;
{{patch|1220213074.4371.173.camel@ebony.2ndQuadrant|Infrastructure changes for recovery|status=Pending Review|Simon Riggs|reviewers=Tom Lane, Heikki Linnakangas}} &lt;br /&gt;
{{comment|sriggs| important patch for other work}}&lt;br /&gt;
{{comment|tgl|some comments {{messageLink|1905.1220895241@sss.pgh.pa.us|here}}}}&lt;br /&gt;
{{comment|tgl|updated patch {{messageLink|1221080797.3913.768.camel@ebony.2ndQuadrant|here}}, still being tested}}&lt;br /&gt;
{{comment|tgl|Simon found {{messageLink|1221725145.3913.2315.camel@ebony.2ndQuadrant|some issues}}}}&lt;br /&gt;
{{comment|tgl|{{messageLink|1222184541.4445.400.camel@ebony.2ndQuadrant|patch v7}} here}}&lt;br /&gt;
{{comment|tgl|it&#039;s still got {{messageLink|28973.1222381719@sss.pgh.pa.us|issues}}}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1222815151.4445.1397.camel@ebony.2ndQuadrant|patch v8}} here}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1223472898.4747.310.camel@ebony.2ndQuadrant|patch v9}} here, in response to {{messageLink|48EC9CC5.6060803@enterprisedb.com|Heikki&#039;s review}}}}&lt;br /&gt;
{{comment|sriggs|some issues overlooked, fixed as part of Hot Standby patch only at present}}&lt;br /&gt;
{{comment|sriggs|do we want this split out again as a separate patch for easier review?}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1225557138.3971.673.camel@ebony.2ndQuadrant|Hot Standby - queries during archive recovery|status=Pending Review|Simon Riggs}}&lt;br /&gt;
{{comment|sriggs| v5d now available, fixing all Mark&#039;s reported issues. Main parts are fully reviewable}}&lt;br /&gt;
{{comment|sriggs| Wiki contains dynamically updated list of outstanding items [[Hot_Standby]] }}&lt;br /&gt;
&lt;br /&gt;
{{patch|1223472186.4747.301.camel@ebony.2ndQuadrant|pg_stop_backup wait bug fix|Simon Riggs}}&lt;br /&gt;
{{comment|Robert Haas|sriggs extracted this from recovery infrastructure patch per {{messageLink|48EC9CC5.6060803@enterprisedb.com|Heikki&#039;s suggestion}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1220174867.4371.107.camel@ebony.2ndQuadrant|rmgr hooks and contrib/rmgr_hook|status=Waiting on dependencies|Simon Riggs}} &lt;br /&gt;
{{comment|sriggs| deferrable, if required}}&lt;br /&gt;
{{comment|tgl|I think the plan is for this to wait till &amp;quot;infrastructure&amp;quot; patch goes in}}&lt;br /&gt;
&lt;br /&gt;
{{patch|3f0b79eb0810310436w360f0afdy76ff1499b177ce0d@mail.gmail.com|Synchronous log-shipping replication|Masao Fujii|reviewers=Heikki Linnakangas, Simon Riggs}}&lt;br /&gt;
{{comment|fujii|{{messageLink|3f0b79eb0811040404r799d3170v5bb9f201000f1771@mail.gmail.com|signal handling patch v2}} here}}&lt;br /&gt;
{{comment|fujii|{{messageLink|3f0b79eb0811050617o3237130awb4aec1d3a2daacab@mail.gmail.com|walsender process patch v1}} here}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Upgrade-in-place and related issues === &lt;br /&gt;
&lt;br /&gt;
{{patch|490B7C1B.8050408@sun.com|In-place online upgrade|status=Waiting for new version|Zdenek Kotala|reviewers=Robert Haas}}&lt;br /&gt;
{{comment|Zdenek Kotala|This patch requires &amp;quot;htup and bufpage API clean up&amp;quot; and &amp;quot;HeapTuple version extension&amp;quot; patches. Git repository is [http://git.postgresql.org here] }}&lt;br /&gt;
{{review|603c8f070811022022x582a9cbdp60798a6b87910edf@mail.gmail.com|Robert Haas|preliminary comments, still need a clean diff}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48F1FC7E.1060406@sun.com|Extending pg_class info + more flexible TOAST chunk size|Zdenek Kotala|reviewers=Robert Haas|status=Waiting for new version}}&lt;br /&gt;
{{comment|tgl|seems it&#039;d be better to make TOAST chunks work like {{messageLink|490AB654.6040409@enterprisedb.com|this}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4909DFCE.1000702@sun.com|HeapTuple version extension + code cleanup|Zdenek Kotala|reviewers=Robert Haas|status=Waiting for new version}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== SQL language features ===&lt;br /&gt;
&lt;br /&gt;
{{patch|e08cc0400810270912u49a6ec83vc23984c01f368f76@mail.gmail.com|Window Functions|Hitoshi Harada|reviewers=Heikki Linnakangas, David Rowley}}&lt;br /&gt;
{{comment|Hitoshi Harada|updated patch is {{messageLink|e08cc0400810310721l22a6bb7kb6a300ce66443806@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Hitoshi Harada|updated patch is {{messageLink|e08cc0400811070746p43553f10s6bb09e98b7eafc3b@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Hitoshi Harada|updated patch is {{messageLink|e08cc0400811100548s1d31af73s888062c05c8512bd@mail.gmail.com|here}}, still some issues on {{messageLink|e08cc0400811100619w46a1b013x2051f6a8f2dad116@mail.gmail.com|ntile}} and {{messageLink|e08cc0400811100624o77744b15me1bc009b74d292c1@mail.gmail.com|nth_value}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|162867790810170316l4eeecb0bq321dd771f8f4e661@mail.gmail.com|grouping sets|status=WIP|Pavel Stehule|reviewers=Ibrar Ahmed}}&lt;br /&gt;
{{comment|Pavel Stehule| doc and notes [[Grouping Sets]]}}&lt;br /&gt;
&lt;br /&gt;
{{patch|162867790810260428p56d16352qa1ec5c4c5330f25c@mail.gmail.com|default values for function&#039;s parameters|Pavel Stehule|reviewers=Peter Eisentraut|status=WIP}}&lt;br /&gt;
{{comment|Pavel Stehule| fix known bugs, currently only doc should be finished}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070808070503jd7be083kcce3e16345affb08@mail.gmail.com|add columns via CREATE OR REPLACE VIEW|Robert Haas|reviewers=Bernd Helmle}}&lt;br /&gt;
{{comment|Robert Haas|some further justification of the proposed design {{messageLink|603c8f070808070956t1ab98dcdr933575eb096e4c28@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Robert Haas|questions about how to move forward {{messageLink|603c8f070810031839y7ce9a852o86effbab9fd6dd9b@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Robert Haas|a {{messageLink|482096EC.3000805@dunslane.net|similar feature request}} from Andrew Dunstan}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48EFA13C.2060407@frogthinker.org|Prepared transactions and temp tables|Emmanuel Cecchet|reviewers=Heikki Linnakangas}}&lt;br /&gt;
{{comment|tgl|new patch version {{messageLink|4914CD14.2060608@frogthinker.org|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4909726F.8000800@gmx.net|TABLE command|Peter Eisentraut|status=Waiting on author|reviewers=Unicron, Robert Haas}}&lt;br /&gt;
{{comment|Unicron|Patch {{messageLink|850603.14426.qm@web62408.mail.re1.yahoo.com|works per specification}}}}&lt;br /&gt;
{{review|603c8f070811081050k79926d12x6547ae72abaa41af@mail.gmail.com|Robert Haas|wrong non-terminal, needs doc and psql updates}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490AFC08.8040500@Sun.COM|Distinct types|Peter Eisentraut|status=Waiting on author}}&lt;br /&gt;
{{comment|Bernd Helmle|Patch needs further work regarding {{messageLink|17750.1225571886@sss.pgh.pa.us|indexing}}}}&lt;br /&gt;
{{comment|tgl|I don&#039;t think the {{messageLink|21942.1226084284@sss.pgh.pa.us|type-system behavior}} has been thought through properly}}&lt;br /&gt;
&lt;br /&gt;
{{patch|2849137C693B65CC8E86411C@imhotep.credativ.de|Automatic view update rules|status=WIP|Bernd Helmle|reviewers=Unicron}}&lt;br /&gt;
{{comment|Bernd Helmle|New version with RETURNING support {{messageLink|94CF655A8D0DC7D5B4B81D8B@imhotep.credativ.de|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1225543926.8122.14.camel@huvostro|Enable pl/python to return records based on multiple OUT params|status=Waiting on author|Hannu Krosing}}&lt;br /&gt;
{{comment|Robert Haas|Hannu is {{messageLink|1225781532.7597.19.camel@huvostro|working on a new version}}}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Datatypes ===&lt;br /&gt;
&lt;br /&gt;
{{patch|48E4A30C.3000503@cheapcomplexdevices.com|status=Waiting on Author|ISO 8601 interval literal input and output|Ron Mayer|reviewers=Brendan Jurd}}&lt;br /&gt;
{{comment|Ron Mayer|The initial (2003) version of this patch along with a thread which explains the feature a bit more can be found [http://archives.postgresql.org/pgsql-patches/2003-09/msg00103.php here].}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|490BA342.7010300@cheapcomplexdevices.com|latest version}}}}&lt;br /&gt;
{{review|37ed240d0811050750v11726fd1of441646f87b583da@mail.gmail.com|BJ|Code style and documentation suggestions}}&lt;br /&gt;
{{comment|Ron Mayer|Update here [http://0ape.com/postgres_interval_patches/ here] that fixes style &amp;amp; docs; as well as a bug where the ISO8601 spec wasn&#039;t quite followed (an optional field was treated as required by previous patches).}}&lt;br /&gt;
{{review|37ed240d0811062058n752c3880kb04feb85e355b524@mail.gmail.com|BJ|Query behaviour of &#039;P0001&#039;, final doc cleanup suggestions}}&lt;br /&gt;
{{comment|Ron Mayer|Update here [http://0ape.com/postgres_interval_patches/ here] that fixes &#039;P0001&#039; and updated docs.}}&lt;br /&gt;
{{comment|tgl|patch will need some work to sync with what I changed in the base IntervalStyle patch}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48CEDE68.7090501@cheapcomplexdevices.com|Interval rounding consistency|Ron Mayer|reviewers=Brendan Jurd}}&lt;br /&gt;
{{comment|Ron Mayer|Patch 3 [http://0ape.com/postgres_interval_patches/ here] refactors the interval code to remove much of the copy&amp;amp;paste in DecodeInterval and EncodeInterval with the side effect of making interval rounding more consistent between styles.  This patch applies on top of the IntervalStyle patch and the ISO 8601 Interval patch.}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20952F54-6730-49D8-99A3-1834697790B5@decibel.org|array_length|Jim C. Nasby|reviewers=Peter Eisentraut}}&lt;br /&gt;
{{comment|Robert Haas|I have {{messageLink|603c8f070811062006q4f20b2bq179d4d2ffec65690@mail.gmail.com|reimplemented this in C}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810151933p445978b3td481a5422a2aebf4@mail.gmail.com|array_agg/array_accum|Robert Haas|reviewers=Peter Eisentraut}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1225045937.4434.21.camel@localhost.localdomain|another version}} and {{messageLink|1225682527.1375.150.camel@jdavis|another one}} from Jeff Davis}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Indexes ===&lt;br /&gt;
&lt;br /&gt;
{{patch|490B07BA.6030109@sigaev.ru|GIN fast insert|Teodor Sigaev, Oleg Bartunov|reviewers=Jeff Davis}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490B3752.3010800@sigaev.ru|B-Tree emulation for GIN|status=WIP|Teodor Sigaev, Oleg Bartunov|reviewers=Jeff Davis}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081101000154.GO27872@fune|On-disk bitmap indexes|status=WIP|Gabriele Bartolini, Gianni Ciolli|reviewers=Greg Stark (more welcome!)}}&lt;br /&gt;
{{review|49130E72.1000803@sigaev.ru|Teodor Sigaev|several bugs}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Performance ===&lt;br /&gt;
&lt;br /&gt;
{{patch|6EEA43D22289484890D119821101B1DF2C1683@exchange20.mercury.ad.ubc.ca|Improve Performance of Multi-Batch Hash Join for Skewed Data Sets|Ramon Lawrence/Bryce Cutt|reviewers=Joshua Tolley}}&lt;br /&gt;
{{comment|Joshua Tolley|[http://archives.postgresql.org/pgsql-hackers/2008-11/msg00286.php] reports backend crash}}&lt;br /&gt;
{{comment|tgl|updated patch {{messageLink|1924d1180811051606w19aaf30du589e8ea10ea5534d@mail.gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4909B326.507@enterprisedb.com|Optimizing COPY with memchr()|Heikki Linnakangas|status=WIP|reviewers=Robert Haas}}&lt;br /&gt;
{{comment|tgl|does this really need any more review at this point?}}&lt;br /&gt;
{{comment|Robert Haas|asked author for {{messageLink|603c8f070811081745v410d2ff5o4bd107d7fbb440f3@mail.gmail.com|a status update}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|87ljw5c0lx.fsf@oxford.xeocode.com|posix_fadvise|Gregory Stark}}&lt;br /&gt;
&lt;br /&gt;
{{patch|a778a7260810280033n43f70d36x8c437eacf9a5461e@mail.gmail.com|Proposal of PITR performance improvement|Koichi Suzuki|reviewers=Simon Riggs}}&lt;br /&gt;
&lt;br /&gt;
{{patch|36e682920811021349h7202bdecpd7a45c8a8038465e@mail.gmail.com|Hash Join-Filter Pruning using Bloom Filters|status=WIP|Jonah Harris|reviewers=Kurt Harriman}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Improving admin experience ===&lt;br /&gt;
&lt;br /&gt;
{{patch|4905AE17.7090305@enterprisedb.com|Visibility map, partial vacuums|status=WIP|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081029183248.GE4331@alvh.no-ip.org|Block-level CRC checks|Alvaro Herrera|status=WIP}}&lt;br /&gt;
{{comment|alvherre|{{messageLink|20081107191140.GE5507@alvh.no-ip.org|updated patch}} here}}&lt;br /&gt;
&lt;br /&gt;
{{patch|c2ee6dbd0810100553gd328275ue2eb6e14bee70a8@mail.gmail.com|adding VERBOSE option to CLUSTER|Jim Cox|reviewers=Peter Eisentraut}}&lt;br /&gt;
&lt;br /&gt;
{{patch|a301bfd90810310750pf108c69x36499546f406650f@mail.gmail.com|Auto Partitioning Patch|Nikhil Sontakke|reviewers=Jaime Casanova}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1223379173.4747.145.camel@ebony.2ndQuadrant|Reducing some DDL Locks to ShareLock|status=Pending Review|Simon Riggs|reviewers=Tom Lane}} &lt;br /&gt;
{{comment|tgl|{{messageLink|1223404726.4747.249.camel@ebony.2ndQuadrant|v6 patch here}}}}&lt;br /&gt;
{{comment|sriggs|agreed rework to implement pg_domain constraint, but the main patch still needs review}}&lt;br /&gt;
{{comment|tgl|I think we&#039;d decided to pass on the pg_constraint restructuring, at least for now}}&lt;br /&gt;
{{comment|tgl|partially applied, what&#039;s left is {{messageLink|17459.1226279911@sss.pgh.pa.us|here}}}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Connection management ===&lt;br /&gt;
&lt;br /&gt;
{{patch|48FC7E84.3080702@hagander.net|SSL cleanups/hostname verification|Magnus Hagander|reviewers=Alex Hunsaker}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49009D67.4040202@hagander.net|clientcert option for pg_hba|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49076F39.1080502@hagander.net|regexp support in usermaps|Magnus Hagander|reviewers=Gianni Colli}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Contrib modules ===&lt;br /&gt;
&lt;br /&gt;
{{patch|20081106171139.8D21.52131E4D@oss.ntt.co.jp|contrib infrastructures|Martin Pihlak, Takahiro Itagaki|reviewers=Jeff Davis, Matthew Wetmore}}&lt;br /&gt;
{{comment|Itagaki|contains {{messageLink|490A00A8.7050708@gmail.com|QueryDesc}}, {{messageLink|20081009165157.9BE4.52131E4D@oss.ntt.co.jp|explain}} and {{messageLink|20081027171917.ADD6.52131E4D@oss.ntt.co.jp|hooks}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081009165157.9BE4.52131E4D@oss.ntt.co.jp|contrib/auto_explain|Takahiro Itagaki|reviewers=Jeff Davis}}&lt;br /&gt;
{{comment|Itagaki|{{messageLink|20081110173232.7F2B.52131E4D@oss.ntt.co.jp|latest patch versions}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081011172450.3402.52131E4D@oss.ntt.co.jp|contrib/pg_stat_statements|Takahiro Itagaki|reviewers=Matthew Wetmore}}&lt;br /&gt;
{{comment|Itagaki|{{messageLink|20081027171917.ADD6.52131E4D@oss.ntt.co.jp|latest patch versions}}}}&lt;br /&gt;
{{comment|Itagaki|{{messageLink|1d709ecc0811011343lf65f58fjb2e96194f4c2ecc5@mail.gmail.com|comments}} from Vladimir}}&lt;br /&gt;
&lt;br /&gt;
{{patch|e4ccc24e0810222010p12bae2f4xa3a11cb2bc51bd89@mail.gmail.com|pg_standby support for compressed segments|Charles Duffy|reviewers=Simon Riggs}}&lt;br /&gt;
{{comment|Simon Riggs|Deferring review for a few weeks until we get a better picture of streaming replication requirements for 8.4}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.GSO.4.64.0811012101220.17619@westnet.com|Simple postgresql.conf wizard|Greg Smith|reviewers=Josh Berkus}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
=== Clients ===&lt;br /&gt;
&lt;br /&gt;
{{patch|200810271936.m9RJaGW09544@momjian.us|libpq callback unregistration|Bruce Momjian|reviewers=Magnus Hagander}}&lt;br /&gt;
{{comment|Magnus|Needs more work, comments {{messageLink|490EEF2D.2050703@hagander.net|here}}}}&lt;br /&gt;
{{comment|alvherre|Bruce posted a {{messageLink|200811050502.mA552TJ20677@momjian.us|new version}}, but it still {{messageLink|20081107201029.GF5507@alvh.no-ip.org|needs some work}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48F04B7C.3080303@benedekl.tvnetwork.hu|pg_dump roles support|Benedek Laszlo|reviewers=Ibrar Ahmed|Status=Waiting for Author}}&lt;br /&gt;
{{comment|alvherre|there&#039;s an {{messageLink|4912FA4E.1090000@benedekl.tvnetwork.hu|updated patch}}, and some extra {{messageLink|20081107202000.GG5507@alvh.no-ip.org|comments}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490878AC.1@dunslane.net|parallel restore|status=WIP|Andrew Dunstan|reviewers=Kenneth Marshall}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
{{patch|03c301c91737$be5a2a30$0e01a8c0@IBMC9A0F63B40D|Solve a problem of LC_TIME of windows|Hiroshi Saito}}&lt;br /&gt;
{{comment|tgl|updated version {{messageLink|2C940A1672E743439355545C5DB15786@HIRO57887DE653|here}}}}&lt;br /&gt;
{{comment|itagaki|comments and updated version {{messageLink|20081104094301.7EE8.52131E4D@oss.ntt.co.jp|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|BLU110-W38CE0A22D467A8C3D9736CFF540@phx.gbl|Support PLUGINS lines in Makefiles, similar to MODULES|Asif Naeem}}&lt;br /&gt;
{{comment|Dave Page|This doesn&#039;t work with the edb-debugger plugin, which is the only such plugin around AFAIK. It needs to ignore comments on the PLUGINS line, and handle multiple targets (plugin_debugger, pldbgapi, targetinfo etc). Not sure if we want that complexity though.}}&lt;br /&gt;
{{comment|Heikki|Unix-makefile version: {{messageLink|BLU110-W57823CEB7DC113354471EFF3B0@phx.gbl|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48F53EC0.3020004@timbira.com|autovacuum and reloption|status=WIP|Euler Taveira de Oliveira|reviewers=Alvaro Herrera}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49097338.2070700@gmail.com|SQL/MED compatible connection manager|Martin Pihlak|status=WIP}}&lt;br /&gt;
{{comment|Martin Pihlak|Updated patch {{messageLink|49142C02.8020706@gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081029164000.GL27466@fetter.org|pre-MED|David Fetter|reviewers=Alex Hunsaker|status=Waiting on author}}&lt;br /&gt;
{{comment|David Fetter|Updated patch {{messageLink|20081031144852.GF15545@fetter.org|here}}}}&lt;br /&gt;
{{review|34d269d40811031902p1d73d177w9f2e721ae169e8be@mail.gmail.com|alexhun|few questions and tgl had some constructive {{messageLink|24867.1225819435@sss.pgh.pa.us|comments}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|f205bb120810280833x340324d3m19a4f8aa65d822b@mail.gmail.com|FAQ_Solaris 1.28 to spanish|Emanuel CALVO FRANCO|reviewers=Peter Eisentraut}}&lt;br /&gt;
&lt;br /&gt;
{{CommitFestEndSection}}&lt;br /&gt;
&lt;br /&gt;
== Committed patches ==&lt;br /&gt;
{{CommitFestSectionNew}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20080803.114711.73374027.t-ishii@sraoss.co.jp|Common Table Expressions|Yoshiyuki Asaba|status=Committed 2008-10-04|reviewers=Jeff Davis}}&lt;br /&gt;
{{comment|David Fetter|README is {{messageLink|20080818.163852.105172778.t-ishii@sraoss.co.jp|here.}}}}&lt;br /&gt;
{{comment|David Fetter|Git repository is [http://git.postgresql.org/git/~davidfetter/cte/.git here.]}}&lt;br /&gt;
{{comment|David Fetter|[[CTEReadme]]}}&lt;br /&gt;
{{comment|David Fetter|[[CTESQLStandard| Fair Use from the draft SQL:2008 standard (WIP)]]}}&lt;br /&gt;
{{review|13449.1221589943@sss.pgh.pa.us|tgl|needs a good bit of work yet}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.GSO.4.64.0809152349440.19910@westnet.com|Add default_val to pg_settings|status=Committed 2008-10-06|Greg Smith|reviewers=Simon Riggs,Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081016102603.897D.52131E4D@oss.ntt.co.jp|Noisy _dosmaperror|status=Committed 2008-10-16|Takahiro Itagaki|reviewers=Tom Lane}}&lt;br /&gt;
&lt;br /&gt;
{{patch|b4e5ce320810151918g2acf69ebh9f80f4f2e1c203a0@mail.gmail.com|Memory leak on hashed agg rescan|status=Committed 2008-10-16|Neil Conway|reviewers=Tom Lane}}&lt;br /&gt;
{{review|10455.1224160007@sss.pgh.pa.us|Tom Lane|move some logic to separate function}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1223383838.4747.154.camel@ebony.2ndQuadrant|Atomic subtransaction commit|status=Committed 2008-10-20|Simon Riggs|reviewers=Alvaro Herrera}} &lt;br /&gt;
&lt;br /&gt;
{{patch|3327.1224535092@sss.pgh.pa.us|add placeholder variables to planner|status=Committed 2008-10-22|Tom Lane}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48E271C5.7010907@hagander.net|pg_hba options parsing|status=Committed 2008-10-23|Magnus Hagander|reviewers=Bruce Momjian}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|48F0DE8B.8030004@hagander.net|updated patch}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48FC3994.8040809@hagander.net|libpq ssl -&amp;gt; clear fallback looses error messages|status=Committed 2008-10-27|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905D22D.9040001@hagander.net|better hba parsing error messages|status=Committed 2008-10-27|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905A1DE.5030102@hagander.net|remove crypt authentication|status=Committed 2008-10-28|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905F515.3020208@gmx.net|Unicode escapes in literals|status=Committed 2008-10-29|Peter Eisentraut}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490A138E.80100@enterprisedb.com|User defined I/O conversion casts|status=Committed 2008-10-31|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49085327.5010608@enterprisedb.com|Updating FSM on recovery|status=Committed 2008-10-31|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.BSO.4.64.0810271955030.28764@leary.csoft.net|use new heap_(form/deform/modify)_tuple API|Kris Jurka|reviewers=Zdenek Kotala|status=Committed 2008-11-01}}&lt;br /&gt;
{{comment|Zdenek Kotala| It seems OK. Needs apply also {{messageLink|Pine.BSO.4.64.0810281721500.6833@leary.csoft.net|pfree patch.}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.BSO.4.64.0810281622240.9851@leary.csoft.net|don&#039;t use MAKE_PTR/OFFSET for shmem pointers|Kris Jurka|reviewers=Tom Lane|status=Committed 2008-11-02}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48C181D4.8030807@gmail.com|reducing statistics write overhead|Martin Pihlak|reviewers=Tom Lane|status=Committed 2008-11-02}}&lt;br /&gt;
{{comment|Martin Pihlak|Latest patch {{messageLink|48C594D8.6050504@gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|37ed240d0809030015u73b65b66v70fd76741317c6f5@mail.gmail.com|pg_typeof()|Brendan Jurd|reviewers=Kurt Harriman|status=Committed 2008-11-03}}&lt;br /&gt;
{{comment|Kurt Harriman|{{messageLink|http://archives.postgresql.org/pgsql-hackers/2008-11/msg00080.php|Updated patch}} is ready to commit if there is no objection}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.BSO.4.64.0810081931240.11647@leary.csoft.net|Fixes for psql describeOneTableDetails|Kris Jurka|reviewers=Tom Lane|status=Committed 2008-11-03}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48E22CF5.4050503@sun.com|PageGetTempPage cleanup |Zdenek Kotala|reviewers=Tom Lane|status=Committed 2008-11-03}}&lt;br /&gt;
{{comment|Zdenek Kotala|Original discussion {{messageLink|4938.1217862947@sss.pgh.pa.us|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810092009s1312d30bxc854cdfb5d9fed7e@mail.gmail.com|Allow the UUID type to accept non-standard formats|Robert Haas|reviewers=Peter Eisentraut|status=Committed 2008-11-03}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810101937n776c1e7cvd6a12345b0bbda28@mail.gmail.com|array_ndims|Robert Haas|reviewers=Peter Eisentraut|status=Committed 2008-11-04}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810282045g7fa6bdf9p53f03114d49643d7@mail.gmail.com|bulk inserts - keep most recent page pinned|Robert Haas|reviewers=Tom Lane|status=Committed 2008-11-06}}&lt;br /&gt;
{{comment|Robert Haas|based on work by Simon Riggs: [http://archives.postgresql.org/pgsql-hackers/2008-02/msg01080.php original idea],[http://archives.postgresql.org/pgsql-patches/2008-02/msg00140.php original patch], [http://archives.postgresql.org/pgsql-patches/2008-02/msg00154.php Tom Lane&#039;s comments]}}&lt;br /&gt;
{{comment|Robert Haas|Tom&#039;s comments on my [http://archives.postgresql.org/pgsql-hackers/2008-10/msg01276.php design proposal] are {{messageLink|17996.1225049097@sss.pgh.pa.us|here}}}}&lt;br /&gt;
{{comment|Robert Haas|patch {{messageLink|603c8f070811011023n202aea33w4da13b7d14f74134@mail.gmail.com|v2}}, adjusting for Heikki&#039;s changes to the ReadBuffer interface}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490394B7.6090503@lelarge.info|ALTER DATABASE SET TABLESPACE Statement|Guillaume Lelarge|reviewers=Bernd Helmle|status=Committed 2008-11-07}}&lt;br /&gt;
{{comment|Bernd Helmle|Syntax discussion and updated version {{messageLink|C0F6602797884925406AB88F@imhotep.credativ.de|here}}}}&lt;br /&gt;
{{comment|Guillaume Lelarge|Updated version with SET syntax {{messageLink|4910E46E.4010000@lelarge.info|here}}}}&lt;br /&gt;
{{comment|Bernd Helmle|Updated version from Guillaume {{messageLink|4912C88A.2070808@lelarge.info|here}}}}&lt;br /&gt;
{{comment|Guillaume Lelarge|Updated version {{messageLink|49140181.3000903@lelarge.info|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|0BD2E4E9-AF5A-4B4F-B546-027424EE8FAD@kineticode.com|Tests citext casts|David Wheeler|reviewers=&lt;br /&gt;
Kenneth Marshall|status=Committed 2008-11-07}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48D15471.6080305@cheapcomplexdevices.com|SQL Standard Interval output and IntervalStyle GUC|Ron Mayer|status=Committed 2008-11-08|reviewers=Brendan Jurd}}&lt;br /&gt;
{{comment|Ron Mayer|Early updates {{messageLink|48D52E48.406@cheapcomplexdevices.com|here}},   {{messageLink|48E49BDC.4090402@cheapcomplexdevices.com|here}}, and [http://0ape.com/postgres_interval_patches/ here]. Mostly related to GUC changes.}}&lt;br /&gt;
{{review|37ed240d0811032122u56db1959h91f53bbb9733c90d@mail.gmail.com|BJ|Bug in output, stylistic suggestions}}&lt;br /&gt;
{{comment|the mailing list|Feedback from {{messageLink|19477.1225814409@sss.pgh.pa.us|Tom L}} and {{messageLink|49101C94.EE98.0025.0@wicourts.gov|Kevin G}} about mixed-sign intervals}}&lt;br /&gt;
{{comment|Ron Mayer|Updated patch {{messageLink|4910B1DB.4000000.cheapcomplexdevices@com|here}} to fix -12:01:-30 bug and style suggestions from the review and to attempt to address feedback about mixed-sign intervals with doc updates.}}&lt;br /&gt;
{{review|37ed240d0811042102q78df5b86t2ff2092a75d371d7@mail.gmail.com|BJ|One last typo in docs but otherwise all good; review complete}}&lt;br /&gt;
{{review|28915.1226109473@sss.pgh.pa.us|Tom L|Tom pointed out issues with pg_dump and restore into databases with a different interval style}}&lt;br /&gt;
{{comment|Ron Mayer|{{messageLink|4915AC0A.9070608@cheapcomplexdevices.com|Speculating}} if an analogy with standard_conforming_strings applies to how we can handle dump/restore.}}&lt;br /&gt;
&lt;br /&gt;
{{CommitFestEndSection}}&lt;br /&gt;
&lt;br /&gt;
== Returned with Feedback ==&lt;br /&gt;
{{CommitFestSectionNew}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1225010283.21241.33.camel@localhost.localdomain|new correlation metric|Jeff Davis|reviewers=Brendan Jurd|status=Pending rework}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49086E4C.9030602@sun.com|htup and bufpage API clean up|Zdenek Kotala|reviewers=Robert Haas|status=Needs different approach}}&lt;br /&gt;
{{comment|Zdenek Kotala|New version is {{messageLink|490875FA.4020709@sun.com|here}}}}&lt;br /&gt;
{{review|603c8f070811031822q7d3b33f7x8576b7028f498cc4@mail.gmail.com|Robert Haas|proposed API seems too costly and fragile}}&lt;br /&gt;
&lt;br /&gt;
{{CommitFestEndSection}}&lt;br /&gt;
&lt;br /&gt;
== Round Robin Reviewers ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; cellspacing=&amp;quot;0&amp;quot; style=&amp;quot;width: 60%; border-collapse: collapse; border: 1px solid #ccc; font-size: 90%;&amp;quot;&lt;br /&gt;
|- style=&amp;quot;background: #eee;&amp;quot;&lt;br /&gt;
! width=&amp;quot;30%&amp;quot; | Name&lt;br /&gt;
!Status&lt;br /&gt;
!Reviewing&lt;br /&gt;
!Completed&lt;br /&gt;
|-&lt;br /&gt;
|Brendan Jurd || Available || 2 || 2&lt;br /&gt;
|-&lt;br /&gt;
|Jaime Casanova || Available || 1 || 1&lt;br /&gt;
|-&lt;br /&gt;
|Stephen Frost || Available 11/15 || 0 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Jeff Davis || Available || 2 || 1&lt;br /&gt;
|-&lt;br /&gt;
|Greg Stark || Unknown || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Abhijit Menon-Sen || Unknown || 0 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Alex Hunsaker || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Markus Wanner || Cherry-picking || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Ibrar Ahmed || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|D&#039;Arcy Cain || Unknown || 0 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Kenneth Marshall || Available || 1 || 1&lt;br /&gt;
|-&lt;br /&gt;
|Robert Haas || Available || 1 || 4&lt;br /&gt;
|-&lt;br /&gt;
|Matthew Wetmore || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Gianni Colli || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|&amp;quot;Unicron&amp;quot; || Available || 1 || 1&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=CommitFest_2008-11&amp;diff=3452</id>
		<title>CommitFest 2008-11</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=CommitFest_2008-11&amp;diff=3452"/>
		<updated>2008-11-10T14:41:11Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* SQL language features */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__TOC__&lt;br /&gt;
&lt;br /&gt;
This is the page for the CommitFest starting &#039;&#039;&#039;2008 November&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Managers for this CommitFest are Josh Berkus (josh-at-agliodbs-com) and Dave Page (dpage-at-pgadmin-org).&lt;br /&gt;
&lt;br /&gt;
{{CommitFestCurrent}}&lt;br /&gt;
&lt;br /&gt;
== Pending patches ==&lt;br /&gt;
{{CommitFestSectionNew}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
=== SE-PostgreSQL and related ===&lt;br /&gt;
&lt;br /&gt;
{{patch|4863B3DA.8030209@kaigai.gr.jp|SE-PostgreSQL patches|Kaigai Kohei}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|48F71E36.9010203@ak.jp.nec.com|latest version}}, now with 6 patches}}&lt;br /&gt;
{{comment|KaiGai|[[SEPostgreSQL]] is a draft of comprehensive document}}&lt;br /&gt;
{{comment|KaiGai|{{messageLink|49180B32.5030308@ak.jp.nec.com|The latest patches to be reviewed (r1206)}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20080901063855.GJ16005@tamriel.snowman.net|Column-level Permissions|Stephen Frost|status=Pending Review|reviewers=Markus Wanner}}&lt;br /&gt;
{{comment|Stephen Frost|Updated patch {{messageLink|20080902221823.GL16005@tamriel.snowman.net|here}}}}&lt;br /&gt;
{{review|48DB48AC.5010400@bluegap.ch|Markus Wanner|Awaiting updated patch.}}&lt;br /&gt;
{{comment|Stephen Frost|Updated patch, again, {{messageLink|20081102034517.GR4452@tamriel.snowman.net|here}}}}&lt;br /&gt;
{{comment|Stephen Frost|Updated patch, fixes case where unprivileged user can get row count, {{messageLink|20081102131332.GU4452@tamriel.snowman.net|here}}}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Recovery, Replication, Hot Standby ===&lt;br /&gt;
&lt;br /&gt;
{{patch|1220213074.4371.173.camel@ebony.2ndQuadrant|Infrastructure changes for recovery|status=Pending Review|Simon Riggs|reviewers=Tom Lane, Heikki Linnakangas}} &lt;br /&gt;
{{comment|sriggs| important patch for other work}}&lt;br /&gt;
{{comment|tgl|some comments {{messageLink|1905.1220895241@sss.pgh.pa.us|here}}}}&lt;br /&gt;
{{comment|tgl|updated patch {{messageLink|1221080797.3913.768.camel@ebony.2ndQuadrant|here}}, still being tested}}&lt;br /&gt;
{{comment|tgl|Simon found {{messageLink|1221725145.3913.2315.camel@ebony.2ndQuadrant|some issues}}}}&lt;br /&gt;
{{comment|tgl|{{messageLink|1222184541.4445.400.camel@ebony.2ndQuadrant|patch v7}} here}}&lt;br /&gt;
{{comment|tgl|it&#039;s still got {{messageLink|28973.1222381719@sss.pgh.pa.us|issues}}}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1222815151.4445.1397.camel@ebony.2ndQuadrant|patch v8}} here}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1223472898.4747.310.camel@ebony.2ndQuadrant|patch v9}} here, in response to {{messageLink|48EC9CC5.6060803@enterprisedb.com|Heikki&#039;s review}}}}&lt;br /&gt;
{{comment|sriggs|some issues overlooked, fixed as part of Hot Standby patch only at present}}&lt;br /&gt;
{{comment|sriggs|do we want this split out again as a separate patch for easier review?}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1225557138.3971.673.camel@ebony.2ndQuadrant|Hot Standby - queries during archive recovery|status=Pending Review|Simon Riggs}}&lt;br /&gt;
{{comment|sriggs| v5d now available, fixing all Mark&#039;s reported issues. Main parts are fully reviewable}}&lt;br /&gt;
{{comment|sriggs| Wiki contains dynamically updated list of outstanding items [[Hot_Standby]] }}&lt;br /&gt;
&lt;br /&gt;
{{patch|1223472186.4747.301.camel@ebony.2ndQuadrant|pg_stop_backup wait bug fix|Simon Riggs}}&lt;br /&gt;
{{comment|Robert Haas|sriggs extracted this from recovery infrastructure patch per {{messageLink|48EC9CC5.6060803@enterprisedb.com|Heikki&#039;s suggestion}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1220174867.4371.107.camel@ebony.2ndQuadrant|rmgr hooks and contrib/rmgr_hook|status=Waiting on dependencies|Simon Riggs}} &lt;br /&gt;
{{comment|sriggs| deferrable, if required}}&lt;br /&gt;
{{comment|tgl|I think the plan is for this to wait till &amp;quot;infrastructure&amp;quot; patch goes in}}&lt;br /&gt;
&lt;br /&gt;
{{patch|3f0b79eb0810310436w360f0afdy76ff1499b177ce0d@mail.gmail.com|Synchronous log-shipping replication|Masao Fujii|reviewers=Heikki Linnakangas, Simon Riggs}}&lt;br /&gt;
{{comment|fujii|{{messageLink|3f0b79eb0811040404r799d3170v5bb9f201000f1771@mail.gmail.com|signal handling patch v2}} here}}&lt;br /&gt;
{{comment|fujii|{{messageLink|3f0b79eb0811050617o3237130awb4aec1d3a2daacab@mail.gmail.com|walsender process patch v1}} here}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Upgrade-in-place and related issues === &lt;br /&gt;
&lt;br /&gt;
{{patch|490B7C1B.8050408@sun.com|In-place online upgrade|status=Waiting for new version|Zdenek Kotala|reviewers=Robert Haas}}&lt;br /&gt;
{{comment|Zdenek Kotala|This patch requires &amp;quot;htup and bufpage API clean up&amp;quot; and &amp;quot;HeapTuple version extension&amp;quot; patches. Git repository is [http://git.postgresql.org here] }}&lt;br /&gt;
{{review|603c8f070811022022x582a9cbdp60798a6b87910edf@mail.gmail.com|Robert Haas|preliminary comments, still need a clean diff}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48F1FC7E.1060406@sun.com|Extending pg_class info + more flexible TOAST chunk size|Zdenek Kotala|reviewers=Robert Haas|status=Waiting for new version}}&lt;br /&gt;
{{comment|tgl|seems it&#039;d be better to make TOAST chunks work like {{messageLink|490AB654.6040409@enterprisedb.com|this}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4909DFCE.1000702@sun.com|HeapTuple version extension + code cleanup|Zdenek Kotala|reviewers=Robert Haas|status=Waiting for new version}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== SQL language features ===&lt;br /&gt;
&lt;br /&gt;
{{patch|e08cc0400810270912u49a6ec83vc23984c01f368f76@mail.gmail.com|Window Functions|Hitoshi Harada|reviewers=Heikki Linnakangas, David Rowley}}&lt;br /&gt;
{{comment|Hitoshi Harada|updated patch is {{messageLink|e08cc0400810310721l22a6bb7kb6a300ce66443806@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Hitoshi Harada|updated patch is {{messageLink|e08cc0400811070746p43553f10s6bb09e98b7eafc3b@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Hitoshi Harada|updated patch is {{messageLink|e08cc0400811100548s1d31af73s888062c05c8512bd@mail.gmail.com|here}}, stil some issues on {{messageLink|e08cc0400811100619w46a1b013x2051f6a8f2dad116@mail.gmail.com|ntile} and {{messageLink|e08cc0400811100624o77744b15me1bc009b74d292c1@mail.gmail.com|nth_value}}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|162867790810170316l4eeecb0bq321dd771f8f4e661@mail.gmail.com|grouping sets|status=WIP|Pavel Stehule|reviewers=Ibrar Ahmed}}&lt;br /&gt;
{{comment|Pavel Stehule| doc and notes [[Grouping Sets]]}}&lt;br /&gt;
&lt;br /&gt;
{{patch|162867790810260428p56d16352qa1ec5c4c5330f25c@mail.gmail.com|default values for function&#039;s parameters|Pavel Stehule|reviewers=Peter Eisentraut|status=WIP}}&lt;br /&gt;
{{comment|Pavel Stehule| fix known bugs, currently only doc should be finished}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070808070503jd7be083kcce3e16345affb08@mail.gmail.com|add columns via CREATE OR REPLACE VIEW|Robert Haas|reviewers=Bernd Helmle}}&lt;br /&gt;
{{comment|Robert Haas|some further justification of the proposed design {{messageLink|603c8f070808070956t1ab98dcdr933575eb096e4c28@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Robert Haas|questions about how to move forward {{messageLink|603c8f070810031839y7ce9a852o86effbab9fd6dd9b@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Robert Haas|a {{messageLink|482096EC.3000805@dunslane.net|similar feature request}} from Andrew Dunstan}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48EFA13C.2060407@frogthinker.org|Prepared transactions and temp tables|Emmanuel Cecchet|reviewers=Heikki Linnakangas}}&lt;br /&gt;
{{comment|tgl|new patch version {{messageLink|4914CD14.2060608@frogthinker.org|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4909726F.8000800@gmx.net|TABLE command|Peter Eisentraut|status=Waiting on author|reviewers=Unicron, Robert Haas}}&lt;br /&gt;
{{comment|Unicron|Patch {{messageLink|850603.14426.qm@web62408.mail.re1.yahoo.com|works per specification}}}}&lt;br /&gt;
{{review|603c8f070811081050k79926d12x6547ae72abaa41af@mail.gmail.com|Robert Haas|wrong non-terminal, needs doc and psql updates}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490AFC08.8040500@Sun.COM|Distinct types|Peter Eisentraut|status=Waiting on author}}&lt;br /&gt;
{{comment|Bernd Helmle|Patch needs further work regarding {{messageLink|17750.1225571886@sss.pgh.pa.us|indexing}}}}&lt;br /&gt;
{{comment|tgl|I don&#039;t think the {{messageLink|21942.1226084284@sss.pgh.pa.us|type-system behavior}} has been thought through properly}}&lt;br /&gt;
&lt;br /&gt;
{{patch|2849137C693B65CC8E86411C@imhotep.credativ.de|Automatic view update rules|status=WIP|Bernd Helmle|reviewers=Unicron}}&lt;br /&gt;
{{comment|Bernd Helmle|New version with RETURNING support {{messageLink|94CF655A8D0DC7D5B4B81D8B@imhotep.credativ.de|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1225543926.8122.14.camel@huvostro|Enable pl/python to return records based on multiple OUT params|status=Waiting on author|Hannu Krosing}}&lt;br /&gt;
{{comment|Robert Haas|Hannu is {{messageLink|1225781532.7597.19.camel@huvostro|working on a new version}}}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Datatypes ===&lt;br /&gt;
&lt;br /&gt;
{{patch|48E4A30C.3000503@cheapcomplexdevices.com|status=Waiting on Author|ISO 8601 interval literal input and output|Ron Mayer|reviewers=Brendan Jurd}}&lt;br /&gt;
{{comment|Ron Mayer|The initial (2003) version of this patch along with a thread which explains the feature a bit more can be found [http://archives.postgresql.org/pgsql-patches/2003-09/msg00103.php here].}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|490BA342.7010300@cheapcomplexdevices.com|latest version}}}}&lt;br /&gt;
{{review|37ed240d0811050750v11726fd1of441646f87b583da@mail.gmail.com|BJ|Code style and documentation suggestions}}&lt;br /&gt;
{{comment|Ron Mayer|Update here [http://0ape.com/postgres_interval_patches/ here] that fixes style &amp;amp; docs; as well as a bug where the ISO8601 spec wasn&#039;t quite followed (an optional field was treated as required by previous patches).}}&lt;br /&gt;
{{review|37ed240d0811062058n752c3880kb04feb85e355b524@mail.gmail.com|BJ|Query behaviour of &#039;P0001&#039;, final doc cleanup suggestions}}&lt;br /&gt;
{{comment|Ron Mayer|Update here [http://0ape.com/postgres_interval_patches/ here] that fixes &#039;P0001&#039; and updated docs.}}&lt;br /&gt;
{{comment|tgl|patch will need some work to sync with what I changed in the base IntervalStyle patch}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48CEDE68.7090501@cheapcomplexdevices.com|Interval rounding consistency|Ron Mayer|reviewers=Brendan Jurd}}&lt;br /&gt;
{{comment|Ron Mayer|Patch 3 [http://0ape.com/postgres_interval_patches/ here] refactors the interval code to remove much of the copy&amp;amp;paste in DecodeInterval and EncodeInterval with the side effect of making interval rounding more consistent between styles.  This patch applies on top of the IntervalStyle patch and the ISO 8601 Interval patch.}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20952F54-6730-49D8-99A3-1834697790B5@decibel.org|array_length|Jim C. Nasby|reviewers=Peter Eisentraut}}&lt;br /&gt;
{{comment|Robert Haas|I have {{messageLink|603c8f070811062006q4f20b2bq179d4d2ffec65690@mail.gmail.com|reimplemented this in C}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810151933p445978b3td481a5422a2aebf4@mail.gmail.com|array_agg/array_accum|Robert Haas|reviewers=Peter Eisentraut}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1225045937.4434.21.camel@localhost.localdomain|another version}} and {{messageLink|1225682527.1375.150.camel@jdavis|another one}} from Jeff Davis}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Indexes ===&lt;br /&gt;
&lt;br /&gt;
{{patch|490B07BA.6030109@sigaev.ru|GIN fast insert|Teodor Sigaev, Oleg Bartunov|reviewers=Jeff Davis}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490B3752.3010800@sigaev.ru|B-Tree emulation for GIN|status=WIP|Teodor Sigaev, Oleg Bartunov|reviewers=Jeff Davis}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081101000154.GO27872@fune|On-disk bitmap indexes|status=WIP|Gabriele Bartolini, Gianni Ciolli|reviewers=Greg Stark (more welcome!)}}&lt;br /&gt;
{{review|49130E72.1000803@sigaev.ru|Teodor Sigaev|several bugs}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Performance ===&lt;br /&gt;
&lt;br /&gt;
{{patch|6EEA43D22289484890D119821101B1DF2C1683@exchange20.mercury.ad.ubc.ca|Improve Performance of Multi-Batch Hash Join for Skewed Data Sets|Ramon Lawrence/Bryce Cutt|reviewers=Joshua Tolley}}&lt;br /&gt;
{{comment|Joshua Tolley|[http://archives.postgresql.org/pgsql-hackers/2008-11/msg00286.php] reports backend crash}}&lt;br /&gt;
{{comment|tgl|updated patch {{messageLink|1924d1180811051606w19aaf30du589e8ea10ea5534d@mail.gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4909B326.507@enterprisedb.com|Optimizing COPY with memchr()|Heikki Linnakangas|status=WIP|reviewers=Robert Haas}}&lt;br /&gt;
{{comment|tgl|does this really need any more review at this point?}}&lt;br /&gt;
{{comment|Robert Haas|asked author for {{messageLink|603c8f070811081745v410d2ff5o4bd107d7fbb440f3@mail.gmail.com|a status update}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|87ljw5c0lx.fsf@oxford.xeocode.com|posix_fadvise|Gregory Stark}}&lt;br /&gt;
&lt;br /&gt;
{{patch|a778a7260810280033n43f70d36x8c437eacf9a5461e@mail.gmail.com|Proposal of PITR performance improvement|Koichi Suzuki|reviewers=Simon Riggs}}&lt;br /&gt;
&lt;br /&gt;
{{patch|36e682920811021349h7202bdecpd7a45c8a8038465e@mail.gmail.com|Hash Join-Filter Pruning using Bloom Filters|status=WIP|Jonah Harris|reviewers=Kurt Harriman}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Improving admin experience ===&lt;br /&gt;
&lt;br /&gt;
{{patch|4905AE17.7090305@enterprisedb.com|Visibility map, partial vacuums|status=WIP|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081029183248.GE4331@alvh.no-ip.org|Block-level CRC checks|Alvaro Herrera|status=WIP}}&lt;br /&gt;
{{comment|alvherre|{{messageLink|20081107191140.GE5507@alvh.no-ip.org|updated patch}} here}}&lt;br /&gt;
&lt;br /&gt;
{{patch|c2ee6dbd0810100553gd328275ue2eb6e14bee70a8@mail.gmail.com|adding VERBOSE option to CLUSTER|Jim Cox|reviewers=Peter Eisentraut}}&lt;br /&gt;
&lt;br /&gt;
{{patch|a301bfd90810310750pf108c69x36499546f406650f@mail.gmail.com|Auto Partitioning Patch|Nikhil Sontakke|reviewers=Jaime Casanova}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1223379173.4747.145.camel@ebony.2ndQuadrant|Reducing some DDL Locks to ShareLock|status=Pending Review|Simon Riggs|reviewers=Tom Lane}} &lt;br /&gt;
{{comment|tgl|{{messageLink|1223404726.4747.249.camel@ebony.2ndQuadrant|v6 patch here}}}}&lt;br /&gt;
{{comment|sriggs|agreed rework to implement pg_domain constraint, but the main patch still needs review}}&lt;br /&gt;
{{comment|tgl|I think we&#039;d decided to pass on the pg_constraint restructuring, at least for now}}&lt;br /&gt;
{{comment|tgl|partially applied, what&#039;s left is {{messageLink|17459.1226279911@sss.pgh.pa.us|here}}}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Connection management ===&lt;br /&gt;
&lt;br /&gt;
{{patch|48FC7E84.3080702@hagander.net|SSL cleanups/hostname verification|Magnus Hagander|reviewers=Alex Hunsaker}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49009D67.4040202@hagander.net|clientcert option for pg_hba|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49076F39.1080502@hagander.net|regexp support in usermaps|Magnus Hagander|reviewers=Gianni Colli}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Contrib modules ===&lt;br /&gt;
&lt;br /&gt;
{{patch|20081106171139.8D21.52131E4D@oss.ntt.co.jp|contrib infrastructures|Martin Pihlak, Takahiro Itagaki|reviewers=Jeff Davis, Matthew Wetmore}}&lt;br /&gt;
{{comment|Itagaki|contains {{messageLink|490A00A8.7050708@gmail.com|QueryDesc}}, {{messageLink|20081009165157.9BE4.52131E4D@oss.ntt.co.jp|explain}} and {{messageLink|20081027171917.ADD6.52131E4D@oss.ntt.co.jp|hooks}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081009165157.9BE4.52131E4D@oss.ntt.co.jp|contrib/auto_explain|Takahiro Itagaki|reviewers=Jeff Davis}}&lt;br /&gt;
{{comment|Itagaki|{{messageLink|20081110173232.7F2B.52131E4D@oss.ntt.co.jp|latest patch versions}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081011172450.3402.52131E4D@oss.ntt.co.jp|contrib/pg_stat_statements|Takahiro Itagaki|reviewers=Matthew Wetmore}}&lt;br /&gt;
{{comment|Itagaki|{{messageLink|20081027171917.ADD6.52131E4D@oss.ntt.co.jp|latest patch versions}}}}&lt;br /&gt;
{{comment|Itagaki|{{messageLink|1d709ecc0811011343lf65f58fjb2e96194f4c2ecc5@mail.gmail.com|comments}} from Vladimir}}&lt;br /&gt;
&lt;br /&gt;
{{patch|e4ccc24e0810222010p12bae2f4xa3a11cb2bc51bd89@mail.gmail.com|pg_standby support for compressed segments|Charles Duffy|reviewers=Simon Riggs}}&lt;br /&gt;
{{comment|Simon Riggs|Deferring review for a few weeks until we get a better picture of streaming replication requirements for 8.4}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.GSO.4.64.0811012101220.17619@westnet.com|Simple postgresql.conf wizard|Greg Smith|reviewers=Josh Berkus}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
=== Clients ===&lt;br /&gt;
&lt;br /&gt;
{{patch|200810271936.m9RJaGW09544@momjian.us|libpq callback unregistration|Bruce Momjian|reviewers=Magnus Hagander}}&lt;br /&gt;
{{comment|Magnus|Needs more work, comments {{messageLink|490EEF2D.2050703@hagander.net|here}}}}&lt;br /&gt;
{{comment|alvherre|Bruce posted a {{messageLink|200811050502.mA552TJ20677@momjian.us|new version}}, but it still {{messageLink|20081107201029.GF5507@alvh.no-ip.org|needs some work}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48F04B7C.3080303@benedekl.tvnetwork.hu|pg_dump roles support|Benedek Laszlo|reviewers=Ibrar Ahmed|Status=Waiting for Author}}&lt;br /&gt;
{{comment|alvherre|there&#039;s an {{messageLink|4912FA4E.1090000@benedekl.tvnetwork.hu|updated patch}}, and some extra {{messageLink|20081107202000.GG5507@alvh.no-ip.org|comments}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490878AC.1@dunslane.net|parallel restore|status=WIP|Andrew Dunstan|reviewers=Kenneth Marshall}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
{{patch|03c301c91737$be5a2a30$0e01a8c0@IBMC9A0F63B40D|Solve a problem of LC_TIME of windows|Hiroshi Saito}}&lt;br /&gt;
{{comment|tgl|updated version {{messageLink|2C940A1672E743439355545C5DB15786@HIRO57887DE653|here}}}}&lt;br /&gt;
{{comment|itagaki|comments and updated version {{messageLink|20081104094301.7EE8.52131E4D@oss.ntt.co.jp|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|BLU110-W38CE0A22D467A8C3D9736CFF540@phx.gbl|Support PLUGINS lines in Makefiles, similar to MODULES|Asif Naeem}}&lt;br /&gt;
{{comment|Dave Page|This doesn&#039;t work with the edb-debugger plugin, which is the only such plugin around AFAIK. It needs to ignore comments on the PLUGINS line, and handle multiple targets (plugin_debugger, pldbgapi, targetinfo etc). Not sure if we want that complexity though.}}&lt;br /&gt;
{{comment|Heikki|Unix-makefile version: {{messageLink|BLU110-W57823CEB7DC113354471EFF3B0@phx.gbl|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48F53EC0.3020004@timbira.com|autovacuum and reloption|status=WIP|Euler Taveira de Oliveira|reviewers=Alvaro Herrera}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49097338.2070700@gmail.com|SQL/MED compatible connection manager|Martin Pihlak|status=WIP}}&lt;br /&gt;
{{comment|Martin Pihlak|Updated patch {{messageLink|49142C02.8020706@gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081029164000.GL27466@fetter.org|pre-MED|David Fetter|reviewers=Alex Hunsaker|status=Waiting on author}}&lt;br /&gt;
{{comment|David Fetter|Updated patch {{messageLink|20081031144852.GF15545@fetter.org|here}}}}&lt;br /&gt;
{{review|34d269d40811031902p1d73d177w9f2e721ae169e8be@mail.gmail.com|alexhun|few questions and tgl had some constructive {{messageLink|24867.1225819435@sss.pgh.pa.us|comments}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|f205bb120810280833x340324d3m19a4f8aa65d822b@mail.gmail.com|FAQ_Solaris 1.28 to spanish|Emanuel CALVO FRANCO|reviewers=Peter Eisentraut}}&lt;br /&gt;
&lt;br /&gt;
{{CommitFestEndSection}}&lt;br /&gt;
&lt;br /&gt;
== Committed patches ==&lt;br /&gt;
{{CommitFestSectionNew}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20080803.114711.73374027.t-ishii@sraoss.co.jp|Common Table Expressions|Yoshiyuki Asaba|status=Committed 2008-10-04|reviewers=Jeff Davis}}&lt;br /&gt;
{{comment|David Fetter|README is {{messageLink|20080818.163852.105172778.t-ishii@sraoss.co.jp|here.}}}}&lt;br /&gt;
{{comment|David Fetter|Git repository is [http://git.postgresql.org/git/~davidfetter/cte/.git here.]}}&lt;br /&gt;
{{comment|David Fetter|[[CTEReadme]]}}&lt;br /&gt;
{{comment|David Fetter|[[CTESQLStandard| Fair Use from the draft SQL:2008 standard (WIP)]]}}&lt;br /&gt;
{{review|13449.1221589943@sss.pgh.pa.us|tgl|needs a good bit of work yet}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.GSO.4.64.0809152349440.19910@westnet.com|Add default_val to pg_settings|status=Committed 2008-10-06|Greg Smith|reviewers=Simon Riggs,Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081016102603.897D.52131E4D@oss.ntt.co.jp|Noisy _dosmaperror|status=Committed 2008-10-16|Takahiro Itagaki|reviewers=Tom Lane}}&lt;br /&gt;
&lt;br /&gt;
{{patch|b4e5ce320810151918g2acf69ebh9f80f4f2e1c203a0@mail.gmail.com|Memory leak on hashed agg rescan|status=Committed 2008-10-16|Neil Conway|reviewers=Tom Lane}}&lt;br /&gt;
{{review|10455.1224160007@sss.pgh.pa.us|Tom Lane|move some logic to separate function}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1223383838.4747.154.camel@ebony.2ndQuadrant|Atomic subtransaction commit|status=Committed 2008-10-20|Simon Riggs|reviewers=Alvaro Herrera}} &lt;br /&gt;
&lt;br /&gt;
{{patch|3327.1224535092@sss.pgh.pa.us|add placeholder variables to planner|status=Committed 2008-10-22|Tom Lane}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48E271C5.7010907@hagander.net|pg_hba options parsing|status=Committed 2008-10-23|Magnus Hagander|reviewers=Bruce Momjian}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|48F0DE8B.8030004@hagander.net|updated patch}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48FC3994.8040809@hagander.net|libpq ssl -&amp;gt; clear fallback looses error messages|status=Committed 2008-10-27|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905D22D.9040001@hagander.net|better hba parsing error messages|status=Committed 2008-10-27|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905A1DE.5030102@hagander.net|remove crypt authentication|status=Committed 2008-10-28|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905F515.3020208@gmx.net|Unicode escapes in literals|status=Committed 2008-10-29|Peter Eisentraut}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490A138E.80100@enterprisedb.com|User defined I/O conversion casts|status=Committed 2008-10-31|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49085327.5010608@enterprisedb.com|Updating FSM on recovery|status=Committed 2008-10-31|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.BSO.4.64.0810271955030.28764@leary.csoft.net|use new heap_(form/deform/modify)_tuple API|Kris Jurka|reviewers=Zdenek Kotala|status=Committed 2008-11-01}}&lt;br /&gt;
{{comment|Zdenek Kotala| It seems OK. Needs apply also {{messageLink|Pine.BSO.4.64.0810281721500.6833@leary.csoft.net|pfree patch.}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.BSO.4.64.0810281622240.9851@leary.csoft.net|don&#039;t use MAKE_PTR/OFFSET for shmem pointers|Kris Jurka|reviewers=Tom Lane|status=Committed 2008-11-02}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48C181D4.8030807@gmail.com|reducing statistics write overhead|Martin Pihlak|reviewers=Tom Lane|status=Committed 2008-11-02}}&lt;br /&gt;
{{comment|Martin Pihlak|Latest patch {{messageLink|48C594D8.6050504@gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|37ed240d0809030015u73b65b66v70fd76741317c6f5@mail.gmail.com|pg_typeof()|Brendan Jurd|reviewers=Kurt Harriman|status=Committed 2008-11-03}}&lt;br /&gt;
{{comment|Kurt Harriman|{{messageLink|http://archives.postgresql.org/pgsql-hackers/2008-11/msg00080.php|Updated patch}} is ready to commit if there is no objection}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.BSO.4.64.0810081931240.11647@leary.csoft.net|Fixes for psql describeOneTableDetails|Kris Jurka|reviewers=Tom Lane|status=Committed 2008-11-03}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48E22CF5.4050503@sun.com|PageGetTempPage cleanup |Zdenek Kotala|reviewers=Tom Lane|status=Committed 2008-11-03}}&lt;br /&gt;
{{comment|Zdenek Kotala|Original discussion {{messageLink|4938.1217862947@sss.pgh.pa.us|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810092009s1312d30bxc854cdfb5d9fed7e@mail.gmail.com|Allow the UUID type to accept non-standard formats|Robert Haas|reviewers=Peter Eisentraut|status=Committed 2008-11-03}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810101937n776c1e7cvd6a12345b0bbda28@mail.gmail.com|array_ndims|Robert Haas|reviewers=Peter Eisentraut|status=Committed 2008-11-04}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810282045g7fa6bdf9p53f03114d49643d7@mail.gmail.com|bulk inserts - keep most recent page pinned|Robert Haas|reviewers=Tom Lane|status=Committed 2008-11-06}}&lt;br /&gt;
{{comment|Robert Haas|based on work by Simon Riggs: [http://archives.postgresql.org/pgsql-hackers/2008-02/msg01080.php original idea],[http://archives.postgresql.org/pgsql-patches/2008-02/msg00140.php original patch], [http://archives.postgresql.org/pgsql-patches/2008-02/msg00154.php Tom Lane&#039;s comments]}}&lt;br /&gt;
{{comment|Robert Haas|Tom&#039;s comments on my [http://archives.postgresql.org/pgsql-hackers/2008-10/msg01276.php design proposal] are {{messageLink|17996.1225049097@sss.pgh.pa.us|here}}}}&lt;br /&gt;
{{comment|Robert Haas|patch {{messageLink|603c8f070811011023n202aea33w4da13b7d14f74134@mail.gmail.com|v2}}, adjusting for Heikki&#039;s changes to the ReadBuffer interface}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490394B7.6090503@lelarge.info|ALTER DATABASE SET TABLESPACE Statement|Guillaume Lelarge|reviewers=Bernd Helmle|status=Committed 2008-11-07}}&lt;br /&gt;
{{comment|Bernd Helmle|Syntax discussion and updated version {{messageLink|C0F6602797884925406AB88F@imhotep.credativ.de|here}}}}&lt;br /&gt;
{{comment|Guillaume Lelarge|Updated version with SET syntax {{messageLink|4910E46E.4010000@lelarge.info|here}}}}&lt;br /&gt;
{{comment|Bernd Helmle|Updated version from Guillaume {{messageLink|4912C88A.2070808@lelarge.info|here}}}}&lt;br /&gt;
{{comment|Guillaume Lelarge|Updated version {{messageLink|49140181.3000903@lelarge.info|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|0BD2E4E9-AF5A-4B4F-B546-027424EE8FAD@kineticode.com|Tests citext casts|David Wheeler|reviewers=&lt;br /&gt;
Kenneth Marshall|status=Committed 2008-11-07}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48D15471.6080305@cheapcomplexdevices.com|SQL Standard Interval output and IntervalStyle GUC|Ron Mayer|status=Committed 2008-11-08|reviewers=Brendan Jurd}}&lt;br /&gt;
{{comment|Ron Mayer|Early updates {{messageLink|48D52E48.406@cheapcomplexdevices.com|here}},   {{messageLink|48E49BDC.4090402@cheapcomplexdevices.com|here}}, and [http://0ape.com/postgres_interval_patches/ here]. Mostly related to GUC changes.}}&lt;br /&gt;
{{review|37ed240d0811032122u56db1959h91f53bbb9733c90d@mail.gmail.com|BJ|Bug in output, stylistic suggestions}}&lt;br /&gt;
{{comment|the mailing list|Feedback from {{messageLink|19477.1225814409@sss.pgh.pa.us|Tom L}} and {{messageLink|49101C94.EE98.0025.0@wicourts.gov|Kevin G}} about mixed-sign intervals}}&lt;br /&gt;
{{comment|Ron Mayer|Updated patch {{messageLink|4910B1DB.4000000.cheapcomplexdevices@com|here}} to fix -12:01:-30 bug and style suggestions from the review and to attempt to address feedback about mixed-sign intervals with doc updates.}}&lt;br /&gt;
{{review|37ed240d0811042102q78df5b86t2ff2092a75d371d7@mail.gmail.com|BJ|One last typo in docs but otherwise all good; review complete}}&lt;br /&gt;
{{review|28915.1226109473@sss.pgh.pa.us|Tom L|Tom pointed out issues with pg_dump and restore into databases with a different interval style}}&lt;br /&gt;
{{comment|Ron Mayer|{{messageLink|4915AC0A.9070608@cheapcomplexdevices.com|Speculating}} if an analogy with standard_conforming_strings applies to how we can handle dump/restore.}}&lt;br /&gt;
&lt;br /&gt;
{{CommitFestEndSection}}&lt;br /&gt;
&lt;br /&gt;
== Returned with Feedback ==&lt;br /&gt;
{{CommitFestSectionNew}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1225010283.21241.33.camel@localhost.localdomain|new correlation metric|Jeff Davis|reviewers=Brendan Jurd|status=Pending rework}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49086E4C.9030602@sun.com|htup and bufpage API clean up|Zdenek Kotala|reviewers=Robert Haas|status=Needs different approach}}&lt;br /&gt;
{{comment|Zdenek Kotala|New version is {{messageLink|490875FA.4020709@sun.com|here}}}}&lt;br /&gt;
{{review|603c8f070811031822q7d3b33f7x8576b7028f498cc4@mail.gmail.com|Robert Haas|proposed API seems too costly and fragile}}&lt;br /&gt;
&lt;br /&gt;
{{CommitFestEndSection}}&lt;br /&gt;
&lt;br /&gt;
== Round Robin Reviewers ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; cellspacing=&amp;quot;0&amp;quot; style=&amp;quot;width: 60%; border-collapse: collapse; border: 1px solid #ccc; font-size: 90%;&amp;quot;&lt;br /&gt;
|- style=&amp;quot;background: #eee;&amp;quot;&lt;br /&gt;
! width=&amp;quot;30%&amp;quot; | Name&lt;br /&gt;
!Status&lt;br /&gt;
!Reviewing&lt;br /&gt;
!Completed&lt;br /&gt;
|-&lt;br /&gt;
|Brendan Jurd || Available || 2 || 2&lt;br /&gt;
|-&lt;br /&gt;
|Jaime Casanova || Available || 1 || 1&lt;br /&gt;
|-&lt;br /&gt;
|Stephen Frost || Available 11/15 || 0 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Jeff Davis || Available || 2 || 1&lt;br /&gt;
|-&lt;br /&gt;
|Greg Stark || Unknown || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Abhijit Menon-Sen || Unknown || 0 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Alex Hunsaker || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Markus Wanner || Cherry-picking || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Ibrar Ahmed || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|D&#039;Arcy Cain || Unknown || 0 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Kenneth Marshall || Available || 1 || 1&lt;br /&gt;
|-&lt;br /&gt;
|Robert Haas || Available || 1 || 4&lt;br /&gt;
|-&lt;br /&gt;
|Matthew Wetmore || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Gianni Colli || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|&amp;quot;Unicron&amp;quot; || Available || 1 || 1&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=CommitFest_2008-11&amp;diff=3399</id>
		<title>CommitFest 2008-11</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=CommitFest_2008-11&amp;diff=3399"/>
		<updated>2008-11-07T16:45:49Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* SQL language features */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__TOC__&lt;br /&gt;
&lt;br /&gt;
This is the page for the CommitFest starting &#039;&#039;&#039;2008 November&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Managers for this CommitFest are Josh Berkus (josh-at-agliodbs-com) and Dave Page (dpage-at-pgadmin-org).&lt;br /&gt;
&lt;br /&gt;
{{CommitFestCurrent}}&lt;br /&gt;
&lt;br /&gt;
== Pending patches ==&lt;br /&gt;
{{CommitFestSectionNew}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
=== SE-PostgreSQL and related ===&lt;br /&gt;
&lt;br /&gt;
{{patch|4863B3DA.8030209@kaigai.gr.jp|SE-PostgreSQL patches|Kaigai Kohei}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|48F71E36.9010203@ak.jp.nec.com|latest version}}, now with 6 patches}}&lt;br /&gt;
{{comment|KaiGai|[[SEPostgreSQL]] is a draft of comprehensive document}}&lt;br /&gt;
{{comment|KaiGai|{{messageLink|49140871.4050906@ak.jp.nec.com|latest patches (r1197)}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20080901063855.GJ16005@tamriel.snowman.net|Column-level Permissions|Stephen Frost|status=Pending Review|reviewers=Markus Wanner}}&lt;br /&gt;
{{comment|Stephen Frost|Updated patch {{messageLink|20080902221823.GL16005@tamriel.snowman.net|here}}}}&lt;br /&gt;
{{review|48DB48AC.5010400@bluegap.ch|Markus Wanner|Awaiting updated patch.}}&lt;br /&gt;
{{comment|Stephen Frost|Updated patch, again, {{messageLink|20081102034517.GR4452@tamriel.snowman.net|here}}}}&lt;br /&gt;
{{comment|Stephen Frost|Updated patch, fixes case where unprivileged user can get row count, {{messageLink|20081102131332.GU4452@tamriel.snowman.net|here}}}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Recovery, Replication, Hot Standby ===&lt;br /&gt;
&lt;br /&gt;
{{patch|1220213074.4371.173.camel@ebony.2ndQuadrant|Infrastructure changes for recovery|status=Pending Review|Simon Riggs|reviewers=Tom Lane, Heikki Linnakangas}} &lt;br /&gt;
{{comment|sriggs| important patch for other work}}&lt;br /&gt;
{{comment|tgl|some comments {{messageLink|1905.1220895241@sss.pgh.pa.us|here}}}}&lt;br /&gt;
{{comment|tgl|updated patch {{messageLink|1221080797.3913.768.camel@ebony.2ndQuadrant|here}}, still being tested}}&lt;br /&gt;
{{comment|tgl|Simon found {{messageLink|1221725145.3913.2315.camel@ebony.2ndQuadrant|some issues}}}}&lt;br /&gt;
{{comment|tgl|{{messageLink|1222184541.4445.400.camel@ebony.2ndQuadrant|patch v7}} here}}&lt;br /&gt;
{{comment|tgl|it&#039;s still got {{messageLink|28973.1222381719@sss.pgh.pa.us|issues}}}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1222815151.4445.1397.camel@ebony.2ndQuadrant|patch v8}} here}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1223472898.4747.310.camel@ebony.2ndQuadrant|patch v9}} here, in response to {{messageLink|48EC9CC5.6060803@enterprisedb.com|Heikki&#039;s review}}}}&lt;br /&gt;
{{comment|sriggs|some issues overlooked, fixed as part of Hot Standby patch only at present}}&lt;br /&gt;
{{comment|sriggs|do we want this split out again as a separate patch for easier review?}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1225557138.3971.673.camel@ebony.2ndQuadrant|Hot Standby - queries during archive recovery|status=Pending Review|Simon Riggs}}&lt;br /&gt;
{{comment|sriggs| v5d now available, fixing all Mark&#039;s reported issues. Main parts are fully reviewable}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1223472186.4747.301.camel@ebony.2ndQuadrant|pg_stop_backup wait bug fix|Simon Riggs}}&lt;br /&gt;
{{comment|Robert Haas|sriggs extracted this from recovery infrastructure patch per {{messageLink|48EC9CC5.6060803@enterprisedb.com|Heikki&#039;s suggestion}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch||pg_start_backup checkpoint issue|Simon Riggs}}&lt;br /&gt;
{{comment|sriggs|separated out from Infrastructure changes patch per {{messageLink|48EC9CC5.6060803@enterprisedb.com|Heikki&#039;s suggestion}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1220174867.4371.107.camel@ebony.2ndQuadrant|rmgr hooks and contrib/rmgr_hook|status=Waiting on dependencies|Simon Riggs}} &lt;br /&gt;
{{comment|sriggs| deferrable, if required}}&lt;br /&gt;
{{comment|tgl|I think the plan is for this to wait till &amp;quot;infrastructure&amp;quot; patch goes in}}&lt;br /&gt;
&lt;br /&gt;
{{patch|3f0b79eb0810310436w360f0afdy76ff1499b177ce0d@mail.gmail.com|Synchronous log-shipping replication|Masao Fujii|reviewers=Heikki Linnakangas, Simon Riggs}}&lt;br /&gt;
{{comment|fujii|{{messageLink|3f0b79eb0811040404r799d3170v5bb9f201000f1771@mail.gmail.com|signal handling patch v2}} here}}&lt;br /&gt;
{{comment|fujii|{{messageLink|3f0b79eb0811050617o3237130awb4aec1d3a2daacab@mail.gmail.com|walsender process patch v1}} here}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Upgrade-in-place and related issues === &lt;br /&gt;
&lt;br /&gt;
{{patch|490B7C1B.8050408@sun.com|In-place online upgrade|status=Waiting for new version|Zdenek Kotala|reviewers=Robert Haas}}&lt;br /&gt;
{{comment|Zdenek Kotala|This patch requires &amp;quot;htup and bufpage API clean up&amp;quot; and &amp;quot;HeapTuple version extension&amp;quot; patches. Git repository is [http://git.postgresql.org here] }}&lt;br /&gt;
{{review|603c8f070811022022x582a9cbdp60798a6b87910edf@mail.gmail.com|Robert Haas|preliminary comments, still need a clean diff}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48F1FC7E.1060406@sun.com|Extending pg_class info + more flexible TOAST chunk size|Zdenek Kotala|reviewers=Robert Haas|status=Waiting for new version}}&lt;br /&gt;
{{comment|tgl|seems it&#039;d be better to make TOAST chunks work like {{messageLink|490AB654.6040409@enterprisedb.com|this}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4909DFCE.1000702@sun.com|HeapTuple version extension + code cleanup|Zdenek Kotala|reviewers=Robert Haas|status=Waiting for new version}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== SQL language features ===&lt;br /&gt;
&lt;br /&gt;
{{patch|e08cc0400810270912u49a6ec83vc23984c01f368f76@mail.gmail.com|Window Functions|Hitoshi Harada|reviewers=Heikki Linnakangas, David Rowley}}&lt;br /&gt;
{{comment|Hitoshi Harada|updated patch is {{messageLink|e08cc0400810310721l22a6bb7kb6a300ce66443806@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Hitoshi Harada|the latest patch is {{messageLink|e08cc0400811070746p43553f10s6bb09e98b7eafc3b@mail.gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|162867790810170316l4eeecb0bq321dd771f8f4e661@mail.gmail.com|grouping sets|status=WIP|Pavel Stehule|reviewers=Ibrar Ahmed}}&lt;br /&gt;
{{comment|Pavel Stehule| doc and notes [[Grouping Sets]]}}&lt;br /&gt;
&lt;br /&gt;
{{patch|162867790810260428p56d16352qa1ec5c4c5330f25c@mail.gmail.com|default values for function&#039;s parameters|Pavel Stehule|reviewers=Peter Eisentraut}}&lt;br /&gt;
{{comment|Pavel Stehule| fix known bugs, currently only doc should be finished}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070808070503jd7be083kcce3e16345affb08@mail.gmail.com|add columns via CREATE OR REPLACE VIEW|Robert Haas|reviewers=Bernd Helmle}}&lt;br /&gt;
{{comment|Robert Haas|some further justification of the proposed design {{messageLink|603c8f070808070956t1ab98dcdr933575eb096e4c28@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Robert Haas|questions about how to move forward {{messageLink|603c8f070810031839y7ce9a852o86effbab9fd6dd9b@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Robert Haas|a {{messageLink|482096EC.3000805@dunslane.net|similar feature request}} from Andrew Dunstan}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490394B7.6090503@lelarge.info|ALTER DATABASE WITH TABLESPACE Statement|Guillaume Lelarge|reviewers=Bernd Helmle}}&lt;br /&gt;
{{comment|Bernd Helmle|Syntax discussion and updated version {{messageLink|C0F6602797884925406AB88F@imhotep.credativ.de|here}}}}&lt;br /&gt;
{{comment|Guillaume Lelarge|Updated version with SET syntax {{messageLink|4910E46E.4010000@lelarge.info|here}}}}&lt;br /&gt;
{{comment|Bernd Helmle|Updated version from Guillaume {{messageLink|4912C88A.2070808@lelarge.info|here}}}}&lt;br /&gt;
{{comment|Guillaume Lelarge|Updated version {{messageLink|49140181.3000903@lelarge.info|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48EFA13C.2060407@frogthinker.org|Prepared transactions and temp tables|Emmanuel Cecchet|reviewers=Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4909726F.8000800@gmx.net|TABLE command|Peter Eisentraut|status=Ready for Code Review|reviewers=Unicron}}&lt;br /&gt;
{{comment|Unicron|Patch {{messageLink|850603.14426.qm@web62408.mail.re1.yahoo.com|works per specification}} }}&lt;br /&gt;
&lt;br /&gt;
{{patch|490AFC08.8040500@Sun.COM|Distinct types|Peter Eisentraut|status=Waiting for Author}}&lt;br /&gt;
{{comment|Bernd Helmle|Patch needs further work regarding {{messageLink|17750.1225571886@sss.pgh.pa.us|indexing}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|2849137C693B65CC8E86411C@imhotep.credativ.de|Automatic view update rules|status=WIP|Bernd Helmle|reviewers=Unicron}}&lt;br /&gt;
{{comment|Bernd Helmle|New version with RETURNING support {{messageLink|94CF655A8D0DC7D5B4B81D8B@imhotep.credativ.de|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1225543926.8122.14.camel@huvostro|Enable pl/python to return records based on multiple OUT params|status=Waiting on author|Hannu Krosing}}&lt;br /&gt;
{{comment|Robert Haas|Hannu is {{messageLink|1225781532.7597.19.camel@huvostro|working on a new version}}}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Datatypes ===&lt;br /&gt;
&lt;br /&gt;
{{patch|48D15471.6080305@cheapcomplexdevices.com|SQL Standard Interval output and IntervalStyle GUC|Ron Mayer|status=Ready for committer|reviewers=Brendan Jurd}}&lt;br /&gt;
{{comment|Ron Mayer|An update {{messageLink|48D52E48.406@cheapcomplexdevices.com|here}} fixed some bugs in GUC setting.}}&lt;br /&gt;
{{comment|Ron Mayer|Another update {{messageLink|48E49BDC.4090402@cheapcomplexdevices.com|here}}, brought up-to-date with HEAD}}&lt;br /&gt;
{{comment|Ron Mayer|Brought up-to-date with head [http://0ape.com/postgres_interval_patches/ here]. Now allows setting IntervalStyle through an environment variable because pg_regress had set interval styles (as a side-effect of setting DateStyles) through the environment, some minor cleanup.}}&lt;br /&gt;
{{review|37ed240d0811032122u56db1959h91f53bbb9733c90d@mail.gmail.com|BJ|Bug in output, stylistic suggestions}}&lt;br /&gt;
{{comment|the mailing list|Feedback from {{messageLink|19477.1225814409@sss.pgh.pa.us|Tom L}} and {{messageLink|49101C94.EE98.0025.0@wicourts.gov|Kevin G}} about mixed-sign intervals}}&lt;br /&gt;
{{comment|Ron Mayer|Updated patch {{messageLink|4910B1DB.4000000.cheapcomplexdevices@com|here}} to fixe bug and style suggestions from the review and to attempt to address feedback about mixed-sign intervals with doc updates.}}&lt;br /&gt;
{{review|37ed240d0811042102q78df5b86t2ff2092a75d371d7@mail.gmail.com|BJ|One last typo in docs but otherwise all good; review complete}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48E4A30C.3000503@cheapcomplexdevices.com|ISO 8601 interval literal input and output|Ron Mayer|reviewers=Brendan Jurd|status=Waiting for response}}&lt;br /&gt;
{{comment|Ron Mayer|Note that this patch doesn&#039;t apply directly to HEAD, but depends on the IntervalStyle GUC patch to be applied first.}}&lt;br /&gt;
{{comment|Ron Mayer|The initial (2003) version of this patch along with a thread which explains the feature a bit more can be found [http://archives.postgresql.org/pgsql-patches/2003-09/msg00103.php here].}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|490BA342.7010300@cheapcomplexdevices.com|latest version}}}}&lt;br /&gt;
{{comment|Ron Mayer|Latest version [http://0ape.com/postgres_interval_patches/ here] that matches the latest version of the IntervalStyle patch that can be found elsewhere on this page.}}&lt;br /&gt;
{{review|37ed240d0811050750v11726fd1of441646f87b583da@mail.gmail.com|BJ|Code style and documentation suggestions}}&lt;br /&gt;
{{comment|Ron Mayer|Update here [http://0ape.com/postgres_interval_patches/ here] that fixes style &amp;amp; docs; as well as a bug where the ISO8601 spec wasn&#039;t quite followed (an optional field was treated as required by previous patches).}}&lt;br /&gt;
{{review|37ed240d0811062058n752c3880kb04feb85e355b524@mail.gmail.com|BJ|Query behaviour of &#039;P0001&#039;, final doc cleanup suggestions}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48CEDE68.7090501@cheapcomplexdevices.com|Interval rounding consistency|Ron Mayer|reviewers=Brendan Jurd}}&lt;br /&gt;
{{comment|Ron Mayer|Patch 3 [http://0ape.com/postgres_interval_patches/ here] refactors the interval code to remove much of the copy&amp;amp;paste in DecodeInterval and EncodeInterval with the side effect of making interval rounding more consistent between styles.  This patch applies on top of the IntervalStyle patch and the ISO 8601 Interval patch.}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20952F54-6730-49D8-99A3-1834697790B5@decibel.org|array_length|Jim C. Nasby|reviewers=Peter Eisentraut}}&lt;br /&gt;
{{comment|Robert Haas|I have {{messageLink|603c8f070811062006q4f20b2bq179d4d2ffec65690@mail.gmail.com|reimplemented this in C}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810151933p445978b3td481a5422a2aebf4@mail.gmail.com|array_agg/array_accum|Robert Haas|reviewers=Peter Eisentraut}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1225045937.4434.21.camel@localhost.localdomain|another version}} and {{messageLink|1225682527.1375.150.camel@jdavis|another one}} from Jeff Davis}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Indexes ===&lt;br /&gt;
&lt;br /&gt;
{{patch|490B07BA.6030109@sigaev.ru|GIN fast insert|Teodor Sigaev, Oleg Bartunov}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490B3752.3010800@sigaev.ru|B-Tree emulation for GIN|status=WIP|Teodor Sigaev, Oleg Bartunov}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081101000154.GO27872@fune|On-disk bitmap indexes|status=WIP|Gabriele Bartolini, Gianni Ciolli|reviewers=Greg Stark (more welcome!)}}&lt;br /&gt;
{{review|49130E72.1000803@sigaev.ru|Teodor Sigaev|several bugs}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Performance ===&lt;br /&gt;
&lt;br /&gt;
{{patch|6EEA43D22289484890D119821101B1DF2C1683@exchange20.mercury.ad.ubc.ca|Improve Performance of Multi-Batch Hash Join for Skewed Data Sets|Ramon Lawrence/Bryce Cutt|reviewers=Joshua Tolley}}&lt;br /&gt;
{{comment|Joshua Tolley|[http://archives.postgresql.org/pgsql-hackers/2008-11/msg00286.php] reports backend crash}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4909B326.507@enterprisedb.com|Optimizing COPY with memchr()|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|87ljw5c0lx.fsf@oxford.xeocode.com|posix_fadvise|Gregory Stark}}&lt;br /&gt;
&lt;br /&gt;
{{patch|a778a7260810280033n43f70d36x8c437eacf9a5461e@mail.gmail.com|Proposal of PITR performance improvement|Koichi Suzuki|reviewers=Simon Riggs}}&lt;br /&gt;
&lt;br /&gt;
{{patch|36e682920811021349h7202bdecpd7a45c8a8038465e@mail.gmail.com|Hash Join-Filter Pruning using Bloom Filters|status=WIP|Jonah Harris}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Improving admin experience ===&lt;br /&gt;
&lt;br /&gt;
{{patch|4905AE17.7090305@enterprisedb.com|Visibility map, partial vacuums|status=WIP|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081029183248.GE4331@alvh.no-ip.org|Block-level CRC checks|Alvaro Herrera|status=WIP}}&lt;br /&gt;
&lt;br /&gt;
{{patch|c2ee6dbd0810100553gd328275ue2eb6e14bee70a8@mail.gmail.com|adding VERBOSE option to CLUSTER|Jim Cox|reviewers=Peter Eisentraut}}&lt;br /&gt;
&lt;br /&gt;
{{patch|a301bfd90810310750pf108c69x36499546f406650f@mail.gmail.com|Auto Partitioning Patch|Nikhil Sontakke|reviewers=Jaime Casanova}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1223379173.4747.145.camel@ebony.2ndQuadrant|Reducing some DDL Locks to ShareLock|status=Pending Review|Simon Riggs}} &lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1722552592.7.1224882093461.JavaMail.root@spotone|ddl_lock_reduce.v4.patch}}}}&lt;br /&gt;
{{comment|sriggs|agreed rework to implement pg_domain constraint, but the main patch still needs review}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
=== Connection management ===&lt;br /&gt;
&lt;br /&gt;
{{patch|48FC7E84.3080702@hagander.net|SSL cleanups/hostname verification|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49009D67.4040202@hagander.net|clientcert option for pg_hba|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49076F39.1080502@hagander.net|regexp support in usermaps|Magnus Hagander|reviewers=Gianni Colli}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Contrib modules ===&lt;br /&gt;
&lt;br /&gt;
{{patch|0BD2E4E9-AF5A-4B4F-B546-027424EE8FAD@kineticode.com|Tests citext casts|David Wheeler|reviewers=&lt;br /&gt;
Kenneth Marshall}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081106171139.8D21.52131E4D@oss.ntt.co.jp|contrib infrastructures|Martin Pihlak, Takahiro Itagaki|reviewers=Jeff Davis, Matthew Wetmore}}&lt;br /&gt;
{{comment|Itagaki|contains {{messageLink|490A00A8.7050708@gmail.com|QueryDesc}}, {{messageLink|20081009165157.9BE4.52131E4D@oss.ntt.co.jp|explain}} and {{messageLink|20081027171917.ADD6.52131E4D@oss.ntt.co.jp|hooks}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081009165157.9BE4.52131E4D@oss.ntt.co.jp|contrib/auto_explain|Takahiro Itagaki|reviewers=Jeff Davis}}&lt;br /&gt;
{{comment|Itagaki|nested statements handling is {{messageLink|48FCA095.8020709@gmail.com|requested}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081011172450.3402.52131E4D@oss.ntt.co.jp|contrib/pg_stat_statements|Takahiro Itagaki|reviewers=Matthew Wetmore}}&lt;br /&gt;
{{comment|Itagaki|{{messageLink|20081027171917.ADD6.52131E4D@oss.ntt.co.jp|latest patch versions}}}}&lt;br /&gt;
{{comment|Itagaki|{{messageLink|1d709ecc0811011343lf65f58fjb2e96194f4c2ecc5@mail.gmail.com|comments}} from Vladimir}}&lt;br /&gt;
&lt;br /&gt;
{{patch|e4ccc24e0810222010p12bae2f4xa3a11cb2bc51bd89@mail.gmail.com|pg_standby support for compressed segments|Charles Duffy|reviewers=Simon Riggs}}&lt;br /&gt;
{{comment|Simon Riggs|Deferring review for a few weeks until we get a better picture of streaming replication requirements for 8.4}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.GSO.4.64.0811012101220.17619@westnet.com|Simple postgresql.conf wizard|Greg Smith|reviewers=Josh Berkus}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
=== Clients ===&lt;br /&gt;
&lt;br /&gt;
{{patch|200810271936.m9RJaGW09544@momjian.us|libpq callback unregistration|Bruce Momjian|reviewers=Magnus Hagander}}&lt;br /&gt;
{{comment|Magnus|Needs more work, comments {{messageLink|490EEF2D.2050703@hagander.net|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48F04B7C.3080303@benedekl.tvnetwork.hu|pg_dump roles support|Benedek Laszlo|reviewers=Ibrar Ahmed|Status=Waiting for Author}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490878AC.1@dunslane.net|parallel restore|status=WIP|Andrew Dunstan}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
{{patch|03c301c91737$be5a2a30$0e01a8c0@IBMC9A0F63B40D|Solve a problem of LC_TIME of windows|Hiroshi Saito}}&lt;br /&gt;
{{comment|tgl|updated version {{messageLink|2C940A1672E743439355545C5DB15786@HIRO57887DE653|here}}}}&lt;br /&gt;
{{comment|itagaki|comments and updated version {{messageLink|20081104094301.7EE8.52131E4D@oss.ntt.co.jp|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|BLU110-W38CE0A22D467A8C3D9736CFF540@phx.gbl|Support PLUGINS lines in Makefiles, similar to MODULES|Asif Naeem}}&lt;br /&gt;
{{comment|Dave Page|This doesn&#039;t work with the edb-debugger plugin, which is the only such plugin around AFAIK. It needs to ignore comments on the PLUGINS line, and handle multiple targets (plugin_debugger, pldbgapi, targetinfo etc). Not sure if we want that complexity though.}}&lt;br /&gt;
{{comment|Heikki|Unix-makefile version: {{messageLink|BLU110-W57823CEB7DC113354471EFF3B0@phx.gbl|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48F53EC0.3020004@timbira.com|autovacuum and reloption|status=WIP|Euler Taveira de Oliveira|reviewers=Alvaro Herrera}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49097338.2070700@gmail.com|SQL/MED compatible connection manager|Martin Pihlak|status=WIP}}&lt;br /&gt;
{{comment|Martin Pihlak|Updated patch {{messageLink|490B28FA.4080101@gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081029164000.GL27466@fetter.org|pre-MED|David Fetter|reviewers=Alex Hunsaker|status=Waiting on author}}&lt;br /&gt;
{{comment|David Fetter|Updated patch {{messageLink|20081031144852.GF15545@fetter.org|here}}}}&lt;br /&gt;
{{review|34d269d40811031902p1d73d177w9f2e721ae169e8be@mail.gmail.com|alexhun|few questions and tgl had some constructive {{messageLink|24867.1225819435@sss.pgh.pa.us|comments}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|f205bb120810280833x340324d3m19a4f8aa65d822b@mail.gmail.com|FAQ_Solaris 1.28 to spanish|Emanuel CALVO FRANCO|reviewers=Peter Eisentraut}}&lt;br /&gt;
&lt;br /&gt;
{{CommitFestEndSection}}&lt;br /&gt;
&lt;br /&gt;
== Committed patches ==&lt;br /&gt;
{{CommitFestSectionNew}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20080803.114711.73374027.t-ishii@sraoss.co.jp|Common Table Expressions|Yoshiyuki Asaba|status=Committed 2008-10-04|reviewers=Jeff Davis}}&lt;br /&gt;
{{comment|David Fetter|README is {{messageLink|20080818.163852.105172778.t-ishii@sraoss.co.jp|here.}}}}&lt;br /&gt;
{{comment|David Fetter|Git repository is [http://git.postgresql.org/git/~davidfetter/cte/.git here.]}}&lt;br /&gt;
{{comment|David Fetter|[[CTEReadme]]}}&lt;br /&gt;
{{comment|David Fetter|[[CTESQLStandard| Fair Use from the draft SQL:2008 standard (WIP)]]}}&lt;br /&gt;
{{review|13449.1221589943@sss.pgh.pa.us|tgl|needs a good bit of work yet}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.GSO.4.64.0809152349440.19910@westnet.com|Add default_val to pg_settings|status=Committed 2008-10-06|Greg Smith|reviewers=Simon Riggs,Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081016102603.897D.52131E4D@oss.ntt.co.jp|Noisy _dosmaperror|status=Committed 2008-10-16|Takahiro Itagaki|reviewers=Tom Lane}}&lt;br /&gt;
&lt;br /&gt;
{{patch|b4e5ce320810151918g2acf69ebh9f80f4f2e1c203a0@mail.gmail.com|Memory leak on hashed agg rescan|status=Committed 2008-10-16|Neil Conway|reviewers=Tom Lane}}&lt;br /&gt;
{{review|10455.1224160007@sss.pgh.pa.us|Tom Lane|move some logic to separate function}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1223383838.4747.154.camel@ebony.2ndQuadrant|Atomic subtransaction commit|status=Committed 2008-10-20|Simon Riggs|reviewers=Alvaro Herrera}} &lt;br /&gt;
&lt;br /&gt;
{{patch|3327.1224535092@sss.pgh.pa.us|add placeholder variables to planner|status=Committed 2008-10-22|Tom Lane}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48E271C5.7010907@hagander.net|pg_hba options parsing|status=Committed 2008-10-23|Magnus Hagander|reviewers=Bruce Momjian}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|48F0DE8B.8030004@hagander.net|updated patch}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48FC3994.8040809@hagander.net|libpq ssl -&amp;gt; clear fallback looses error messages|status=Committed 2008-10-27|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905D22D.9040001@hagander.net|better hba parsing error messages|status=Committed 2008-10-27|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905A1DE.5030102@hagander.net|remove crypt authentication|status=Committed 2008-10-28|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905F515.3020208@gmx.net|Unicode escapes in literals|status=Committed 2008-10-29|Peter Eisentraut}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490A138E.80100@enterprisedb.com|User defined I/O conversion casts|status=Committed 2008-10-31|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49085327.5010608@enterprisedb.com|Updating FSM on recovery|status=Committed 2008-10-31|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.BSO.4.64.0810271955030.28764@leary.csoft.net|use new heap_(form/deform/modify)_tuple API|Kris Jurka|reviewers=Zdenek Kotala|status=Committed 2008-11-01}}&lt;br /&gt;
{{comment|Zdenek Kotala| It seems OK. Needs apply also {{messageLink|Pine.BSO.4.64.0810281721500.6833@leary.csoft.net|pfree patch.}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.BSO.4.64.0810281622240.9851@leary.csoft.net|don&#039;t use MAKE_PTR/OFFSET for shmem pointers|Kris Jurka|reviewers=Tom Lane|status=Committed 2008-11-02}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48C181D4.8030807@gmail.com|reducing statistics write overhead|Martin Pihlak|reviewers=Tom Lane|status=Committed 2008-11-02}}&lt;br /&gt;
{{comment|Martin Pihlak|Latest patch {{messageLink|48C594D8.6050504@gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|37ed240d0809030015u73b65b66v70fd76741317c6f5@mail.gmail.com|pg_typeof()|Brendan Jurd|reviewers=Kurt Harriman|status=Committed 2008-11-03}}&lt;br /&gt;
{{comment|Kurt Harriman|{{messageLink|http://archives.postgresql.org/pgsql-hackers/2008-11/msg00080.php|Updated patch}} is ready to commit if there is no objection}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.BSO.4.64.0810081931240.11647@leary.csoft.net|Fixes for psql describeOneTableDetails|Kris Jurka|reviewers=Tom Lane|status=Committed 2008-11-03}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48E22CF5.4050503@sun.com|PageGetTempPage cleanup |Zdenek Kotala|reviewers=Tom Lane|status=Committed 2008-11-03}}&lt;br /&gt;
{{comment|Zdenek Kotala|Original discussion {{messageLink|4938.1217862947@sss.pgh.pa.us|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810092009s1312d30bxc854cdfb5d9fed7e@mail.gmail.com|Allow the UUID type to accept non-standard formats|Robert Haas|reviewers=Peter Eisentraut|status=Committed 2008-11-03}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810101937n776c1e7cvd6a12345b0bbda28@mail.gmail.com|array_ndims|Robert Haas|reviewers=Peter Eisentraut|status=Committed 2008-11-04}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810282045g7fa6bdf9p53f03114d49643d7@mail.gmail.com|bulk inserts - keep most recent page pinned|Robert Haas|reviewers=Tom Lane|status=Committed 2008-11-06}}&lt;br /&gt;
{{comment|Robert Haas|based on work by Simon Riggs: [http://archives.postgresql.org/pgsql-hackers/2008-02/msg01080.php original idea],[http://archives.postgresql.org/pgsql-patches/2008-02/msg00140.php original patch], [http://archives.postgresql.org/pgsql-patches/2008-02/msg00154.php Tom Lane&#039;s comments]}}&lt;br /&gt;
{{comment|Robert Haas|Tom&#039;s comments on my [http://archives.postgresql.org/pgsql-hackers/2008-10/msg01276.php design proposal] are {{messageLink|17996.1225049097@sss.pgh.pa.us|here}}}}&lt;br /&gt;
{{comment|Robert Haas|patch {{messageLink|603c8f070811011023n202aea33w4da13b7d14f74134@mail.gmail.com|v2}}, adjusting for Heikki&#039;s changes to the ReadBuffer interface}}&lt;br /&gt;
&lt;br /&gt;
{{CommitFestEndSection}}&lt;br /&gt;
&lt;br /&gt;
== Returned with Feedback ==&lt;br /&gt;
{{CommitFestSectionNew}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1225010283.21241.33.camel@localhost.localdomain|new correlation metric|Jeff Davis|reviewers=Brendan Jurd|status=Pending rework}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49086E4C.9030602@sun.com|htup and bufpage API clean up|Zdenek Kotala|reviewers=Robert Haas|status=Needs different approach}}&lt;br /&gt;
{{comment|Zdenek Kotala|New version is {{messageLink|490875FA.4020709@sun.com|here}}}}&lt;br /&gt;
{{review|603c8f070811031822q7d3b33f7x8576b7028f498cc4@mail.gmail.com|Robert Haas|proposed API seems too costly and fragile}}&lt;br /&gt;
&lt;br /&gt;
{{CommitFestEndSection}}&lt;br /&gt;
&lt;br /&gt;
== Round Robin Reviewers ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; cellspacing=&amp;quot;0&amp;quot; style=&amp;quot;width: 60%; border-collapse: collapse; border: 1px solid #ccc; font-size: 90%;&amp;quot;&lt;br /&gt;
|- style=&amp;quot;background: #eee;&amp;quot;&lt;br /&gt;
! width=&amp;quot;30%&amp;quot; | Name&lt;br /&gt;
!Status&lt;br /&gt;
!Reviewing&lt;br /&gt;
!Completed&lt;br /&gt;
|-&lt;br /&gt;
|Brendan Jurd || Available || 2 || 2&lt;br /&gt;
|-&lt;br /&gt;
|Jaime Casanova || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Stephen Frost || Available 11/15 || 0 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Jeff Davis || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Greg Stark || Unknown || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Abhijit Menon-Sen || Unknown || 0 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Alex Hunsaker || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Markus Wanner || Cherry-picking || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Ibrar Ahmed || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|D&#039;Arcy Cain || Unknown || 0 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Kenneth Marshall || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Robert Haas || Available || 0 || 3&lt;br /&gt;
|-&lt;br /&gt;
|Matthew Wetmore || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Gianni Colli || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|&amp;quot;Unicron&amp;quot; || Available || 1 || 0&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=CommitFest_2008-11&amp;diff=3398</id>
		<title>CommitFest 2008-11</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=CommitFest_2008-11&amp;diff=3398"/>
		<updated>2008-11-07T16:45:19Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: /* SQL language features */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__TOC__&lt;br /&gt;
&lt;br /&gt;
This is the page for the CommitFest starting &#039;&#039;&#039;2008 November&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Managers for this CommitFest are Josh Berkus (josh-at-agliodbs-com) and Dave Page (dpage-at-pgadmin-org).&lt;br /&gt;
&lt;br /&gt;
{{CommitFestCurrent}}&lt;br /&gt;
&lt;br /&gt;
== Pending patches ==&lt;br /&gt;
{{CommitFestSectionNew}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
=== SE-PostgreSQL and related ===&lt;br /&gt;
&lt;br /&gt;
{{patch|4863B3DA.8030209@kaigai.gr.jp|SE-PostgreSQL patches|Kaigai Kohei}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|48F71E36.9010203@ak.jp.nec.com|latest version}}, now with 6 patches}}&lt;br /&gt;
{{comment|KaiGai|[[SEPostgreSQL]] is a draft of comprehensive document}}&lt;br /&gt;
{{comment|KaiGai|{{messageLink|49140871.4050906@ak.jp.nec.com|latest patches (r1197)}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20080901063855.GJ16005@tamriel.snowman.net|Column-level Permissions|Stephen Frost|status=Pending Review|reviewers=Markus Wanner}}&lt;br /&gt;
{{comment|Stephen Frost|Updated patch {{messageLink|20080902221823.GL16005@tamriel.snowman.net|here}}}}&lt;br /&gt;
{{review|48DB48AC.5010400@bluegap.ch|Markus Wanner|Awaiting updated patch.}}&lt;br /&gt;
{{comment|Stephen Frost|Updated patch, again, {{messageLink|20081102034517.GR4452@tamriel.snowman.net|here}}}}&lt;br /&gt;
{{comment|Stephen Frost|Updated patch, fixes case where unprivileged user can get row count, {{messageLink|20081102131332.GU4452@tamriel.snowman.net|here}}}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Recovery, Replication, Hot Standby ===&lt;br /&gt;
&lt;br /&gt;
{{patch|1220213074.4371.173.camel@ebony.2ndQuadrant|Infrastructure changes for recovery|status=Pending Review|Simon Riggs|reviewers=Tom Lane, Heikki Linnakangas}} &lt;br /&gt;
{{comment|sriggs| important patch for other work}}&lt;br /&gt;
{{comment|tgl|some comments {{messageLink|1905.1220895241@sss.pgh.pa.us|here}}}}&lt;br /&gt;
{{comment|tgl|updated patch {{messageLink|1221080797.3913.768.camel@ebony.2ndQuadrant|here}}, still being tested}}&lt;br /&gt;
{{comment|tgl|Simon found {{messageLink|1221725145.3913.2315.camel@ebony.2ndQuadrant|some issues}}}}&lt;br /&gt;
{{comment|tgl|{{messageLink|1222184541.4445.400.camel@ebony.2ndQuadrant|patch v7}} here}}&lt;br /&gt;
{{comment|tgl|it&#039;s still got {{messageLink|28973.1222381719@sss.pgh.pa.us|issues}}}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1222815151.4445.1397.camel@ebony.2ndQuadrant|patch v8}} here}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1223472898.4747.310.camel@ebony.2ndQuadrant|patch v9}} here, in response to {{messageLink|48EC9CC5.6060803@enterprisedb.com|Heikki&#039;s review}}}}&lt;br /&gt;
{{comment|sriggs|some issues overlooked, fixed as part of Hot Standby patch only at present}}&lt;br /&gt;
{{comment|sriggs|do we want this split out again as a separate patch for easier review?}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1225557138.3971.673.camel@ebony.2ndQuadrant|Hot Standby - queries during archive recovery|status=Pending Review|Simon Riggs}}&lt;br /&gt;
{{comment|sriggs| v5d now available, fixing all Mark&#039;s reported issues. Main parts are fully reviewable}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1223472186.4747.301.camel@ebony.2ndQuadrant|pg_stop_backup wait bug fix|Simon Riggs}}&lt;br /&gt;
{{comment|Robert Haas|sriggs extracted this from recovery infrastructure patch per {{messageLink|48EC9CC5.6060803@enterprisedb.com|Heikki&#039;s suggestion}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch||pg_start_backup checkpoint issue|Simon Riggs}}&lt;br /&gt;
{{comment|sriggs|separated out from Infrastructure changes patch per {{messageLink|48EC9CC5.6060803@enterprisedb.com|Heikki&#039;s suggestion}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1220174867.4371.107.camel@ebony.2ndQuadrant|rmgr hooks and contrib/rmgr_hook|status=Waiting on dependencies|Simon Riggs}} &lt;br /&gt;
{{comment|sriggs| deferrable, if required}}&lt;br /&gt;
{{comment|tgl|I think the plan is for this to wait till &amp;quot;infrastructure&amp;quot; patch goes in}}&lt;br /&gt;
&lt;br /&gt;
{{patch|3f0b79eb0810310436w360f0afdy76ff1499b177ce0d@mail.gmail.com|Synchronous log-shipping replication|Masao Fujii|reviewers=Heikki Linnakangas, Simon Riggs}}&lt;br /&gt;
{{comment|fujii|{{messageLink|3f0b79eb0811040404r799d3170v5bb9f201000f1771@mail.gmail.com|signal handling patch v2}} here}}&lt;br /&gt;
{{comment|fujii|{{messageLink|3f0b79eb0811050617o3237130awb4aec1d3a2daacab@mail.gmail.com|walsender process patch v1}} here}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Upgrade-in-place and related issues === &lt;br /&gt;
&lt;br /&gt;
{{patch|490B7C1B.8050408@sun.com|In-place online upgrade|status=Waiting for new version|Zdenek Kotala|reviewers=Robert Haas}}&lt;br /&gt;
{{comment|Zdenek Kotala|This patch requires &amp;quot;htup and bufpage API clean up&amp;quot; and &amp;quot;HeapTuple version extension&amp;quot; patches. Git repository is [http://git.postgresql.org here] }}&lt;br /&gt;
{{review|603c8f070811022022x582a9cbdp60798a6b87910edf@mail.gmail.com|Robert Haas|preliminary comments, still need a clean diff}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48F1FC7E.1060406@sun.com|Extending pg_class info + more flexible TOAST chunk size|Zdenek Kotala|reviewers=Robert Haas|status=Waiting for new version}}&lt;br /&gt;
{{comment|tgl|seems it&#039;d be better to make TOAST chunks work like {{messageLink|490AB654.6040409@enterprisedb.com|this}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4909DFCE.1000702@sun.com|HeapTuple version extension + code cleanup|Zdenek Kotala|reviewers=Robert Haas|status=Waiting for new version}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== SQL language features ===&lt;br /&gt;
&lt;br /&gt;
{{patch|e08cc0400810270912u49a6ec83vc23984c01f368f76@mail.gmail.com|Window Functions|Hitoshi Harada|reviewers=Heikki Linnakangas, David Rowley}}&lt;br /&gt;
{{comment|Harada|updated patch is {{messageLink|e08cc0400810310721l22a6bb7kb6a300ce66443806@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Harada|the latest patch is {{messageLink|e08cc0400811070746p43553f10s6bb09e98b7eafc3b@mail.gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|162867790810170316l4eeecb0bq321dd771f8f4e661@mail.gmail.com|grouping sets|status=WIP|Pavel Stehule|reviewers=Ibrar Ahmed}}&lt;br /&gt;
{{comment|Pavel Stehule| doc and notes [[Grouping Sets]]}}&lt;br /&gt;
&lt;br /&gt;
{{patch|162867790810260428p56d16352qa1ec5c4c5330f25c@mail.gmail.com|default values for function&#039;s parameters|Pavel Stehule|reviewers=Peter Eisentraut}}&lt;br /&gt;
{{comment|Pavel Stehule| fix known bugs, currently only doc should be finished}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070808070503jd7be083kcce3e16345affb08@mail.gmail.com|add columns via CREATE OR REPLACE VIEW|Robert Haas|reviewers=Bernd Helmle}}&lt;br /&gt;
{{comment|Robert Haas|some further justification of the proposed design {{messageLink|603c8f070808070956t1ab98dcdr933575eb096e4c28@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Robert Haas|questions about how to move forward {{messageLink|603c8f070810031839y7ce9a852o86effbab9fd6dd9b@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Robert Haas|a {{messageLink|482096EC.3000805@dunslane.net|similar feature request}} from Andrew Dunstan}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490394B7.6090503@lelarge.info|ALTER DATABASE WITH TABLESPACE Statement|Guillaume Lelarge|reviewers=Bernd Helmle}}&lt;br /&gt;
{{comment|Bernd Helmle|Syntax discussion and updated version {{messageLink|C0F6602797884925406AB88F@imhotep.credativ.de|here}}}}&lt;br /&gt;
{{comment|Guillaume Lelarge|Updated version with SET syntax {{messageLink|4910E46E.4010000@lelarge.info|here}}}}&lt;br /&gt;
{{comment|Bernd Helmle|Updated version from Guillaume {{messageLink|4912C88A.2070808@lelarge.info|here}}}}&lt;br /&gt;
{{comment|Guillaume Lelarge|Updated version {{messageLink|49140181.3000903@lelarge.info|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48EFA13C.2060407@frogthinker.org|Prepared transactions and temp tables|Emmanuel Cecchet|reviewers=Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4909726F.8000800@gmx.net|TABLE command|Peter Eisentraut|status=Ready for Code Review|reviewers=Unicron}}&lt;br /&gt;
{{comment|Unicron|Patch {{messageLink|850603.14426.qm@web62408.mail.re1.yahoo.com|works per specification}} }}&lt;br /&gt;
&lt;br /&gt;
{{patch|490AFC08.8040500@Sun.COM|Distinct types|Peter Eisentraut|status=Waiting for Author}}&lt;br /&gt;
{{comment|Bernd Helmle|Patch needs further work regarding {{messageLink|17750.1225571886@sss.pgh.pa.us|indexing}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|2849137C693B65CC8E86411C@imhotep.credativ.de|Automatic view update rules|status=WIP|Bernd Helmle|reviewers=Unicron}}&lt;br /&gt;
{{comment|Bernd Helmle|New version with RETURNING support {{messageLink|94CF655A8D0DC7D5B4B81D8B@imhotep.credativ.de|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1225543926.8122.14.camel@huvostro|Enable pl/python to return records based on multiple OUT params|status=Waiting on author|Hannu Krosing}}&lt;br /&gt;
{{comment|Robert Haas|Hannu is {{messageLink|1225781532.7597.19.camel@huvostro|working on a new version}}}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Datatypes ===&lt;br /&gt;
&lt;br /&gt;
{{patch|48D15471.6080305@cheapcomplexdevices.com|SQL Standard Interval output and IntervalStyle GUC|Ron Mayer|status=Ready for committer|reviewers=Brendan Jurd}}&lt;br /&gt;
{{comment|Ron Mayer|An update {{messageLink|48D52E48.406@cheapcomplexdevices.com|here}} fixed some bugs in GUC setting.}}&lt;br /&gt;
{{comment|Ron Mayer|Another update {{messageLink|48E49BDC.4090402@cheapcomplexdevices.com|here}}, brought up-to-date with HEAD}}&lt;br /&gt;
{{comment|Ron Mayer|Brought up-to-date with head [http://0ape.com/postgres_interval_patches/ here]. Now allows setting IntervalStyle through an environment variable because pg_regress had set interval styles (as a side-effect of setting DateStyles) through the environment, some minor cleanup.}}&lt;br /&gt;
{{review|37ed240d0811032122u56db1959h91f53bbb9733c90d@mail.gmail.com|BJ|Bug in output, stylistic suggestions}}&lt;br /&gt;
{{comment|the mailing list|Feedback from {{messageLink|19477.1225814409@sss.pgh.pa.us|Tom L}} and {{messageLink|49101C94.EE98.0025.0@wicourts.gov|Kevin G}} about mixed-sign intervals}}&lt;br /&gt;
{{comment|Ron Mayer|Updated patch {{messageLink|4910B1DB.4000000.cheapcomplexdevices@com|here}} to fixe bug and style suggestions from the review and to attempt to address feedback about mixed-sign intervals with doc updates.}}&lt;br /&gt;
{{review|37ed240d0811042102q78df5b86t2ff2092a75d371d7@mail.gmail.com|BJ|One last typo in docs but otherwise all good; review complete}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48E4A30C.3000503@cheapcomplexdevices.com|ISO 8601 interval literal input and output|Ron Mayer|reviewers=Brendan Jurd|status=Waiting for response}}&lt;br /&gt;
{{comment|Ron Mayer|Note that this patch doesn&#039;t apply directly to HEAD, but depends on the IntervalStyle GUC patch to be applied first.}}&lt;br /&gt;
{{comment|Ron Mayer|The initial (2003) version of this patch along with a thread which explains the feature a bit more can be found [http://archives.postgresql.org/pgsql-patches/2003-09/msg00103.php here].}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|490BA342.7010300@cheapcomplexdevices.com|latest version}}}}&lt;br /&gt;
{{comment|Ron Mayer|Latest version [http://0ape.com/postgres_interval_patches/ here] that matches the latest version of the IntervalStyle patch that can be found elsewhere on this page.}}&lt;br /&gt;
{{review|37ed240d0811050750v11726fd1of441646f87b583da@mail.gmail.com|BJ|Code style and documentation suggestions}}&lt;br /&gt;
{{comment|Ron Mayer|Update here [http://0ape.com/postgres_interval_patches/ here] that fixes style &amp;amp; docs; as well as a bug where the ISO8601 spec wasn&#039;t quite followed (an optional field was treated as required by previous patches).}}&lt;br /&gt;
{{review|37ed240d0811062058n752c3880kb04feb85e355b524@mail.gmail.com|BJ|Query behaviour of &#039;P0001&#039;, final doc cleanup suggestions}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48CEDE68.7090501@cheapcomplexdevices.com|Interval rounding consistency|Ron Mayer|reviewers=Brendan Jurd}}&lt;br /&gt;
{{comment|Ron Mayer|Patch 3 [http://0ape.com/postgres_interval_patches/ here] refactors the interval code to remove much of the copy&amp;amp;paste in DecodeInterval and EncodeInterval with the side effect of making interval rounding more consistent between styles.  This patch applies on top of the IntervalStyle patch and the ISO 8601 Interval patch.}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20952F54-6730-49D8-99A3-1834697790B5@decibel.org|array_length|Jim C. Nasby|reviewers=Peter Eisentraut}}&lt;br /&gt;
{{comment|Robert Haas|I have {{messageLink|603c8f070811062006q4f20b2bq179d4d2ffec65690@mail.gmail.com|reimplemented this in C}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810151933p445978b3td481a5422a2aebf4@mail.gmail.com|array_agg/array_accum|Robert Haas|reviewers=Peter Eisentraut}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1225045937.4434.21.camel@localhost.localdomain|another version}} and {{messageLink|1225682527.1375.150.camel@jdavis|another one}} from Jeff Davis}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Indexes ===&lt;br /&gt;
&lt;br /&gt;
{{patch|490B07BA.6030109@sigaev.ru|GIN fast insert|Teodor Sigaev, Oleg Bartunov}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490B3752.3010800@sigaev.ru|B-Tree emulation for GIN|status=WIP|Teodor Sigaev, Oleg Bartunov}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081101000154.GO27872@fune|On-disk bitmap indexes|status=WIP|Gabriele Bartolini, Gianni Ciolli|reviewers=Greg Stark (more welcome!)}}&lt;br /&gt;
{{review|49130E72.1000803@sigaev.ru|Teodor Sigaev|several bugs}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Performance ===&lt;br /&gt;
&lt;br /&gt;
{{patch|6EEA43D22289484890D119821101B1DF2C1683@exchange20.mercury.ad.ubc.ca|Improve Performance of Multi-Batch Hash Join for Skewed Data Sets|Ramon Lawrence/Bryce Cutt|reviewers=Joshua Tolley}}&lt;br /&gt;
{{comment|Joshua Tolley|[http://archives.postgresql.org/pgsql-hackers/2008-11/msg00286.php] reports backend crash}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4909B326.507@enterprisedb.com|Optimizing COPY with memchr()|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|87ljw5c0lx.fsf@oxford.xeocode.com|posix_fadvise|Gregory Stark}}&lt;br /&gt;
&lt;br /&gt;
{{patch|a778a7260810280033n43f70d36x8c437eacf9a5461e@mail.gmail.com|Proposal of PITR performance improvement|Koichi Suzuki|reviewers=Simon Riggs}}&lt;br /&gt;
&lt;br /&gt;
{{patch|36e682920811021349h7202bdecpd7a45c8a8038465e@mail.gmail.com|Hash Join-Filter Pruning using Bloom Filters|status=WIP|Jonah Harris}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Improving admin experience ===&lt;br /&gt;
&lt;br /&gt;
{{patch|4905AE17.7090305@enterprisedb.com|Visibility map, partial vacuums|status=WIP|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081029183248.GE4331@alvh.no-ip.org|Block-level CRC checks|Alvaro Herrera|status=WIP}}&lt;br /&gt;
&lt;br /&gt;
{{patch|c2ee6dbd0810100553gd328275ue2eb6e14bee70a8@mail.gmail.com|adding VERBOSE option to CLUSTER|Jim Cox|reviewers=Peter Eisentraut}}&lt;br /&gt;
&lt;br /&gt;
{{patch|a301bfd90810310750pf108c69x36499546f406650f@mail.gmail.com|Auto Partitioning Patch|Nikhil Sontakke|reviewers=Jaime Casanova}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1223379173.4747.145.camel@ebony.2ndQuadrant|Reducing some DDL Locks to ShareLock|status=Pending Review|Simon Riggs}} &lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1722552592.7.1224882093461.JavaMail.root@spotone|ddl_lock_reduce.v4.patch}}}}&lt;br /&gt;
{{comment|sriggs|agreed rework to implement pg_domain constraint, but the main patch still needs review}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
=== Connection management ===&lt;br /&gt;
&lt;br /&gt;
{{patch|48FC7E84.3080702@hagander.net|SSL cleanups/hostname verification|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49009D67.4040202@hagander.net|clientcert option for pg_hba|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49076F39.1080502@hagander.net|regexp support in usermaps|Magnus Hagander|reviewers=Gianni Colli}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Contrib modules ===&lt;br /&gt;
&lt;br /&gt;
{{patch|0BD2E4E9-AF5A-4B4F-B546-027424EE8FAD@kineticode.com|Tests citext casts|David Wheeler|reviewers=&lt;br /&gt;
Kenneth Marshall}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081106171139.8D21.52131E4D@oss.ntt.co.jp|contrib infrastructures|Martin Pihlak, Takahiro Itagaki|reviewers=Jeff Davis, Matthew Wetmore}}&lt;br /&gt;
{{comment|Itagaki|contains {{messageLink|490A00A8.7050708@gmail.com|QueryDesc}}, {{messageLink|20081009165157.9BE4.52131E4D@oss.ntt.co.jp|explain}} and {{messageLink|20081027171917.ADD6.52131E4D@oss.ntt.co.jp|hooks}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081009165157.9BE4.52131E4D@oss.ntt.co.jp|contrib/auto_explain|Takahiro Itagaki|reviewers=Jeff Davis}}&lt;br /&gt;
{{comment|Itagaki|nested statements handling is {{messageLink|48FCA095.8020709@gmail.com|requested}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081011172450.3402.52131E4D@oss.ntt.co.jp|contrib/pg_stat_statements|Takahiro Itagaki|reviewers=Matthew Wetmore}}&lt;br /&gt;
{{comment|Itagaki|{{messageLink|20081027171917.ADD6.52131E4D@oss.ntt.co.jp|latest patch versions}}}}&lt;br /&gt;
{{comment|Itagaki|{{messageLink|1d709ecc0811011343lf65f58fjb2e96194f4c2ecc5@mail.gmail.com|comments}} from Vladimir}}&lt;br /&gt;
&lt;br /&gt;
{{patch|e4ccc24e0810222010p12bae2f4xa3a11cb2bc51bd89@mail.gmail.com|pg_standby support for compressed segments|Charles Duffy|reviewers=Simon Riggs}}&lt;br /&gt;
{{comment|Simon Riggs|Deferring review for a few weeks until we get a better picture of streaming replication requirements for 8.4}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.GSO.4.64.0811012101220.17619@westnet.com|Simple postgresql.conf wizard|Greg Smith|reviewers=Josh Berkus}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
=== Clients ===&lt;br /&gt;
&lt;br /&gt;
{{patch|200810271936.m9RJaGW09544@momjian.us|libpq callback unregistration|Bruce Momjian|reviewers=Magnus Hagander}}&lt;br /&gt;
{{comment|Magnus|Needs more work, comments {{messageLink|490EEF2D.2050703@hagander.net|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48F04B7C.3080303@benedekl.tvnetwork.hu|pg_dump roles support|Benedek Laszlo|reviewers=Ibrar Ahmed|Status=Waiting for Author}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490878AC.1@dunslane.net|parallel restore|status=WIP|Andrew Dunstan}}&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| colspan=&amp;quot;4&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
&lt;br /&gt;
{{patch|03c301c91737$be5a2a30$0e01a8c0@IBMC9A0F63B40D|Solve a problem of LC_TIME of windows|Hiroshi Saito}}&lt;br /&gt;
{{comment|tgl|updated version {{messageLink|2C940A1672E743439355545C5DB15786@HIRO57887DE653|here}}}}&lt;br /&gt;
{{comment|itagaki|comments and updated version {{messageLink|20081104094301.7EE8.52131E4D@oss.ntt.co.jp|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|BLU110-W38CE0A22D467A8C3D9736CFF540@phx.gbl|Support PLUGINS lines in Makefiles, similar to MODULES|Asif Naeem}}&lt;br /&gt;
{{comment|Dave Page|This doesn&#039;t work with the edb-debugger plugin, which is the only such plugin around AFAIK. It needs to ignore comments on the PLUGINS line, and handle multiple targets (plugin_debugger, pldbgapi, targetinfo etc). Not sure if we want that complexity though.}}&lt;br /&gt;
{{comment|Heikki|Unix-makefile version: {{messageLink|BLU110-W57823CEB7DC113354471EFF3B0@phx.gbl|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48F53EC0.3020004@timbira.com|autovacuum and reloption|status=WIP|Euler Taveira de Oliveira|reviewers=Alvaro Herrera}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49097338.2070700@gmail.com|SQL/MED compatible connection manager|Martin Pihlak|status=WIP}}&lt;br /&gt;
{{comment|Martin Pihlak|Updated patch {{messageLink|490B28FA.4080101@gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081029164000.GL27466@fetter.org|pre-MED|David Fetter|reviewers=Alex Hunsaker|status=Waiting on author}}&lt;br /&gt;
{{comment|David Fetter|Updated patch {{messageLink|20081031144852.GF15545@fetter.org|here}}}}&lt;br /&gt;
{{review|34d269d40811031902p1d73d177w9f2e721ae169e8be@mail.gmail.com|alexhun|few questions and tgl had some constructive {{messageLink|24867.1225819435@sss.pgh.pa.us|comments}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|f205bb120810280833x340324d3m19a4f8aa65d822b@mail.gmail.com|FAQ_Solaris 1.28 to spanish|Emanuel CALVO FRANCO|reviewers=Peter Eisentraut}}&lt;br /&gt;
&lt;br /&gt;
{{CommitFestEndSection}}&lt;br /&gt;
&lt;br /&gt;
== Committed patches ==&lt;br /&gt;
{{CommitFestSectionNew}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20080803.114711.73374027.t-ishii@sraoss.co.jp|Common Table Expressions|Yoshiyuki Asaba|status=Committed 2008-10-04|reviewers=Jeff Davis}}&lt;br /&gt;
{{comment|David Fetter|README is {{messageLink|20080818.163852.105172778.t-ishii@sraoss.co.jp|here.}}}}&lt;br /&gt;
{{comment|David Fetter|Git repository is [http://git.postgresql.org/git/~davidfetter/cte/.git here.]}}&lt;br /&gt;
{{comment|David Fetter|[[CTEReadme]]}}&lt;br /&gt;
{{comment|David Fetter|[[CTESQLStandard| Fair Use from the draft SQL:2008 standard (WIP)]]}}&lt;br /&gt;
{{review|13449.1221589943@sss.pgh.pa.us|tgl|needs a good bit of work yet}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.GSO.4.64.0809152349440.19910@westnet.com|Add default_val to pg_settings|status=Committed 2008-10-06|Greg Smith|reviewers=Simon Riggs,Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081016102603.897D.52131E4D@oss.ntt.co.jp|Noisy _dosmaperror|status=Committed 2008-10-16|Takahiro Itagaki|reviewers=Tom Lane}}&lt;br /&gt;
&lt;br /&gt;
{{patch|b4e5ce320810151918g2acf69ebh9f80f4f2e1c203a0@mail.gmail.com|Memory leak on hashed agg rescan|status=Committed 2008-10-16|Neil Conway|reviewers=Tom Lane}}&lt;br /&gt;
{{review|10455.1224160007@sss.pgh.pa.us|Tom Lane|move some logic to separate function}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1223383838.4747.154.camel@ebony.2ndQuadrant|Atomic subtransaction commit|status=Committed 2008-10-20|Simon Riggs|reviewers=Alvaro Herrera}} &lt;br /&gt;
&lt;br /&gt;
{{patch|3327.1224535092@sss.pgh.pa.us|add placeholder variables to planner|status=Committed 2008-10-22|Tom Lane}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48E271C5.7010907@hagander.net|pg_hba options parsing|status=Committed 2008-10-23|Magnus Hagander|reviewers=Bruce Momjian}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|48F0DE8B.8030004@hagander.net|updated patch}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48FC3994.8040809@hagander.net|libpq ssl -&amp;gt; clear fallback looses error messages|status=Committed 2008-10-27|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905D22D.9040001@hagander.net|better hba parsing error messages|status=Committed 2008-10-27|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905A1DE.5030102@hagander.net|remove crypt authentication|status=Committed 2008-10-28|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905F515.3020208@gmx.net|Unicode escapes in literals|status=Committed 2008-10-29|Peter Eisentraut}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490A138E.80100@enterprisedb.com|User defined I/O conversion casts|status=Committed 2008-10-31|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49085327.5010608@enterprisedb.com|Updating FSM on recovery|status=Committed 2008-10-31|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.BSO.4.64.0810271955030.28764@leary.csoft.net|use new heap_(form/deform/modify)_tuple API|Kris Jurka|reviewers=Zdenek Kotala|status=Committed 2008-11-01}}&lt;br /&gt;
{{comment|Zdenek Kotala| It seems OK. Needs apply also {{messageLink|Pine.BSO.4.64.0810281721500.6833@leary.csoft.net|pfree patch.}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.BSO.4.64.0810281622240.9851@leary.csoft.net|don&#039;t use MAKE_PTR/OFFSET for shmem pointers|Kris Jurka|reviewers=Tom Lane|status=Committed 2008-11-02}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48C181D4.8030807@gmail.com|reducing statistics write overhead|Martin Pihlak|reviewers=Tom Lane|status=Committed 2008-11-02}}&lt;br /&gt;
{{comment|Martin Pihlak|Latest patch {{messageLink|48C594D8.6050504@gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|37ed240d0809030015u73b65b66v70fd76741317c6f5@mail.gmail.com|pg_typeof()|Brendan Jurd|reviewers=Kurt Harriman|status=Committed 2008-11-03}}&lt;br /&gt;
{{comment|Kurt Harriman|{{messageLink|http://archives.postgresql.org/pgsql-hackers/2008-11/msg00080.php|Updated patch}} is ready to commit if there is no objection}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.BSO.4.64.0810081931240.11647@leary.csoft.net|Fixes for psql describeOneTableDetails|Kris Jurka|reviewers=Tom Lane|status=Committed 2008-11-03}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48E22CF5.4050503@sun.com|PageGetTempPage cleanup |Zdenek Kotala|reviewers=Tom Lane|status=Committed 2008-11-03}}&lt;br /&gt;
{{comment|Zdenek Kotala|Original discussion {{messageLink|4938.1217862947@sss.pgh.pa.us|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810092009s1312d30bxc854cdfb5d9fed7e@mail.gmail.com|Allow the UUID type to accept non-standard formats|Robert Haas|reviewers=Peter Eisentraut|status=Committed 2008-11-03}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810101937n776c1e7cvd6a12345b0bbda28@mail.gmail.com|array_ndims|Robert Haas|reviewers=Peter Eisentraut|status=Committed 2008-11-04}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810282045g7fa6bdf9p53f03114d49643d7@mail.gmail.com|bulk inserts - keep most recent page pinned|Robert Haas|reviewers=Tom Lane|status=Committed 2008-11-06}}&lt;br /&gt;
{{comment|Robert Haas|based on work by Simon Riggs: [http://archives.postgresql.org/pgsql-hackers/2008-02/msg01080.php original idea],[http://archives.postgresql.org/pgsql-patches/2008-02/msg00140.php original patch], [http://archives.postgresql.org/pgsql-patches/2008-02/msg00154.php Tom Lane&#039;s comments]}}&lt;br /&gt;
{{comment|Robert Haas|Tom&#039;s comments on my [http://archives.postgresql.org/pgsql-hackers/2008-10/msg01276.php design proposal] are {{messageLink|17996.1225049097@sss.pgh.pa.us|here}}}}&lt;br /&gt;
{{comment|Robert Haas|patch {{messageLink|603c8f070811011023n202aea33w4da13b7d14f74134@mail.gmail.com|v2}}, adjusting for Heikki&#039;s changes to the ReadBuffer interface}}&lt;br /&gt;
&lt;br /&gt;
{{CommitFestEndSection}}&lt;br /&gt;
&lt;br /&gt;
== Returned with Feedback ==&lt;br /&gt;
{{CommitFestSectionNew}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1225010283.21241.33.camel@localhost.localdomain|new correlation metric|Jeff Davis|reviewers=Brendan Jurd|status=Pending rework}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49086E4C.9030602@sun.com|htup and bufpage API clean up|Zdenek Kotala|reviewers=Robert Haas|status=Needs different approach}}&lt;br /&gt;
{{comment|Zdenek Kotala|New version is {{messageLink|490875FA.4020709@sun.com|here}}}}&lt;br /&gt;
{{review|603c8f070811031822q7d3b33f7x8576b7028f498cc4@mail.gmail.com|Robert Haas|proposed API seems too costly and fragile}}&lt;br /&gt;
&lt;br /&gt;
{{CommitFestEndSection}}&lt;br /&gt;
&lt;br /&gt;
== Round Robin Reviewers ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;1&amp;quot; cellspacing=&amp;quot;0&amp;quot; style=&amp;quot;width: 60%; border-collapse: collapse; border: 1px solid #ccc; font-size: 90%;&amp;quot;&lt;br /&gt;
|- style=&amp;quot;background: #eee;&amp;quot;&lt;br /&gt;
! width=&amp;quot;30%&amp;quot; | Name&lt;br /&gt;
!Status&lt;br /&gt;
!Reviewing&lt;br /&gt;
!Completed&lt;br /&gt;
|-&lt;br /&gt;
|Brendan Jurd || Available || 2 || 2&lt;br /&gt;
|-&lt;br /&gt;
|Jaime Casanova || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Stephen Frost || Available 11/15 || 0 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Jeff Davis || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Greg Stark || Unknown || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Abhijit Menon-Sen || Unknown || 0 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Alex Hunsaker || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Markus Wanner || Cherry-picking || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Ibrar Ahmed || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|D&#039;Arcy Cain || Unknown || 0 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Kenneth Marshall || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Robert Haas || Available || 0 || 3&lt;br /&gt;
|-&lt;br /&gt;
|Matthew Wetmore || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|Gianni Colli || Available || 1 || 0&lt;br /&gt;
|-&lt;br /&gt;
|&amp;quot;Unicron&amp;quot; || Available || 1 || 0&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
	<entry>
		<id>https://wiki.postgresql.org/index.php?title=CommitFest_2008-11&amp;diff=3158</id>
		<title>CommitFest 2008-11</title>
		<link rel="alternate" type="text/html" href="https://wiki.postgresql.org/index.php?title=CommitFest_2008-11&amp;diff=3158"/>
		<updated>2008-10-31T14:41:38Z</updated>

		<summary type="html">&lt;p&gt;Umitanuki: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__TOC__&lt;br /&gt;
&lt;br /&gt;
This is the page for the CommitFest starting &#039;&#039;&#039;2008 November&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
{{CommitFestOpen}}&lt;br /&gt;
&lt;br /&gt;
== Pending patches ==&lt;br /&gt;
{{CommitFestSectionNew}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4863B3DA.8030209@kaigai.gr.jp|SE-PostgreSQL patches|Kaigai Kohei|reviewers=Peter Eisentraut, Abhijit Menon-Sen}}&lt;br /&gt;
{{comment|Peter|checking with Solaris engineers about compatibility with Solaris TX; will continue review throughout August}}&lt;br /&gt;
{{comment|KaiGai|{{messageLink|488F0C02.4020708@ak.jp.nec.com|latest patch versions}}}}&lt;br /&gt;
{{comment|KaiGai|{{messageLink|48BA12F4.1090201@kaigai.gr.jp|latest patch versions}}}}&lt;br /&gt;
{{comment|Robert Haas|KaiGai&#039;s latest version is {{messageLink|48F46606.4080207@ak.jp.nec.com|r1120}}}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|48F71E36.9010203@ak.jp.nec.com|latest version}}, now with 6 patches}}&lt;br /&gt;
{{comment|KaiGai|[[SEPostgreSQL]] can be a comprehensive documentation (now in progress)}}&lt;br /&gt;
{{comment|KaiGai|{{messageLink|490AD10A.6020902@ak.jp.nec.com|latest patches (r1168)}}}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{patch|1220213074.4371.173.camel@ebony.2ndQuadrant|Infrastructure changes for recovery|status=Pending Review|Simon Riggs|reviewers=Tom Lane, Heikki Linnakangas}} &lt;br /&gt;
{{comment|sriggs| important patch for other work}}&lt;br /&gt;
{{comment|tgl|some comments {{messageLink|1905.1220895241@sss.pgh.pa.us|here}}}}&lt;br /&gt;
{{comment|tgl|updated patch {{messageLink|1221080797.3913.768.camel@ebony.2ndQuadrant|here}}, still being tested}}&lt;br /&gt;
{{comment|tgl|Simon found {{messageLink|1221725145.3913.2315.camel@ebony.2ndQuadrant|some issues}}}}&lt;br /&gt;
{{comment|tgl|{{messageLink|1222184541.4445.400.camel@ebony.2ndQuadrant|patch v7}} here}}&lt;br /&gt;
{{comment|tgl|it&#039;s still got {{messageLink|28973.1222381719@sss.pgh.pa.us|issues}}}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1222815151.4445.1397.camel@ebony.2ndQuadrant|patch v8}} here}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1223472898.4747.310.camel@ebony.2ndQuadrant|patch v9}} here, in response to {{messageLink|48EC9CC5.6060803@enterprisedb.com|Heikki&#039;s review}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1220174867.4371.107.camel@ebony.2ndQuadrant|rmgr hooks and contrib/rmgr_hook|status=Waiting on author|Simon Riggs}} &lt;br /&gt;
{{comment|sriggs| deferrable, if required}}&lt;br /&gt;
{{comment|tgl|I think the plan is for this to wait till &amp;quot;infrastructure&amp;quot; patch goes in}}&lt;br /&gt;
&lt;br /&gt;
{{patch|37ed240d0809030015u73b65b66v70fd76741317c6f5@mail.gmail.com|pg_typeof()|Brendan Jurd}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48C181D4.8030807@gmail.com|reducing statistics write overhead|Martin Pihlak}}&lt;br /&gt;
{{comment|Martin Pihlak|Latest patch {{messageLink|48C594D8.6050504@gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|BLU110-W38CE0A22D467A8C3D9736CFF540@phx.gbl|Support PLUGINS lines in Makefiles, similar to MODULES|Asif Naeem}}&lt;br /&gt;
{{comment|Dave Page|This doesn&#039;t work with the edb-debugger plugin, which is the only such plugin around AFAIK. It needs to ignore comments on the PLUGINS line, and handle multiple targets (plugin_debugger, pldbgapi, targetinfo etc). Not sure if we want that complexity though.}}&lt;br /&gt;
{{comment|Heikki|Unix-makefile version: {{messageLink|BLU110-W57823CEB7DC113354471EFF3B0@phx.gbl|here}}}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{patch|48D15471.6080305@cheapcomplexdevices.com|SQL Standard Interval output and IntervalStyle GUC|Ron Mayer}}&lt;br /&gt;
{{comment|Ron Mayer|&lt;br /&gt;
  An update {{messageLink|48D52E48.406@cheapcomplexdevices.com|here}} fixed &lt;br /&gt;
  some bugs in GUC setting. &lt;br /&gt;
  Another update {{messageLink|48E49BDC.4090402@cheapcomplexdevices.com|here}}, &lt;br /&gt;
  brought up-to-date with HEAD}}&lt;br /&gt;
{{comment|Ron Mayer|Brought up-to-date with head [http://0ape.com/postgres_interval_patches/ here]. Now allows setting IntervalStyle through an environment variable because pg_regress had set interval styles (as a side-effect of setting DateStyles) through the environment, some minor cleanup.}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48E4A30C.3000503@cheapcomplexdevices.com|ISO 8601 interval literal input and output|Ron Mayer}}&lt;br /&gt;
{{comment|Ron Mayer|Note that this patch doesn&#039;t apply directly to HEAD, but depends on the {{messageLink|48E49BDC.4090402@cheapcomplexdevices.com|IntervalStyle GUC patch}} to be applied first.}}&lt;br /&gt;
{{comment|Ron Mayer|The initial (2003) version of this patch along with a thread which explains the feature a bit more can be found [http://archives.postgresql.org/pgsql-patches/2003-09/msg00103.php here].}}&lt;br /&gt;
{{comment|Ron Mayer|An update [http://0ape.com/postgres_interval_patches/ here].  Cleaned up code and added regression tests.}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48CEDE68.7090501@cheapcomplexdevices.com|Interval rounding consistency|Ron Mayer}}&lt;br /&gt;
{{comment|Ron Mayer|Patch 3 [http://0ape.com/postgres_interval_patches/ here] refactors the interval code to remove much of the copy&amp;amp;paste in DecodeInterval and EncodeInterval with the side effect of making interval rounding more consistent between styles.  This patch applies on top of the IntervalStyle patch and the ISO 8601 Interval patch.}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{patch|03c301c91737$be5a2a30$0e01a8c0@IBMC9A0F63B40D|Solve a problem of LC_TIME of windows|Hiroshi Saito}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20080901063855.GJ16005@tamriel.snowman.net|Column-level Permissions|Stephen Frost|status=WIP|reviewers=Markus Wanner}}&lt;br /&gt;
{{comment|Stephen Frost|Updated patch {{messageLink|20080902221823.GL16005@tamriel.snowman.net|here}}}}&lt;br /&gt;
{{review|48DB48AC.5010400@bluegap.ch|Markus Wanner|Awaiting updated patch.}}&lt;br /&gt;
&lt;br /&gt;
{{patch|0BD2E4E9-AF5A-4B4F-B546-027424EE8FAD@kineticode.com|Tests citext casts|David Wheeler}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48E22CF5.4050503@sun.com|PageGetTempPage cleanup |Zdenek Kotala}}&lt;br /&gt;
{{comment|Zdenek Kotala|Original discussion {{messageLink|4938.1217862947@sss.pgh.pa.us|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070808070503jd7be083kcce3e16345affb08@mail.gmail.com|add columns via CREATE OR REPLACE VIEW|Robert Haas}}&lt;br /&gt;
{{comment|Robert Haas|some further justification of the proposed design {{messageLink|603c8f070808070956t1ab98dcdr933575eb096e4c28@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Robert Haas|questions about how to move forward {{messageLink|603c8f070810031839y7ce9a852o86effbab9fd6dd9b@mail.gmail.com|here}}}}&lt;br /&gt;
{{comment|Robert Haas|a {{messageLink|482096EC.3000805@dunslane.net|similar feature request}} from Andrew Dunstan}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1223379173.4747.145.camel@ebony.2ndQuadrant|Reducing some DDL Locks to ShareLock|status=Pending Review|Simon Riggs}} &lt;br /&gt;
{{comment|Robert Haas|{{messageLink|1722552592.7.1224882093461.JavaMail.root@spotone|ddl_lock_reduce.v4.patch}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.BSO.4.64.0810081931240.11647@leary.csoft.net|Fixes for psql describeOneTableDetails|Kris Jurka}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1223472186.4747.301.camel@ebony.2ndQuadrant|pg_stop_backup wait bug fix|Simon Riggs}}&lt;br /&gt;
{{comment|Robert Haas|sriggs extracted this from recovery infrastructure patch per {{messageLink|48EC9CC5.6060803@enterprisedb.com|Heikki&#039;s suggestion}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081009165157.9BE4.52131E4D@oss.ntt.co.jp|contrib/auto_explain|Takahiro Itagaki|}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810092009s1312d30bxc854cdfb5d9fed7e@mail.gmail.com|Allow the UUID type to accept non-standard formats|Robert Haas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810101937n776c1e7cvd6a12345b0bbda28@mail.gmail.com|array_ndims|Robert Haas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48F04B7C.3080303@benedekl.tvnetwork.hu|pg_dump roles support|Benedek Laszlo}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081011172450.3402.52131E4D@oss.ntt.co.jp|contrib/pg_stat_statements|Takahiro Itagaki}}&lt;br /&gt;
{{comment|Itagaki|{{messageLink|20081027171917.ADD6.52131E4D@oss.ntt.co.jp|latest patch versions}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49078031.9030002@gmail.com|contrib/pg_stat_staments querydesc|Martin Pihlak}}&lt;br /&gt;
{{comment|Martin Pihlak|Updated patch {{messageLink|490A00A8.7050708@gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{patch|c2ee6dbd0810100553gd328275ue2eb6e14bee70a8@mail.gmail.com|adding VERBOSE option to CLUSTER|Jim Cox}}&lt;br /&gt;
&lt;br /&gt;
{{patch|e08cc0400810270912u49a6ec83vc23984c01f368f76@mail.gmail.com|Window Functions|Hitoshi Harada|reviewers=Heikki Linnakangas}}&lt;br /&gt;
{{comment|Harada|updated patch is {{messageLink|e08cc0400810310721l22a6bb7kb6a300ce66443806@mail.gmail.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48F1FC7E.1060406@sun.com|Extending pg_class info + more flexible TOAST chunk size|Zdenek Kotala}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48EFA13C.2060407@frogthinker.org|Transactions and temp tables|Emmanuel Cecchet|reviewers=Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20952F54-6730-49D8-99A3-1834697790B5@decibel.org|array_length|Jim C. Nasby}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810151933p445978b3td481a5422a2aebf4@mail.gmail.com|array_agg|Robert Haas}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|27bbfebe0810151633q1aac3ea8v864bea997f3cc5ec@mail.gmail.com|another version}} from Ian Caulfield and {{messageLink|1225045937.4434.21.camel@localhost.localdomain|yet another}} from Jeff Davis}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490878AC.1@dunslane.net|parallel restore|status=WIP|Andrew Dunstan}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48F53EC0.3020004@timbira.com|autovacuum and reloption|status=WIP|Euler Taveira de Oliveira|reviewers=Alvaro Herrera}}&lt;br /&gt;
&lt;br /&gt;
{{patch|162867790810170316l4eeecb0bq321dd771f8f4e661@mail.gmail.com|grouping sets|status=WIP|Pavel Stehule}}&lt;br /&gt;
&lt;br /&gt;
{{patch|6EEA43D22289484890D119821101B1DF2C1683@exchange20.mercury.ad.ubc.ca|Improve Performance of Multi-Batch Hash Join for Skewed Data Sets|Ramon Lawrence/Bryce Cutt}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48FC7E84.3080702@hagander.net|SSL cleanups/hostname verification|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49009D67.4040202@hagander.net|clientcert option for pg_hba|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|e4ccc24e0810222010p12bae2f4xa3a11cb2bc51bd89@mail.gmail.com|pg_standby support for compressed segments|Charles Duffy}}&lt;br /&gt;
&lt;br /&gt;
{{patch|162867790810260428p56d16352qa1ec5c4c5330f25c@mail.gmail.com|default values for function&#039;s parameters|Pavel Stehule}}&lt;br /&gt;
{{comment|Pavel Stehule| fix known bugs, currently only doc should be finished}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490394B7.6090503@lelarge.info|ALTER DATABASE WITH TABLESPACE Statement|Guillaume Lelarge}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.BSO.4.64.0810271955030.28764@leary.csoft.net|use new heap_(form/deform/modify)_tuple API|Kris Jurka|reviewers=Zdenek Kotala|status=Ready for commit}}&lt;br /&gt;
{{comment|Zdenek Kotala| It seems OK. Needs apply also {{messageLink|Pine.BSO.4.64.0810281721500.6833@leary.csoft.net|pfree patch.}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49076F39.1080502@hagander.net|regexp support in usermaps|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.BSO.4.64.0810281622240.9851@leary.csoft.net|don&#039;t use MAKE_PTR/OFFSET for shmem pointers|Kris Jurka}}&lt;br /&gt;
&lt;br /&gt;
{{patch|603c8f070810282045g7fa6bdf9p53f03114d49643d7@mail.gmail.com|bulk inserts - keep most recent page pinned|Robert Haas}}&lt;br /&gt;
{{comment|Robert Haas|based on work by Simon Riggs: [http://archives.postgresql.org/pgsql-hackers/2008-02/msg01080.php original idea],[http://archives.postgresql.org/pgsql-patches/2008-02/msg00140.php original patch], [http://archives.postgresql.org/pgsql-patches/2008-02/msg00154.php Tom Lane&#039;s comments]}}&lt;br /&gt;
{{comment|Robert Haas|Tom&#039;s comments on my [http://archives.postgresql.org/pgsql-hackers/2008-10/msg01276.php design proposal] are {{messageLink|17996.1225049097@sss.pgh.pa.us|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49086E4C.9030602@sun.com|htup and bufpage API clean up|Zdenek Kotala}}&lt;br /&gt;
{{comment|Zdenek Kotala|New version is {{messageLink|490875FA.4020709@sun.com|here}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49097338.2070700@gmail.com|SQL/MED compatible connection manager|Martin Pihlak}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081029164000.GL27466@fetter.org|pre-MED|David Fetter}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905AE17.7090305@enterprisedb.com|Visibility map, partial vacuums|status=WIP|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|49085327.5010608@enterprisedb.com|Updating FSM on recovery|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1225010283.21241.33.camel@localhost.localdomain|new correlation metric|Jeff Davis}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081029183248.GE4331@alvh.no-ip.org|Block-level CRC checks|Alvaro Herrera|status=WIP}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4909DFCE.1000702@sun.com|HeapTuple version extension + code cleanup|Zdenek Kotala}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4909B326.507@enterprisedb.com|Optimizing COPY with memchr()|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|87ljw5c0lx.fsf@oxford.xeocode.com|posix_fadvise|Gregory Stark}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4909726F.8000800@gmx.net|TABLE command|Peter Eisentraut}}&lt;br /&gt;
&lt;br /&gt;
{{patch|200810271936.m9RJaGW09544@momjian.us|libpq callback unregistration|Bruce Momjian}}&lt;br /&gt;
&lt;br /&gt;
{{patch|f205bb120810280833x340324d3m19a4f8aa65d822b@mail.gmail.com|FAQ_Solaris 1.28 to spanish|Emanuel CALVO FRANCO}}&lt;br /&gt;
&lt;br /&gt;
{{patch|3f0b79eb0810310436w360f0afdy76ff1499b177ce0d@mail.gmail.com|Synchronous log-shipping replication|Masao Fujii|reviewers=Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490B07BA.6030109@sigaev.ru|GIN fast insert|Teodor Sigaev, Oleg Bartunov}}&lt;br /&gt;
&lt;br /&gt;
{{CommitFestEndSection}}&lt;br /&gt;
&lt;br /&gt;
== Committed patches ==&lt;br /&gt;
{{CommitFestSectionNew}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20080803.114711.73374027.t-ishii@sraoss.co.jp|Common Table Expressions|Yoshiyuki Asaba|status=Committed 2008-10-04|reviewers=Jeff Davis}}&lt;br /&gt;
{{comment|David Fetter|README is {{messageLink|20080818.163852.105172778.t-ishii@sraoss.co.jp|here.}}}}&lt;br /&gt;
{{comment|David Fetter|Git repository is [http://git.postgresql.org/git/~davidfetter/cte/.git here.]}}&lt;br /&gt;
{{comment|David Fetter|[[CTEReadme]]}}&lt;br /&gt;
{{comment|David Fetter|[[CTESQLStandard| Fair Use from the draft SQL:2008 standard (WIP)]]}}&lt;br /&gt;
{{review|13449.1221589943@sss.pgh.pa.us|tgl|needs a good bit of work yet}}&lt;br /&gt;
&lt;br /&gt;
{{patch|Pine.GSO.4.64.0809152349440.19910@westnet.com|Add default_val to pg_settings|status=Committed 2008-10-06|Greg Smith|reviewers=Simon Riggs,Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|20081016102603.897D.52131E4D@oss.ntt.co.jp|Noisy _dosmaperror|status=Committed 2008-10-16|Takahiro Itagaki|reviewers=Tom Lane}}&lt;br /&gt;
&lt;br /&gt;
{{patch|b4e5ce320810151918g2acf69ebh9f80f4f2e1c203a0@mail.gmail.com|Memory leak on hashed agg rescan|status=Committed 2008-10-16|Neil Conway|reviewers=Tom Lane}}&lt;br /&gt;
{{review|10455.1224160007@sss.pgh.pa.us|Tom Lane|move some logic to separate function}}&lt;br /&gt;
&lt;br /&gt;
{{patch|1223383838.4747.154.camel@ebony.2ndQuadrant|Atomic subtransaction commit|status=Committed 2008-10-20|Simon Riggs|reviewers=Alvaro Herrera}} &lt;br /&gt;
&lt;br /&gt;
{{patch|3327.1224535092@sss.pgh.pa.us|add placeholder variables to planner|status=Committed 2008-10-22|Tom Lane}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48E271C5.7010907@hagander.net|pg_hba options parsing|status=Committed 2008-10-23|Magnus Hagander|reviewers=Bruce Momjian}}&lt;br /&gt;
{{comment|Robert Haas|{{messageLink|48F0DE8B.8030004@hagander.net|updated patch}}}}&lt;br /&gt;
&lt;br /&gt;
{{patch|48FC3994.8040809@hagander.net|libpq ssl -&amp;gt; clear fallback looses error messages|status=Committed 2008-10-27|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905D22D.9040001@hagander.net|better hba parsing error messages|status=Committed 2008-10-27|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905A1DE.5030102@hagander.net|remove crypt authentication|status=Committed 2008-10-28|Magnus Hagander}}&lt;br /&gt;
&lt;br /&gt;
{{patch|4905F515.3020208@gmx.net|Unicode escapes in literals|status=Committed 2008-10-29|Peter Eisentraut}}&lt;br /&gt;
&lt;br /&gt;
{{patch|490A138E.80100@enterprisedb.com|User defined I/O conversion casts|status=Committed 2008-10-31|Heikki Linnakangas}}&lt;br /&gt;
&lt;br /&gt;
{{CommitFestEndSection}}&lt;br /&gt;
&lt;br /&gt;
== Returned with Feedback ==&lt;br /&gt;
{{CommitFestSectionNew}}&lt;br /&gt;
&lt;br /&gt;
{{CommitFestEndSection}}&lt;/div&gt;</summary>
		<author><name>Umitanuki</name></author>
	</entry>
</feed>