Revert "Bug 255."

This reverts commit e689d4fa5f1b4b0eeb9e3f2061b8ba29e5729bb7.
We remove explicit support for 9.1.
The patch in question seemed to cause failures under heavy testing
with the disorder MoveSet test (on occasion).
Fixing documentation error (The clone finish page
used 'clone prepare' in the synopsis)
bug 294 - fixing documentation error - we just added set 2

Conflicts:
	doc/adminguide/addthings.sgml
Fixing documentation according to bug 293.

http://www.slony.info/bugzilla/show_bug.cgi?id=293
Only include the libpq header directory OR the server header directory but not both

This addresses bug 315 where a debian install had libpq-dev 9.3 installed
and postgresql-server-dev 8.4 installed.  The libpq headers are in /usr/include/postgresql
but the server headers are in /usr/lib/postgresql/8.4/server.

configure checks were failing because we were pulling in a mixutre of headers
from both versions.  The only slony component that needs the server
headers are the backend functions and they shouldn't need to use libpq headers.

This patch sets CPPFLAGS as approriate for one or the other but not both

Conflicts:
	Makefile.global.in
	RELEASE
Use server includes for pgport when building slonik

When building with --with-pgport slonik needs to include port.h
port.h is normally found under the server include directory but
some distributions (ie debian libpq-dev) also include it in
/usr/include/postgresql

The fix for bug 315 removed the server include paths from
all client programs including slonik.  This went too far,
the actual issue with bug 315 was src/backend failing because
it pulled in the client headers.

If we are building with pgport we will pull in the server
include directories for slonik
updating version to 2.0.8
fixing release notes