Re: Testing concurrent psql

"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> Greg Stark <gsstark(at)mit(dot)edu> writes:
>> "Jim C. Nasby" <decibel(at)decibel(dot)org> writes:
>>> On Wed, May 16, 2007 at 09:43:36AM -0400, Gregory Stark wrote:
>>>> 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?
>
>> It gives you an error.
>
> Not if you do it correctly.

Ah, I was trying to do a ON SELECT DO ALSO SELECT

I now get this using the patched version, I can't see this divergence as a bad
thing though:

postgres=# insert into foo values(42);
?column?
----------
1
(1 row)

?column?
----------
2
(1 row)

?column?
----------
3
(1 row)

INSERT 0 1

It seems to work fine asynchronously too as libpq doesn't report the response
as having been received until all three result sets are there anyways, so it
doesn't require any special handling.

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