Re: Concurrent psql API

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Shane Ambler <pgsql(at)Sheeky(dot)Biz>
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 03:42:12
Message-ID: 12610.1207712532@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

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?

This is a pretty fundamental issue, and insisting that you want that
behavior will make both the user's mental model and the implementation
a whole lot more complex. I'm not going to accept unsupported arguments
that it might be a nice thing to have.

> 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?

Right.

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

Sure, some status-inquiry commands could be added without fundamentally
affecting anything.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Chernow 2008-04-09 03:46:25 Re: [PATCHES] libpq type system 0.9a
Previous Message Andrew Chernow 2008-04-09 03:38:14 Re: [PATCHES] libpq type system 0.9a

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Chernow 2008-04-09 03:46:25 Re: [PATCHES] libpq type system 0.9a
Previous Message Andrew Chernow 2008-04-09 03:38:14 Re: [PATCHES] libpq type system 0.9a