This was due to incomplete implementation of rowcount reporting
for RMV, which was due to initial waffling on whether it should
be provided.  It seems unlikely to be a useful or universally
available  number as more sophisticated techniques for maintaining
matviews are added, so remove the partial support rather than
completing it.

Per report of Jeevan Chalke, but with a different fix

Continue to allow a request for synchronous
checkpoints as a mechanism in case of problems.

Erikjan Rijkers

Adrian Schreyer

Alvaro Herrera

This is new in 9.3devel.

Andres Freund

Erwin Brandstetter

LANGUAGE 'plpgsql' no longer works.  The single quotes need to be
removed.

Erwin Brandstetter

Split log shipping speed improvement and fail-over speed improvement items.

Per request from Simon

Already fixed in back branch.

Move commit_delay, fix Zoltan's name, and adjust range type histogram
text.

Typo fix from David Fetter.

When creating or manipulating a cached plan for a transaction control
command (particularly ROLLBACK), we must not perform any catalog accesses,
since we might be in an aborted transaction.  However, plancache.c busily
saved or examined the search_path for every cached plan.  If we were
unlucky enough to do this at a moment where the path's expansion into
schema OIDs wasn't already cached, we'd do some catalog accesses; and with
some more bad luck such as an ill-timed signal arrival, that could lead to
crashes or Assert failures, as exhibited in bug #8095 from Nachiket Vaidya.
Fortunately, there's no real need to consider the search path for such
commands, so we can just skip the relevant steps when the subject statement
is a TransactionStmt.  This is somewhat related to bug #5269, though the
failure happens during initial cached-plan creation rather than
revalidation.

This bug has been there since the plan cache was invented, so back-patch
to all supported branches.

More to go.

Forgotten in previous commit.

No links added yet.

suggested by Jov

In most cases, these were just references to the SQL standard in
general.  In a few cases, a contrast was made between SQL92 and later
standards -- those have been kept unchanged.

If an FDW fails to take special measures with a CurrentOfExpr, we will
end up trying to execute it as an ordinary qual, which was being treated
as a purely internal failure condition.  Provide a more user-oriented
error message for such cases.

Undo thinko in commit 87306184.
Per bug #8098 from Catherine Devlin.

Fabrízio de Royes Mello

Only adjusted the user-exposed messages and documentation,  not all
source code comments.

We might eventually allow checksum to no-checksum upgrades.

KaiGai Kohei

KaiGai Kohei, based on a suggestion from Álvaro Herrera

The return type of PQgetssl() was changed from SSL* to void* a long time
ago, but the documentation was not updated.

This saves some memory from each index relcache entry. At least on a 64-bit
machine, it saves just enough to shrink a typical relcache entry's memory
usage from 2k to 1k. That's nice if you have a lot of backends and a lot of
indexes.

When parse_hba_line's return type was changed from bool to a pointer,
the MANDATORY_AUTH_ARG macro wasn't adjusted.

Per complaint from Hubert Depesz Lubaczewski.

Catalog version bumped.

Per gripe from Tom Lane.

The initial coding just descended the index if any of the target trigrams
were possibly present at the next level down.  But actually we can apply
trigramsMatchGraph() so as to take advantage of AND requirements when there
are some.  The input data might contain false positive matches, but that
can only result in a false positive result, not false negative, so it's
safe to do it this way.

Alexander Korotkov