Remove `programFindLocation` and `hookedPrograms` calls from Setup.hs
Merge pull request #11 from mkscrg/master

Remove `programFindLocation` and `hookedPrograms` calls from Setup.hs
Bump Version
Update postgresql-libpq.cabal

Fix issue #12
Credit goes to the maintainer of the OpenBSD package, David Coppa.
Tested on OpenBSD 5.4-release
Update postgresql-libpq.cabal

Conditional added for OpenBSD (as in Leon Smith's comment to pull request #13).
Works on OpenBSD 5.4-release and Debian "wheezy".
Merge pull request #13 from AlexanderAA/master

Also worth linking to a discussion of these issues on the OpenBSD mailing list:

http://openbsd.7691.n7.nabble.com/fix-hs-postgresql-libpq-after-kerberos-update-td230192.html
Bump version to 0.8.2.5
Eliminate closures creation in getvalue

This should be a small but significant optimization;  however getvalue'
still appears to be faster, at least for short strings.
Eliminate more closures
Version 0.8.2.6
More optimizations

Saved a bit more than 6KB of object code on 64-bit ghc-7.6.3 on Linux

    617584 -> 611184

The bulk of this from the strictness annotations inside execParams,
execPrepared, sendQueryParams, and sendqueryPrepared,  for ~300 bytes
per character.
Copy the error message returned by cancel

If my experience with getvalue is any indicator,  this is likely
faster (at least in the single-threaded case).   And as a nice
bonus, the object code is a bit smaller
More optimizations

Further reduced the object code size by a bit over 2 kilobytes, from
609632 bytes to 607560 on my machine (64-bit GHC 7.6.3 on Linux)

Also,  it may be worth deprecating oidValue,  as it's not terribly
relevant anymore:  the default is to create tables without OIDs,
and RETURNING is a better solution anyway.
Remove oidValue

This function hasn't been very relevant for a *long* time now,  and
we'll be dropping support for libpq 8.4 real soon.

You can fetch oids using RETURNING since postgresql 8.3,  and the
default has been to create tables without oids for some time before
that.   So while recent libpqs still have oidValue,  and you can
use newer libpqs to connect to older postgresqls,  I still very
much doubt this will impact anybody.

In particular,  none of the reverse dependencies of postgresql-libpq
on hackage make use of oidValue.  If anybody really desperately
needs this function,  then it should be no difficulty to write a
separate binding for it.
Add escapeIdentifier

There's probably a lot of locations in postgresql-libpq that need a
mask_ to avoid memory leaks in the presence of asynchronous exceptions.
More optimizations
Use withResult more consistently
Version 0.9.0.0
Merge branch 'master' into async
First cut at re-implementing PQexec in terms of the non-blocking API

It's almost but not quite complete.  Two missing parts: translated
strings and concatenating error messages if exec returns more than
one fatal error.

Unfortunately it depends on libpq internals.