| From: | Hannu Krosing <hannu(at)skype(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Tricky bugs in concurrent index build |
| Date: | 2006-08-23 08:05:41 |
| Message-ID: | 1156320341.2961.1.camel@localhost.localdomain |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Ühel kenal päeval, T, 2006-08-22 kell 16:48, kirjutas Tom Lane:
> "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 :-(
Maybe we could find a way to build a non-unique index first and then
convert it to a unique one later, in yet another pass ?
--
----------------
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2006-08-23 08:10:44 | Re: Tricky bugs in concurrent index build |
| Previous Message | Markus Schiltknecht | 2006-08-23 08:04:12 | Re: news server does not respond |