From: | Gregory Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Testing concurrent psql |
Date: | 2007-05-16 13:43:36 |
Message-ID: | 87bqgkq3xz.fsf@stark.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-05-16 13:58:47 | Re: Managing the community information stream |
Previous Message | Andrew Dunstan | 2007-05-16 12:36:24 | Re: Not ready for 8.3 |