Re: Tricky bugs in concurrent index build

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
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 20:48:16
Message-ID: 11512.1156279696@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:
>> 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 :-(

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-08-22 21:01:58 Re: Where is hstore?
Previous Message Tom Lane 2006-08-22 20:30:15 Re: [HACKERS] Queries joining views