Re: BUG #6351: ERROR: btree index keys must be ordered by attribute

From: "Christian Rudolph" <Christian_Oederan(at)gmx(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6351: ERROR: btree index keys must be ordered by attribute
Date: 2011-12-23 12:30:58
Message-ID: 20111223123058.7810@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> But now that we allow it it'd be nice if it actually worked :-(.
> Looking into the archives I see that we were mainly thinking about
> the possibility of exclusion constraints naming the same column
> more than once, which may explain why nobody tried using such an
> index for queries. I'll see about fixing this in HEAD, although
> my initial guess is that it will be too invasive to back-patch.

I didn't recognized the exclusion constraint feature before. But it looks interesting.

Thank you for your effort.
Christian
--
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!
Jetzt informieren: http://www.gmx.net/de/go/freephone

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2011-12-23 17:05:58 Re: BUG #5578: postrgesql database crash
Previous Message stuartb81 2011-12-23 10:28:52 Re: libber library not found on RC1