fetch/move in scan.l.

Report from Josh Tolley.

> * Simplify ability to create partitioned tables
>
>   This would allow creation of partitioned tables without requiring
>   creation of rules for INSERT/UPDATE/DELETE, and constraints for
>   rapid partition selection.  Options could include range and hash
>   partition selection.
>
> * Allow auto-selection of partitioned tables for min/max() operations

--- was part of autovacuum default 'on' patch that was reverted, but we
want this part.

Peter Eisentraut

possible autovacuum use.

>
> 	  http://archives.postgresql.org/pgsql-hackers/2006-08/msg01852.php

/contrib/tsearch2.

Teodor Sigaev

Kai Londenberg, modified by Joe Conway

multiple columns

Susanne Ebrecht

< Last updated:		Sat Sep  2 08:31:04 EDT 2006
> Last updated:		Sat Sep  2 16:31:46 EDT 2006
< 	o Allow UPDATE tab SET ROW (col, ...) = (...) for updating multiple
< 	  columns
> 	o -Allow UPDATE tab SET ROW (col, ...) = (val, ...) for updating
> 	  multiple columns
> 	o Allow UPDATE tab SET ROW (col, ...) = (SELECT...)
<           A subselect can also be used as the value source.

Dhanaraj M

  Suppress some NOTICE messages from REINDEX command.

  Euler Taveira de Oliveira

overhead for every connection, per Tom.

RETURNING play nice with views/rules.  To wit, have the rule rewriter
rewrite any RETURNING clause found in a rule to produce what the rule's
triggering query asked for in its RETURNING clause, in particular drop
the RETURNING clause if no RETURNING in the triggering query.  This
leaves the responsibility for knowing how to produce the view's output
columns on the rule author, without requiring any fundamental changes
in rule semantics such as adding new rule event types would do.  The
initial implementation constrains things to ensure that there is
exactly one, unconditionally invoked RETURNING clause among the rules
for an event --- later we might be able to relax that, but for a post
feature freeze fix it seems better to minimize how much invention we do.
Per gripe from Jaime Casanova.

index page contents.

Satoshi Nagayasu

"server_version" but uses the handy PG_VERSION_NUM which allows apps to
do things like if ($version >= 80200) without having to parse apart the
value of server_version themselves.

Greg Sabino Mullane greg@turnstep.com

< 		o -Allow PL/python to composite types and result sets
> 		o -Allow PL/python to return composite types and result sets

Sven Suursoho

                o -Allow PL/python to composite types and result sets

Euler Taveira de Oliveira

didn't create a dependency from the new conversion to its schema.  Back-patch
to all supported releases.

COPY SELECT work done by Zoltan Boszormenyi

< Last updated:		Tue Aug 29 12:21:52 EDT 2006
> Last updated:		Wed Aug 30 20:34:28 EDT 2006
< 	o Allow COPY (SELECT ...) TO 'filename'
<
< 	  COPY should also be able to output views using COPY (SELECT
< 	  * FROM view) TO 'filename' internally.
< 	  http://archives.postgresql.org/pgsql-patches/2005-09/msg00148.php
> 	o -Allow COPY (SELECT ...) TO 'filename'

Bernd Helmle

and other special flags on Windows.  May fix intermittent 'Permission
denied' errors.  Magnus Hagander

the pager before reporting the error.

queries via a cursor, fetching a limited number of rows at a time and
therefore not risking exhausting memory.  A disadvantage of the scheme
is that 'aligned' output mode will align each group of rows independently
leading to odd-looking output, but all the other output formats work
reasonably well.  Chris Mair, with some additional hacking by moi.

Fix printing of NULL bind parameters, use "NULL".

> 	o Turn on by default

existing for backend GUC variables, and use this to eliminate repeated
fetching/parsing of psql variables in psql's inner loops.  In a trivial
test with lots of 'select 1;' commands, psql's CPU time went down almost
10%, although of course the effect on total elapsed time was much less.
Per discussion about how to ensure the upcoming FETCH_COUNT patch doesn't
cost any performance when not being used.