Re: Async commands (like drop index)
От | Neil Conway |
---|---|
Тема | Re: Async commands (like drop index) |
Дата | |
Msg-id | 1179508841.6059.4.camel@goldbach обсуждение исходный текст |
Ответ на | Re: Async commands (like drop index) ("Jim C. Nasby" <decibel@decibel.org>) |
Ответы |
Re: Async commands (like drop index)
|
Список | pgsql-hackers |
On Fri, 2007-18-05 at 11:47 -0500, Jim C. Nasby wrote: > Assuming the concurrent psql stuff gets in, do you still see a use for > this? I think concurrent psql (and/or async libpq) is the right way to handle this sort of requirement. "DROP INDEX NOWAIT" is hacky, and would be difficult (impossible?) to implement in a reasonable manner: the backend is fundamentally single-threaded. Also, how does the client learn when the DROP INDEX actually finishes? The client would either need to poll the database, or we'd need to implement something like select() -- neither is a very appealing alternative. -1 from me: this functionality belongs on the client-side, where asynchronous operations are much easier to manage. -Neil
В списке pgsql-hackers по дате отправления: