From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Tricky bugs in concurrent index build |
Date: | 2006-08-22 21:04:05 |
Message-ID: | 44EB7145.70503@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
>>> It's fairly clear that we could support concurrent builds of nonunique
>>> indexes, but is that enough of a use-case to justify it?
>
>> I believe there would be. Most PostgreSQL users I run into, develop in
>> production, which means being able to add an index they forgot when
>> doing query analysis.
>
> True, unique constraints are usually something you should get right to
> start with. But it'll be annoying if we can do everything BUT that :-(
Agreed, but better then nothing :).
Sincerely,
Joshua D. Drake
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
--
=== 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/
From | Date | Subject | |
---|---|---|---|
Next Message | chrisnospam | 2006-08-22 21:13:10 | Re: [PATCHES] selecting large result sets in psql using |
Previous Message | Tom Lane | 2006-08-22 21:01:58 | Re: Where is hstore? |