Testing concurrent psql - Mailing list pgsql-hackers

From Gregory Stark
Subject Testing concurrent psql
Date
Msg-id 87bqgkq3xz.fsf@stark.xeocode.com
Whole thread Raw
Responses Re: Testing concurrent psql  (David Fetter <david@fetter.org>)
Re: Testing concurrent psql  ("Jim C. Nasby" <decibel@decibel.org>)
List pgsql-hackers
I'm looking for corner cases where the concurrent psql patch doesn't handle
things properly. I'm wondering about multiple result sets but I can't think of
any cases where I can test them.

If you submit multiple commands at the psql prompt then psql seems to stop at
the first semicolon and send the query separately. The only way to send
multiple queries together seems to be with -c and I don't think we have any
intention to support asynchronous queries via that route. Regular queries
still work fine via this route.

I seem to recall there was a way to construct scenarios that returned multiple
result sets via rules but I don't know how to arrange that. Anyone remember?

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Not ready for 8.3
Next
From: Alvaro Herrera
Date:
Subject: Re: Managing the community information stream