This fixes references to 7.1.3 (I think).  It also
modifies the japanese
FAQ, so I'm not sure if that's done correctly.

Chris

please apply.

Andreas

> * Prevent SIGHUP and 'pg_ctl reload' from changing command line
>   specified parameters to postgresql.conf defaults

and doesn't make sense strictly speaking.

> * Allow ORDER BY ... LIMIT to select top values without sort or index

> * -Allow LOCK TABLE tab1, tab2, tab3 so all tables locked in unison

> 	o Allow UPDATE/DELETE WHERE CURRENT OF cursor using per-cursor tid

> 	o Allow DELETE WHERE CURRENT OF cursor using per-cursor tid
> 	  stored in the backend

> * Increase identifier length (NAMEDATALEN) if small performance hit,
>   perhaps to standard length of 128;  change struct pgNotify to use pid
>   first, breaks notify API;

> * Increase identifier length (NAMEDATALEN) if small performance hit;
>   change struct pgNotify to use pid first, breaks notify API

> * Evaluate AIX cs() spinlock macro for performance optimizations (Tatsuo)

> * Reorder postgresql.conf WAL items in order of importance
> * Remove wal_files postgresql.conf option because WAL files are now recycled
> * Find proper defaults for postgresql.conf WAL entries
> * Add checkpoint_min_warning postgresql.conf option to warn about checkpoints
>   that are too frequent

<   http://www1.distributed.net/source, in client/common/cpucheck.cpp
---
>   from distributted.net, http://www1.distributed.net/source,
>   in client/common/cpucheck.cpp

> * Add code to detect an SMP machine and handle spinlocks accordingly

options.  Document --with-pam and --enable-depend, do some minor
copy-editing.

> * Make IN/NOT IN have similar performance to EXISTS/NOT EXISTS [exists]

choke at 2Gb of output.  From Andrew Sullivan.

> * Use thread-safe crypt() in libpq, if available