Time for a new CLSQL Release

Howdy Kevin,

I was hoping you could make a release for CLSQL (5.3.5 I guess) at some
point soon.  The patches that are up in master have been there for three
weeks, which seems enough time for anyone who wants to test to grab
them.  We have also been using those patches in our production
environment which has been fairly stable.

We have a few more sets of patches we would like to push up once, this
has been released.  After this release, it might be worthwhile to push
all our remaining patches up for a CLSQL 6 release (in a few more weeks).

The remaining patch sets add:
 * Add a new postgres backend based on cl-postgres (which allows the use
of the version 3 socket api, and command objects/parameters)
 * Change how database identifiers are emitted to hopefully make this
less brittle, and more easily intuitable
  * previously every code path that wanted to emit a database identifier
was responsible for coercing what was provided into a correctly escaped
string.  Sometimes two or three functions in a row were trying to
correctly quote and output that string.  I have tried to centralize this
type coersion and logic into a single code path.

These patches could affect backwards compatibility for some people and I
think having a clear release to point them to, would be helpful.  While
I think most users will not notice a difference, some people who were
trying to massage specific identifiers through the old, less predictable
system (like we were), might be affected.

Thanks very much for your help on this,
Russ Tyndall
Acceleration.net