Ühel kenal päeval, T, 2006-08-22 kell 16:48, kirjutas Tom Lane: > "Joshua D. Drake" <[EMAIL PROTECTED]> 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 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
