Hi
Michael Banck wrote:
> I apparently managed to screw up so badly that no PQerrorMessage was
> set, so saw the above (which indeed has no error message after the
> colon).
Well, maybe that's a different bug, then: maybe we should print
something other than PQerrorMessage (or maybe PQerrorMessage should not
return empty!). Can you reproduce the problem?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services