This commit breaks any code that assumes that the mere act of forming a tuple
(without writing it to disk) does not "toast" any fields.  While all available
regression tests pass, I'm not totally sure that we've fixed every nook and
cranny, especially in contrib.

Greg Stark with some help from Tom Lane

output to match.

with errorlevel 1 is >= 1 checks failed.

of tests. Per Andrew Dunstan.

* Reduce WAL traffic so only modified values are written rather than
  entire rows
>
>   http://archives.postgresql.org/pgsql-hackers/2007-03/msg01589.php
>

installation.

    <H3 id="item3.7">3.7) What computer hardware should I use?</H3>

It removes last remaining casts inside struct definitions.
Such usage is bad practice, as it hides problems from compiler.

Reason for the cast is popular practice in some circles
to define functions as foo(MyObj *) instead of foo(PyObject *)
thus avoiding a local variable inside functions and make
direct calling easier.  As pl/python does not use such style,
the casts were unnecessary from the start.


Marko Kreen

Per Andrew Dunstan.

CONCURRENTLY.

Gregory Stark

are in their commit critical sections via flags in the ProcArray.  Checkpoint
can watch the ProcArray to determine when it's safe to proceed.  This is
a considerably better solution to the original problem of race conditions
between checkpoint and transaction commit: it speeds up commit, since there's
one less lock to fool with, and it prevents the problem of checkpoint being
delayed indefinitely when there's a constant flow of commits.  Heikki, with
some kibitzing from Tom.

> 		o -Allow PL/PythonU to return boolean rather than 1/0

Marko Kreen

changes in Python.

Marko Kreen

Add the latter to the values checked in pg_control, since it can't be changed
without invalidating toast table content.  This commit in itself shouldn't
change any behavior, but it lays some necessary groundwork for experimentation
with these toast-control numbers.

Note: while TOAST_TUPLE_THRESHOLD can now be changed without initdb, some
thought still needs to be given to needs_toast_table() in toasting.c before
unleashing random changes.

< * Add transaction_idle_timeout GUC so locks are not held for long
> * Add idle_in_transaction_timeout GUC so locks are not held for long

< * Add idle_timeout GUC so locks are not held for log periods of time
> * Add transaction_idle_timeout GUC so locks are not held for long
>   periods of time

> * Allow all data types to cast to and from TEXT
>
>   http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php
>
>

>
> * Add idle_timeout GUC so locks are not held for log periods of time

        o Allow UPDATE tab SET ROW (col, ...) = (SELECT...)
<
> 	  http://archives.postgresql.org/pgsql-hackers/2007-03/msg00865.php

        o Allow commenting of variables in postgresql.conf to restore them
          to defaults
> 	  http://archives.postgresql.org/pgsql-patches/2007-03/msg00180.php

          o Allow a warm standby system to also allow read-only
statements
            [pitr]
> 	    http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php

* Improve speed with indexes

  For large table adjustments during VACUUM FULL, it is faster to cluster
  or reindex rather than update the index.  Also, index updates can bloat
  the index.

>
>   http://archives.postgresql.org/pgsql-hackers/2007-03/msg00024.php

> 	o Have timestamp subtraction not call justify_hours()?
>
> 	  http://archives.postgresql.org/pgsql-sql/2006-10/msg00059.php
>
< 	o Add overflow checking to timestamp and interval arithmetic
> 	o Add overflow checking to timestamp and interval arithmetic

schema.relation, because the notify code only honors the relation name.
schema.relation will now generate a syntax error.

Check length of enum literals on definition and input to make sure they will fit in a name field and not cause syscache errors.

< 		o Add table function support to pltcl, plpython
> 		o Add table function support to pltcl, plpythonu
< 		o Add PL/Python tracebacks
> 		o Add PL/PythonU tracebacks
< 		o Allow PL/Python to return boolean rather than 1/0
> 		o Allow PL/PythonU to return boolean rather than 1/0

> * Fix to_date()-related functions to consistently issue errors
>
>   http://archives.postgresql.org/pgsql-hackers/2007-02/msg00915.php
>

>
> 		o Allow PL/Python to return boolean rather than 1/0
>
> 		  http://archives.postgresql.org/pgsql-patches/2007-01/msg00596.php
>

>
> * Consider reducing memory used for shared buffer reference count
>
>   http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php

	o Allow RETURN to return row or record functions

> 		o Allow RETURN to return row or record functions
> 		  http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php
> 		  http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php

return void ends with a SELECT, if that SELECT has a single result that is
also of type void.  Without this, it's hard to write a void function that
calls another void function.  Per gripe from Peter.

Back-patch as far as 8.0.

< * Support a data type with specific enumerated values (ENUM)
<
<   http://archives.postgresql.org/pgsql-hackers/2006-08/msg00979.php
<
> * -Support a data type with specific enumerated values (ENUM)

>
> 	  http://archives.postgresql.org/pgsql-hackers/2007-03/msg01803.php

some index terms.

for "vcregress check" to work.
Per report from Dave Page.

Per report from Listmail <lists@peufeu.com>