1 I found that my database recently started generating extra backslashes
2 on roundtrips to the database.
4 The reason seems to be a change to standards_conforming_strings variable in postgresl
5 Beginning in PostgreSQL 9.1, the default is on (prior releases defaulted to off)
8 https://stackoverflow.com/a/3049139
10 * I created a new protocol function (database-escape-backslashes database)
11 * I changed the the generic mysql and postgres databases to return T
12 * I made the postgresql-socket-3 backend check for standards_conforming_string
13 which is exposed in the underlying cl-postgres connection
14 * It seems likely that postgresql-socket-3 could always return NIL, as
15 cl-postgres would probably handle this escaping anyway