<   posix_fadvise() [fadvise]
>   posix_fadvise()
>
>   Posix_fadvise() can control both sequential/random file caching and
>   free-behind behavior, but it is unclear how the setting affects other
>   backends that also have the file open, and the feature is not supported
>   on all operating systems.
>

Add explicit documentation of the recovery configuration settings.  Other
minor improvements in the PITR docs.  Simon Riggs, some editorialization
by Tom Lane.

< * CREATE TABLE AS can not determine column lengths from expressions [atttypmod]
> * Allow CREATE TABLE AS to determine column lengths for complex
>   expressions like SELECT col1 || col2

< * Automatically create rules on views so they are updateable, per SQL99 [view]
> * Automatically create rules on views so they are updateable, per SQL99
>
>   We can only auto-create rules for simple views.  For more complex
>   cases users will still have to write rules.
>

than erroring out.  This is the Unix behavior.

working as intended --- for some reason, FROM a.b.c was getting
parsed as if it were a function name and not a qualified name.
I think there must be a bug in bison, because it should have
complained that the grammar was ambiguous.  Anyway, fix it along
the same lines previously used for func_name vs columnref, and get
rid of the right-recursion in attrs that seems to have confused
bison.

shifting left by full word width gives zero.  Per bug report from
Tyson Thomson.

preserve double leading slashes on Win32.

e.g.    ////a////b => /a/b

actual executable location.  This allows people to continue to use
setups where, eg, postmaster is symlinked from a convenient place.
Per gripe from Josh Berkus.

won't have trivial differences in their common prefix.

tablespace clauses; this should improve compatibility of dump files.
Philip Warner, some rework by Tom Lane.

type-and-length coercion function, make sure that the coercion function
is told the correct typmod.  Fixes Kris Jurka's example of a domain
over bit(N).

* Allow database recovery where tablespaces can't be created

  When a pg_dump is restored, all tablespaces will attempt to be created
  in their original locations. If this fails, the user must be able to
  adjust the restore process.

duplicates sample entries from comments.

default on Win32.

everywhere not just some places, get rid of . and .. when joining path
sections together.  This should eliminate most of the ugly paths like
/foo/bar/./baz that we've been generating.

RestrictInfo nodes in the query expression.  Per example from James Robinson.

clause implicitly whenever one is not given explicitly.  Remove concept
of a schema having an associated tablespace, and simplify the rules for
selecting a default tablespace for a table or index.  It's now just
(a) explicit TABLESPACE clause; (b) default_tablespace if that's not an
empty string; (c) database's default.  This will allow pg_dump to use
SET commands instead of tablespace clauses to determine object locations
(but I didn't actually make it do so).  All per recent discussions.

<   one column or expression indexes, perhaps using per=index statistics
>   one column or expression indexes, perhaps using per-index statistics

< * Add transaction_timestamp(), statement_timestamp(), clock_timestamp() functionality
> * Add transaction_timestamp(), statement_timestamp(), clock_timestamp()
>   functionality
278c279
<   one column
>   one column or expression indexes, perhaps using per=index statistics
846a848
> * Remove kerberos4 from source tree?