Hi, Kevin Grittner wrote:
Not sure what's relevant there. Entire file tarball attached.
Due to reasons mentioned in this thread as well, I've decided to use psql to connect to the database. dtester is parsing its output and checks that against expectations. Hawever, that has its own pitfalls, so in the end I'm almost about to change back to using libpq or implementing the bare minimum protocol (that might have its own merits within the twisted world, if implemented in the required async fashion).
Strangely, your log has escape codes in it, which I'm assuming makes the parsing choke. Is that something special to your installation? My psql never colors its outputs...
However, the quickest way forward probably is to filter out escape sequences. Turning off tty is not really an option, because dtester doesn't have a chance to capture all necessary events, in that mode.
Yes I can. Any queries you'd like me to run in there?
It looks like psql can connect, too. It's just the parsing of outputs which fails.
Regards Markus -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
