* SMP scalability improvements

>   http://archives.postgresql.org/pgsql-hackers/2007-09/msg00206.php

* SMP scalability improvements

>   http://archives.postgresql.org/pgsql-hackers/2008-03/msg00361.php

>
> * SMP scalability improvements
>
>   http://archives.postgresql.org/pgsql-hackers/2007-07/msg00439.php

* Allow statistics last vacuum/analyze execution times to be displayed
  without requiring stats_row_level to be enabled

>
>   http://archives.postgresql.org/pgsql-docs/2007-04/msg00028.php
>

> * Improve reporting of UNION type mismatches
>
>   http://archives.postgresql.org/pgsql-hackers/2007-04/msg00944.php
>   http://archives.postgresql.org/pgsql-hackers/2008-03/msg00597.php

< 	o Allow pre/data/post files when dumping a single object, for
< 	  performance reasons
> 	o Allow pre/data/post files when schema and data are dumped
> 	  separately, for performance reasons

< 	o Support pgxs
> 	o Support pgxs when using MSVC

>   http://archives.postgresql.org/pgsql-patches/2008-02/msg00176.php

>
> * Avoid tuple some tuple copying in sort routines
>
>   http://archives.postgresql.org/pgsql-hackers/2008-02/msg01206.php

>
> * Sort large UPDATE/DELETEs so it is done in heap order
>
>   http://archives.postgresql.org/pgsql-hackers/2008-01/msg01119.php

* Do async I/O for faster random read-ahead of data

  Async I/O allows multiple I/O requests to be sent to the disk with
  results coming back asynchronously.

>   http://archives.postgresql.org/pgsql-patches/2008-01/msg00170.php

<
< * Avoid tuple some tuple copying in sort routines
<
<   http://archives.postgresql.org/pgsql-hackers/2008-02/msg01206.php

> 	o Allow pre/data/post files when dumping a single object, for
> 	  performance reasons
>
> 	  http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php
>

except that it returns the string 'NULL', rather than a SQL null, when called
with a null argument.  This is often a much more useful behavior for
constructing dynamic queries.  Add more discussion to the documentation
about how to use these functions.

Brendan Jurd

>
> 	o Fix MSVC NLS support, like for to_char()
>
> 	  http://archives.postgresql.org/pgsql-hackers/2008-02/msg00485.php
> 	  http://archives.postgresql.org/pgsql-patches/2008-02/msg00038.php

>
> * Improve WAL concurrency by increasing lock granularity
>
>   http://archives.postgresql.org/pgsql-hackers/2008-02/msg00556.php
>

>
> 	o Support pgxs

>
> * Avoid tuple some tuple copying in sort routines
>
>   http://archives.postgresql.org/pgsql-hackers/2008-02/msg01206.php

        o Add checks to prevent a CREATE RULE views on inherited tables

> 	  http://archives.postgresql.org/pgsql-general/2008-03/msg00077.php

with two new functions DCH_to_char and DCH_from_char that have less confusing
APIs.  Brendan Jurd

>
> 	o Add checks to prevent a CREATE RULE views on inherited tables
>
> 	  http://archives.postgresql.org/pgsql-general/2008-02/msg01420.php

* Simplify ability to create partitioned tables

>   http://archives.postgresql.org/pgsql-hackers/2008-01/msg00387.php

* Simplify ability to create partitioned tables

>   http://archives.postgresql.org/pgsql-hackers/2008-01/msg00248.php

>
> * Improve performance of shared invalidation queue for multiple CPUs
>
>   http://archives.postgresql.org/pgsql-performance/2008-01/msg00023.php

* Simplify ability to create partitioned tables

  This would allow creation of partitioned tables without requiring
  creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints
  for rapid partition selection.  Options could include range and hash
  partition selection.

>   http://archives.postgresql.org/pgsql-hackers/2008-01/msg00028.php
>   http://archives.postgresql.org/pgsql-hackers/2008-01/msg00413.php

for a very long time --- in current usage it's entirely redundant with the
name field.

the array decoration as the code had been doing.

(if they'd be visible to the current user in pg_stat_activity).

This might look like it's subject to race conditions, but it's actually
pretty safe because at the time DeadLockReport() is constructing the
report, we haven't yet aborted our transaction and so we can expect that
everyone else involved in the deadlock is still blocked on some lock.
(There are corner cases where that might not be true, such as a statement
timeout triggering in another backend before we finish reporting; but at
worst we'd report a misleading activity string, so it seems acceptable
considering the usefulness of reporting the queries.)

Original patch by Itagaki Takahiro, heavily modified by me.

>
> * Convert single quotes to apostrophes in the PDF documentation
>
>   http://archives.postgresql.org/pgsql-docs/2007-12/msg00059.php
>

>
> * Fix inconsistent precedence of =, >, and < compared to <>, >=, and <=
>
>   http://archives.postgresql.org/pgsql-bugs/2007-12/msg00145.php

>
> 	o Prevent SSL from sending network packets to avoid interference
> 	  with Win32 signal emulation
>
> 	  http://archives.postgresql.org/pgsql-hackers/2007-12/msg00455.php

2^31 blocks.  Also fix pg_relpages() for the same case.
Tatsuhito Kasahara

a new typedef TimeOffset to represent an intermediate time value.  It's
either int64 or double as appropriate, and in most usages will be measured
in microseconds or seconds the same as Timestamp.  We don't call it
Timestamp, though, since the value doesn't necessarily represent an absolute
time instant.

Warren Turkal

directly to all the member expressions, instead of the previous implementation
where the ARRAY[] constructor would infer a common element type and then we'd
coerce the finished array after the fact.  This has a number of benefits,
one being that we can allow an empty ARRAY[] construct so long as its
element type is specified by such a cast.

Brendan Jurd, minor fixes by me.