| From: | Shane Ambler <pgsql(at)Sheeky(dot)Biz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Concurrent psql API |
| Date: | 2008-04-09 02:42:20 |
| Message-ID: | 47FC2D0C.5090405@Sheeky.Biz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2008-04-09 02:47:17 | Re: [PATCHES] libpq type system 0.9a |
| Previous Message | Shane Ambler | 2008-04-09 02:36:40 | Re: Concurrent psql API |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2008-04-09 02:47:17 | Re: [PATCHES] libpq type system 0.9a |
| Previous Message | Shane Ambler | 2008-04-09 02:36:40 | Re: Concurrent psql API |