Re: Testing with concurrent sessions - Mailing list pgsql-hackers

From Markus Wanner
Subject Re: Testing with concurrent sessions
Date
Msg-id 4B50B1F3.2000408@bluegap.ch
Whole thread Raw
In response to Re: Testing with concurrent sessions  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Testing with concurrent sessions  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Re: Testing with concurrent sessions  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
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
yourinstallation? 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


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Hot Standby and handling max_standby_delay
Next
From: Heikki Linnakangas
Date:
Subject: Re: About "Our CLUSTER implementation is pessimal" patch