[tgl@sss.pgh.pa.us: Re: [BUGS] ORDER BY bug in 8.1, WinXP]

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: pgsql-es-ayuda(at)postgresql(dot)org
Subject: [tgl@sss.pgh.pa.us: Re: [BUGS] ORDER BY bug in 8.1, WinXP]
Date: 2006-04-08 21:16:34
Message-ID: 20060408211634.GD14999@surnet.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-es-ayuda

Por favor verifiquen si pueden reproducir el problema en 8.1.3.

----- Forwarded message from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> -----

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
Date: Sat, 08 Apr 2006 15:13:36 -0400
Subject: Re: [BUGS] ORDER BY bug in 8.1, WinXP
X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.0.2

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

----- End forwarded message -----

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

Responses

Browse pgsql-es-ayuda by date

  From Date Subject
Next Message Paolo Lopez 2006-04-08 22:49:41 Re: Problema Order By en PosgreSQL 8.1
Previous Message Ruddy Vargas 2006-04-08 21:09:40 Crystal report y NPGSQL