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>

pg_type.typtype whereever practical.  Tom Dunstan, with some kibitzing
from Tom Lane.

Refactor and document the remaining mapping code.

New view pg_stat_bgwriter, and the functions required to build it.

Jun Kuwamura

add link to libpq SSL does from server docs.

Backpatch to 8.2.X.

will be released by transaction abort before _bt_end_vacuum gets called.
If either of these "can't happen" errors actually happened, we'd freeze up
trying to acquire an already-held lock.  Latest word is that this does
not explain Martin Pitt's trouble report, but it still looks like a bug.

pg_valid_server_encoding() returns the same result if the encoding is
valid.

ITAGAKI Takahiro

* Reduce storage space for small NUMERICs
>   http://archives.postgresql.org/pgsql-patches/2007-02/msg00505.php

> * Reduce storage space for small NUMERICs
>
>   http://archives.postgresql.org/pgsql-hackers/2007-02/msg01331.php
>

< 	o Add more logical syntax CLUSTER table USING index;
> 	o Add more logical syntax CLUSTER table USING index;