>
> 	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.

framework to keep track of snapshots in use.

pg_dumpall from attaching TABLESPACE options to CREATE DATABASE commands.

dumps can be loaded into databases without the same tablespaces that the
source had.  The option acts by suppressing all "SET default_tablespace"
commands, and also CREATE TABLESPACE commands in pg_dumpall's case.

Gavin Roy, with documentation and minor fixes by me.

Removed one include file from connect-test1.

ISO_8859-5 <-> MULE_INTERNAL conversion tables.

This was discovered when trying to convert a string containing those characters
from ISO_8859-5 to Windows-1251, because we use MULE_INTERNAL/KOI8R as an
intermediate encoding between those two.

While the missing "Yo" was just an omission in the conversion tables, there are
a few other characters like the "Numero" sign ("No" as a single character) that
exists in all the other cyrillic encodings (win1251, ISO_8859-5 and cp866), but
not in KOI8R. Added comments about that.

Patch by Sergey Burladyan. Back-patch to 7.4.

is redundant because autovacuum now always analyzes a single table per
transaction.

case where there is a match to the pattern overall but the user has specified
a parenthesized subexpression and that subexpression hasn't got a match.
An example is substring('foo' from 'foo(bar)?').  This should return NULL,
since (bar) isn't matched, but it was mistakenly returning the whole-pattern
match instead (ie, 'foo').  Per bug #4044 from Rui Martins.

This has been broken since the beginning; patch in all supported versions.
The old behavior was sufficiently inconsistent that it's impossible to believe
anyone is depending on it.

except that lob's oid can be specified.

Change Copyright owner from mine to PostgreSQL Global Development Group
Fix minor message typo

* Experiment with multi-threaded backend better I/O utilization

  This would allow a single query to make use of multiple I/O channels
  simultaneously.  One idea is to create a background reader that can
  pre-fetch sequential and index scan pages needed by other backends.
  This could be expanded to allow concurrent reads from multiple devices
  in a partitioned table.

* Experiment with multi-threaded backend better CPU utilization

  This would allow several CPUs to be used for a single query, such as
  for sorting or query execution.