Bug 285 fix move set race condition.

During a move set it is possible on subscriber node, that isn't the
old or new origin, for remoteWorkerThread_$oldorigin to start
processing a SYNC event before the ACCEPT_SET is processed
by the remoteWorkerThread_$neworigin.  If the ACCEPT_SET
transaction then commits before the update sl_setsync
query is executed by the remoteWorkertThread_$oldorigin
the update will update a row for the new origin when
it intends to update the old origin.  This messes up
sl_setsync.

This change will add a condition to the WHERE clause so
a remoteWorkerThread won't UPDATE rows for a different
origin
updating to release 2.2.0 B3
fixing bug number
fmgr_info() must be called in the applyCacheContext.

Subsequent calls using the FmgrInfo structure may add more
sub elements to the info. This will be allocated in the same
memory context, the fmgr_info() call was made in. That
context must exist at least long enough as the FmgrInfo
call itself exists.
updates to docs and win32 makefile for MS-Windows.
(cherry picked from commit aee311a97a2b11ab4b555943ae0e49fb21c449ff)

Conflicts:

	doc/adminguide/installation.sgml
Add a regression test that ensures DDL is purging the apply cache.
Merge branch 'master' of ssh://git.postgresql.org/slony1-engine
Bug 286 PG 9.3 now takes two arguments on LookupExplicitNamespace

Add a configure check to determine if we have the 1 or 2 argument
version of LookupExplicitNamespace and pass the proper number
of arguments
Merge branch 'master' of ssh://git.postgresql.org/slony1-engine
Merge branch 'master' of github.com:cbbrowne/slony1-engine
Updating release notes for bug 286
Merge branch 'master' of ssh://git.postgresql.org/slony1-engine