The previous coding failed in various scenarios possibly including vpath
builds and doing make install without preceding make all.

Takahiro Itagaki

more appropriate place for exclusion constraints.

Original patch by Fujii Masao, with heavy editing and bitrot-fixing
after my other commit.

"replication" are quoted in pg_hba.conf, they lose their special meaning.

loop in standby mode, trying to restore from archive, pg_xlog and
streaming.

Move sections around to make the high availability chapter more
coherent: the most prominent part is now a "Log-Shipping Standby Servers"
section that describes what a standby server is (like the old
"Warm Standby Servers for High Availability" section), and how to
set up a warm standby server, including streaming replication, using the
built-in standby mode. The pg_standby method is desribed in another
section called "Alternative method for log shipping", with the added
caveat that it doesn't work with streaming replication.

It is no longer installed by default, but included in "make world"/"make
install-world".  Documentation updated accordingly.

Also, fix vpathsearch function to work when calling make install-docs
without previous make docs.

requested by Andrew Lardinois

Similar information already appears in the PL/Perl and PL/Tcl chapters.

suggested by Steve White (bug #5272)

by a superuser -- "ALTER USER f RESET setting" already disallows removing such a
setting.

Apply the same treatment to ALTER DATABASE d RESET ALL when run by a database
owner that's not superuser.

writes. The first worker still uses "pgbench_log.<pid>" for the name, but
additional workers use "pgbench_log.<pid>.<serial-number>" instead.

Reported by Greg Smith.

consistency.

Gabrielle (Roth)

Document this restriction.

Also update tagging instructions, and add id tags to a few documentation
sections.

did with server-side languages.

Docs were unclear on whether or not database=replication was required,
nor did they mention the FATAL error this causes if database parameter is
mentioned explicitly, whatever its value.

with a few strategically placed pg_verifymbstr calls.

Also make a couple other minor editorial improvements.

in recovery_end_command, it always came out as 0 because InRedo was
cleared before recovery_end_command was executed. Also, always take
ControlFileLock when reading checkpoint location for %r.

The recovery_end_command bug and the missing locking was present in 8.4
as well, that part of this patch will be backported separately.

Fujii Masao

Also fix and uncomment an old example of creating a GIST index, and make
a couple of other minor editorial adjustments.