Leon P Smith

Well, there is an argument for making all postgresql-simple FromField instances compatible with `unknown`, taking the optimistic instead of pessimistic route to type checking. An "actual" type error would be...

> @lpsmith also, is there any way to allow the users of pg-simple to pick between two versions of HStoreList and HStoreMap -- one for (Text, Text) and the other...

Sorry, life's been pretty crazy for me the last year, and I've not been paying enough attention to my open source efforts. So I do apologize for ignoring this issue...

Argh, libpq versioning stuff really kinda gets me. On the one hand, there are features that I would like to use in newer versions, but I'm also not ready to...

Ahh yes, sorry for not taking a peek at this a bit sooner. Nothing too wrong with this patch in principle, but in practice, IIRC, the `exceptions` package has a...

Well, typically it means that the connection vanished, without receiving an error message from the database backend. `postgresql-simple` will generate a `IOError` in this case, instead of a `SQLError`. How...

Well, what I'm saying is (if necessary) turn on logging on the postgresql server side of things, and check the error logs there too. This particular exception is an `IOError`,...

Also, while it's certainly a worthy goal to write a daemon that never crashes, in practice you probably still want to have a supervisor process that will detect when a...

Well, I didn't read the whole thread carefully, but I don't think we have any evidence that the current issue is related to the psycopg one that you linked, and...

Also, in many distributions, SSL will by default be used in a situation like this; so if you do a packet capture, you may want to include [`sslmode=disable`](http://www.postgresql.org/docs/9.3/static/libpq-connect.html#LIBPQ-CONNECT-SSLMODE) in your...