Add back in find_my_exec() support on platforms that include pgport.
find_my_exec, a postgresql pgport function is again used to find the
location of the slonik binary to locate the share directory.
This is for installs where the install location is not known at
compile time.

Some distributions don't include pgport, this is disabled by default
if you compile with pgport support set to yes (a configure option/check)
then this will be enabled.

Patch submitted by Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
(cherry picked from commit b034434e6279da67008402575ed768a666b827a9)

Conflicts:

	configure.ac
additional cleanups for pgport find_my_exec support

Clean up configure messaging and avoid a compiler warning by
checking for HAVE_PGPORT after config.h is included
(cherry picked from commit be933801d527caa7c88df622b6ec351668189281)

Conflicts:

	RELEASE
	src/slonik/slonik.c
Fix for bug282.

There was a problem with the new COPY protocol when
a data type or domain used in a replicated column
is not in slon's search_path. SPI does not provide
a mechanism to get the namespace name of a columns
data type.

Instead of adding explicit type casting to the apply
queries and handing the data in as TEXT Datums, we
now use the same technique that PL/pgSQL uses at
at least since 8.3 and convert the TEXT datums into
the requested data type ourselves.
Fix for bug273

Do not force the event provider to be part of the providers
unless we don't find any provider at all otherwise.
Bug #284 - fixes to tutorial
Merge branch 'bug273'
Merge branch 'bug282'
Add release note material on bugs 273, 282
Merge branch 'master' of git://git.postgresql.org/git/slony1-engine