> 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
christian_oede...@gmx.de writes:
> our OR-Mapper accidently created an index that contained the same column
> twice, with the result that some SELECTs could not be executed anymore and
> gave the error message "btree index keys must be ordered by attribute".
> The problem can be reproduced with a
The following bug has been logged on the website:
Bug reference: 6351
Logged by: Christian Rudolph
Email address: christian_oede...@gmx.de
PostgreSQL version: 9.0.6
Operating system: openSUSE
Description:
Hi,
our OR-Mapper accidently created an index that contained t
