From: | David Fetter <david(at)fetter(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:19:34 |
Message-ID: | 20070516151934.GD6858@fetter.org |
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?
I don't know about rules, but you can have a SRF return SETOF
REFCURSOR.
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter
Remember to vote!
Consider donating to PostgreSQL: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2007-05-16 15:23:52 | Re: Managing the community information stream |
Previous Message | Bruce Momjian | 2007-05-16 15:15:09 | Re: [HACKERS] row-level stats and last analyze time |