PostgreSQL TODO List

====================

Current maintainer:Bruce Momjian (pgman@candle.pha.pa.us)

Last updated:Fri Jun 1600:04:49 EDT 2006

Last updated:Fri Jun 1612:59:22 EDT 2006

The most recent version of this document can be viewed at

http://www.postgresql.org/docs/faqs.TODO.html.

o Fix interval display to support values exceeding 2^31 hours

o Add overflow checking to timestamp and interval arithmetic

o Add ISO INTERVAL handling

http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php

o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO

SECOND

o Support ISO INTERVAL syntax if units cannot be determined from

<bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">

<h1><aname="section_1">PostgreSQL TODO List</a></h1>

<p>Current maintainer: Bruce Momjian (<ahref="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>

Last updated: Fri Jun 1600:04:49 EDT 2006

Last updated: Fri Jun 1612:59:22 EDT 2006

<p>The most recent version of this document can be viewed at<br/>

<ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.

</li><li>Fix interval display to support values exceeding 2^31 hours

</li><li>Add overflow checking to timestamp and interval arithmetic

</li><li>Add ISO INTERVAL handling

<li>-<em>Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO</em>

<p><ahref="http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php">http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php</a>

<li>-<em>Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO</em>

SECOND

</li><li>Support ISO INTERVAL syntax if units cannot be determined from

</li><li>Support ISO INTERVAL syntax if units cannot be determined from

the string, and are supplied after the string

<p> The SQL standard states that the units after the string

specify the units of the string, e.g. INTERVAL '2' MINUTE

range of units supported, e.g. PostgreSQL supports '1 year 1

hour', while the SQL standard does not.

</li><li>Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH

</li><li>Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS

</li><li>Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH

</li><li>Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS

INTERVAL MONTH), and this should return '12 months'

</li><li>Round or truncate values to the requested precision, e.g.

</li><li>Round or truncate values to the requested precision, e.g.

INTERVAL '11 months' AS YEAR should return one or zero

</li><li>Support precision, CREATE TABLE foo (a INTERVAL MONTH(3))

</li><li>Arrays

</li><li>Support precision, CREATE TABLE foo (a INTERVAL MONTH(3))

<li>-<em>Allow NULLs in arrays</em>

</li><li>Delay resolution of array expression's data type so assignment

<li>Arrays

<li>-<em>Allow NULLs in arrays</em>

</li><li>Delay resolution of array expression's data type so assignment

coercion can be performed on empty array expressions

</li><li>Binary Data

<li>Improve vacuum of large objects, like /contrib/vacuumlo?

</li><li>Add security checking for large objects

</li><li>Auto-delete large objects when referencing row is deleted

</li><li>Binary Data

<li>Improve vacuum of large objects, like /contrib/vacuumlo?

</li><li>Add security checking for large objects

</li><li>Auto-delete large objects when referencing row is deleted

<p> /contrib/lo offers this functionality.

</li><li>Allow read/write into TOAST values like large objects

</li><li>Allow read/write into TOAST values like large objects

<p> This requires the TOAST column to be stored EXTERNAL.

</li><li>Add API for 64-bit large object access

</li><li>Add API for 64-bit large object access

<p><ahref="http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php">http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php</a>

<h1><aname="section_5">Functions</a></h1>