| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Async commands (like drop index) |
| Date: | 2007-05-18 17:12:57 |
| Message-ID: | 29719.1179508377@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> Yes. As cool as concurrent psql is... the majority of our users don't
> use it. They use PgAdminIII.
So? IIRC pgAdmin can open up multiple connections already.
> This should be client agnostic imo.
Just to be perfectly clear: the odds of making a single backend support
concurrent operations in the foreseeable future are indistinguishable
from zero. So if you want a behavior like this, it's going to have to
happen by making the client open up multiple connections. I see no
reason at all to tie such a feature to index-dropping in particular.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2007-05-18 17:15:47 | Re: Async commands (like drop index) |
| Previous Message | Joshua D. Drake | 2007-05-18 16:59:06 | Re: Async commands (like drop index) |