Re: Concurrent psql API

Tom Lane wrote:
> Shane Ambler <pgsql(at)Sheeky(dot)Biz> writes:
>> When switching to a conn we also need a non-destructive way out if it is
>> busy.
>
> Uh, why? Why would you switch to a connection at all, if you didn't
> want its result?

What if you switch to the wrong connection and it hasn't finished. Do
you then have to wait until you get the results before you can issue
another command? Or will we be able to type commands while we wait for
results?

I am thinking as currently happens - you can't type a command as you are
waiting for a result. So if the connection you switch to is busy but you
want to go to another connection then how do you?

This may tie into an 'auto new connection'. You start psql enter a
command that will take a while then think of something else you can do
as you wait. Do you open another shell and start psql again, or send the
working task to the background and enter another command in a new
connection?

Think jobs in a shell, you can suspend a long running process then send
it to the background to work and go on with something else.

So I am thinking something like C-z that will allow you to switch out of
a task that is waiting for results without having to stop it with C-c.

--

Shane Ambler
pgSQL (at) Sheeky (dot) Biz

Get Sheeky @ http://Sheeky.Biz