Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
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.
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!		
Jetzt informieren:

In response to

pgsql-bugs by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group