o Allow UPDATE/DELETE WHERE CURRENT OF cursor
> 	  http://archives.postgresql.org/pgsql-hackers/2007-01/msg01014.php

>
> * Add missing operators for geometric data types
>
>   Some geometric types do not have the full suite of geometric operators,
>   e.g. box @> point
>

bytes and backslashes, remove "ASCII" mention.  Backpatch to 8.2.X.

Backpatch to 8.2.X.

environment variables.  Backpatch to 8.2.X.

file permissions on Windows.

storing mostly-redundant Query trees in prepared statements, portals, etc.
To replace Query, a new node type called PlannedStmt is inserted by the
planner at the top of a completed plan tree; this carries just the fields of
Query that are still needed at runtime.  The statement lists kept in portals
etc. now consist of intermixed PlannedStmt and bare utility-statement nodes
--- no Query.  This incidentally allows us to remove some fields from Query
and Plan nodes that shouldn't have been there in the first place.

Still to do: simplify the execution-time range table; at the moment the
range table passed to the executor still contains Query trees for subqueries.

initdb forced due to change of stored rules.

< 	o Check .pgpass file permissions
>

permission, per Magnus.

anyone cares because the last history change was for PostgreSQL 7.1.

<
> 	o Check .pgpass file permissions

> * Fix IS OF so it matches the ISO specification, and add documentation
>
>   http://archives.postgresql.org/pgsql-patches/2003-08/msg00060.php
>   http://archives.postgresql.org/pgsql-hackers/2007-02/msg00060.php

ISO SQL behavior. Backpatch removal to 8.2.X.

by Bernd Helmle

< 	o ARRAY[[1,2],[3,4]])[1] should return the same values as
< 	  ARRAY[[1,2],[3,4]])[1:1];
<

    <P><I>src/Makefile.custom</I> can be used to set environment variables,
    like <I>CUSTOM_COPT</I>, that are used for every compile.

Julian technically is noon to noon.

< * Consider allowing configuration of TOAST thresholds
> * Allow user configuration of TOAST thresholds

> * Consider allowing configuration of TOAST thresholds
>
>   http://archives.postgresql.org/pgsql-hackers/2007-02/msg00213.php
>

> * Allow UPDATEs on only non-referential integrity columns not to conflict
>   with referential integrity locks
>
>   http://archives.postgresql.org/pgsql-hackers/2007-02/msg00073.php

> * Allow INSERT/UPDATE ... RETURNING inside a SELECT 'FROM' clause
>
>   http://archives.postgresql.org/pgsql-general/2006-09/msg00803.php
>   http://archives.postgresql.org/pgsql-hackers/2006-10/msg00693.php
>

if you do not trust local users.

EXTRACT().

> * -Add ISO day of week format 'ID' to to_char() where Monday = 1

> * -Add a field 'isoyear' to extract(), based on the ISO week

< 	o Add long file support for binary pg_dump output
<
< 	  While Win32 supports 64-bit files, the MinGW API does not,
< 	  meaning we have to build an fseeko replacement on top of the
< 	  Win32 API, and we have to make sure MinGW handles it.  Another
< 	  option is to wait for the MinGW project to fix it, or use the
< 	  code from the LibGW32C project as a guide.
<
< 	  http://archives.postgresql.org/pgsql-hackers/2006-12/msg00551.php
<
> 	o -Add long file support for binary pg_dump output

binary dump formats.

this code was last gone over, there wasn't really any alternative to
globals because we didn't have the PlannerInfo struct being passed all
through the planner code.  Now that we do, we can restructure things
to avoid non-reentrancy.  I'm fooling with this because otherwise I'd
have had to add another global variable for the planned compact
range table list.

Per example from Jeff Ross.