Re: Concurrent psql API
От | Tom Lane |
---|---|
Тема | Re: Concurrent psql API |
Дата | |
Msg-id | 12610.1207712532@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Concurrent psql API (Shane Ambler <pgsql@Sheeky.Biz>) |
Ответы |
Re: Concurrent psql API
|
Список | pgsql-hackers |
Shane Ambler <pgsql@Sheeky.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
В списке pgsql-hackers по дате отправления: