From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Async commands (like drop index) |
Date: | 2007-05-18 16:59:06 |
Message-ID: | 464DDB5A.6080507@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jim C. Nasby wrote:
> On Thu, May 17, 2007 at 12:30:45PM -0700, Joshua D. Drake wrote:
>> It seems that it may be useful to allow something like:
>>
>> DROP INDEX NOWAIT.
>>
>> The idea being, that the terminal will come back, the index will be
>> dropped in the background. If it doesn't drop, it rollback like normal
>> and logs.
>>
>> I bring this up now, as an idea. We can argue about it later... :)
>
> Assuming the concurrent psql stuff gets in, do you still see a use for
> this?
Yes. As cool as concurrent psql is... the majority of our users don't
use it. They use PgAdminIII.
This should be client agnostic imo.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-05-18 17:12:57 | Re: Async commands (like drop index) |
Previous Message | Jim C. Nasby | 2007-05-18 16:47:56 | Re: Async commands (like drop index) |