applications that use FILE pointers.

WAL and the interaction of the new full_page_writes parameter with PITR.

The too-small WAL first sect1 has been merged with the one following
sect1 for clarity.

Some minor comments have been made in the WAL config section also.

Passes SGML make and proofread for typos.
Files changed:
patching file doc/src/sgml/backup.sgml
patching file doc/src/sgml/config.sgml
patching file doc/src/sgml/wal.sgml

Simon Riggs

that is too fragile.

syntax checking to plpgsql: check_sql_expr() wasn't being called by
make_select_stmt(), so that there was no SQL syntax check for SELECT
statements.

that is protected by a spinlock must be volatile, per recent discussion.

> * Prevent PQfnumber() from lowercasing unquoted the column name
>
>   PQfnumber() should never have been doing lowercasing, but historically
>   it has so we need a way to prevent it
>

make_restrictinfo_from_bitmapqual.  The likelihood of finding duplicates
seems much less than in the AND-subclause case, and the cost much higher,
because OR lists with hundreds or even thousands of subclauses are not
uncommon.  Per discussion with Ilia Kantor and andrew@supernews.

< * Prevent libpq's PQfnumber() from lowercasing the column name
<
<   One idea is to lowercase all identifiers except those that are
<   surrounded by quotes.
<

the wrong buffer dirty when trying to kill a dead index entry that's on
a page after the one it started on.  No risk of data corruption, just
inefficiency, but still a bug.

protected data structures and not using a volatile pointer for same.

pointers, to ensure that compilers won't rearrange accesses to occur
while we're not holding the buffer header spinlock.  It's probably
not necessary to mark volatile in every single place in bufmgr.c,
but better safe than sorry.  Per trouble report from Kevin Grittner.

Andrew Dunstan

<
< * Add code to detect an SMP machine and handle spinlocks accordingly
<   from distributted.net, http://www1.distributed.net/source,
<   in client/common/cpucheck.cpp
<
<   On SMP machines, it is possible that locks might be released shortly,
<   while on non-SMP machines, the backend should sleep so the process
<   holding the lock can complete and release it.

< 	o %Add dumping of comments on composite type columns
< 	o %Add dumping of comments on index columns
< 	o Stop dumping CASCADE on DROP TYPE commands in clean mode
> 	o %Add dumping of comments on index columns and composite type columns
604a603
> 	o Stop dumping CASCADE on DROP TYPE commands in clean mode

< 	o %Replace crude DELETE FROM method of pg_dumpall --clean for
<           cleaning of roles with separate DROP commands
608a607
>

<
> 	o Allow pg_dump --clean to drop roles that own objects or have
> 	  privileges

< * Prevent libpq's PQfnumber() from lowercasing the column name?
> * Prevent libpq's PQfnumber() from lowercasing the column name
>
>   One idea is to lowercase all identifiers except those that are
>   surrounded by quotes.
>

> 	o Add options like pg_restore -l and -L to pg_dump

> 	o Allow selection of individual object(s) of all types, not just
> 	  tables
> 	o In a selective dump, allow dumping of an object and all its
> 	  dependencies

must commit *after* autoconf, not before

update to beta3 before tagging ...

whether we seem to be running in a uniprocessor or multiprocessor.
The adjustment rules could probably still use further tweaking, but
I'm convinced this should be a win overall.

The pre-test has been shown to be a big loss on Opterons and at best a
wash on EM64T.

valid type information if they are asked to fetch the values part of a
pg_statistic slot; these arguments are unneeded if fetching only the
numbers part.  Use this to save a catcache lookup in btcostestimate,
which is looking like a bit of a hotspot in recent profiling.  Not a
big savings, but since it's essentially free, might as well do it.

A RestrictInfo representing an OR clause now contains two versions of
the contained expression, one with sub-RestrictInfos and one without.
clause_selectivity() should descend to the version with sub-RestrictInfos
so that it has a chance of caching its results for the OR's sub-clauses.
Failing to do so resulted in redundant planner effort.

emit when given the --clean option, in favor of individual DROP ROLE
commands.  The old technique could not possibly work in 8.1, and was
never a very good idea anyway IMHO.  The DROP ROLE approach has the
defect that the DROPs will fail for roles that own objects or have
privileges, but perhaps we can improve that later.

ie removing shared-dependency entries, should happen before non-rollbackable
ones.  That way a failure during the rollbackable part doesn't leave us
with inconsistent state.

traceable to grant options.  As per my earlier proposal, a GRANT made by
a role member has to be recorded as being granted by the role that actually
holds the grant option, and not the member.