Korry Douglas and Nikhil S

to have such entries, and want to be notified when we do...
Leave the plain bugfix in genbki.

Allow pltcl args to spi_prepare and plpython args to plpy.prepare to be standard type aliases as well as those known in pg_type. Similar to recent change in plperl.

      o Allow row and record variables to be set to NULL constants,
        and allow NULL tests on such variables

BLCKSZ value.

>
> * Consider decreasing the amount of memory used by PrivateRefCount
>
>   http://archives.postgresql.org/pgsql-hackers/2006-11/msg00797.php
>   http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php
>

shared link line.

> * Increase locking when DROPing objects so dependent objects cannot
>   get dropped while the DROP operation is happening
>
>   http://archives.postgresql.org/pgsql-hackers/2007-01/msg00937.php

        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