From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: ORDER BY bug in 8.1, WinXP |
Date: | 2006-04-08 19:13:36 |
Message-ID: | 25536.1144523616@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-es-ayuda |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> I observe that Paolo was using 8.1.0 and Oswaldo 8.1.1.
This appears to be the same bug already fixed in 8.1.3:
2006-01-29 12:27 tgl
* src/: backend/optimizer/path/indxpath.c,
backend/optimizer/path/pathkeys.c, include/optimizer/paths.h
(REL8_1_STABLE): Fix code that checks to see if an index can be
considered to match the query's requested sort order. It was
assuming that build_index_pathkeys always generates a pathkey per
index column, which was not true if implied equality deduction had
determined that two index columns were effectively equated to each
other. Simplest fix seems to be to install an option that causes
build_index_pathkeys to support this behavior as well as the
original one. Per report from Brian Hirt.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Paolo Lopez | 2006-04-08 22:49:41 | Re: Problema Order By en PosgreSQL 8.1 |
Previous Message | Alvaro Herrera | 2006-04-08 17:23:35 | ORDER BY bug in 8.1, WinXP |
From | Date | Subject | |
---|---|---|---|
Next Message | Ruddy Vargas | 2006-04-08 21:09:40 | Crystal report y NPGSQL |
Previous Message | Alvaro Herrera | 2006-04-08 17:23:35 | ORDER BY bug in 8.1, WinXP |