From: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
---|---|
To: | Gregory Stark <gsstark(at)mit(dot)edu> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Testing concurrent psql |
Date: | 2007-05-16 15:39:03 |
Message-ID: | 20070516153903.GJ14548@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, May 16, 2007 at 09:43:36AM -0400, Gregory Stark wrote:
>
> 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?
An ALSO SELECT rule?
--
Jim Nasby decibel(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2007-05-16 15:40:17 | Re: Integer datetimes |
Previous Message | Jim C. Nasby | 2007-05-16 15:36:42 | Re: 8.3 pending patch queue |