Re: BUG #3723: dropping an index that doesn't refer to table's columns

Поиск
Список
Период
Сортировка
От Sam Mason
Тема Re: BUG #3723: dropping an index that doesn't refer to table's columns
Дата
Msg-id 20071106152556.GI1955@frubble.xen.chris-lamb.co.uk
обсуждение исходный текст
Ответ на Re: BUG #3723: dropping an index that doesn't refer to table's columns  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
Дерево обсуждения 
On Tue, Nov 06, 2007 at 10:00:43AM -0500, Tom Lane wrote:
> Heikki Linnakangas <heikki@enterprisedb.com> writes:
> > Not sure that's enough of a use case to justify not banning it...
>
> Yeah, it probably is.

It's reasonably easy to do this instead:

  CREATE TABLE foo (
    one INTEGER NOT NULL UNIQUE CHECK (one = 1)
  );

The bug (for me) was that it's possible to get the database into an
inconsisant state, with no warning or obvious way to back out.


  Sam

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #3723: dropping an index that doesn't refer to table's columns
Следующее
От: "Mason Hale"
Дата:
Сообщение: BUG #3724: Duplicate values added to table despite unique index