Re: Concurrent psql API - Mailing list pgsql-hackers

From Shane Ambler
Subject Re: Concurrent psql API
Date
Msg-id 47FC2D0C.5090405@Sheeky.Biz
Whole thread Raw
In response to Re: Concurrent psql API  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Concurrent psql API  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:

> \join connID
> 
>     Switch to connection connID.  If it is busy, wait for
>     command completion and print the result before offering
>     a new command prompt.

When switching to a conn we also need a non-destructive way out if it is 
busy.


> \join    (or \join - as per Alvaro)
> 
>     Wait for any currently busy connection's command to finish,
>     then \join to it.  Error if there is no busy connection.
> 

So what you suggest is that if you have 10 busy conns running \join will 
send you to the next conn to return a result?

On that - listing the current conns could be useful to have some status 
info with the list to indicate idle or running what command.



-- 

Shane Ambler
pgSQL (at) Sheeky (dot) Biz

Get Sheeky @ http://Sheeky.Biz


pgsql-hackers by date:

Previous
From: Shane Ambler
Date:
Subject: Re: Concurrent psql API
Next
From: "Merlin Moncure"
Date:
Subject: Re: [PATCHES] libpq type system 0.9a