I only did some cursory tests, but the patch (applied to Macport's beta2 distribution) seems to be working on my dev box (OSX / Snow Leopard).
I'll report back if I run into oddities further down the road.
Thanks a lot!
>From: Jeff Davis <pgsql(at)j-davis(dot)com>
>Cc: Denis de Bernardy <ddebernardy(at)yahoo(dot)com>; Teodor Sigaev <teodor(at)sigaev(dot)ru>; pgsql-bugs(at)postgresql(dot)org
>Sent: Sunday, June 19, 2011 7:23 PM
>Subject: Re: PG regression with row comparison when btree_gist is enabled (BUG)
>On Sat, 2011-06-18 at 13:20 -0700, Jeff Davis wrote:
>> Interesting problem... the bug is in get_op_btree_interpretation() which
>> has code like this:
>> * If we can't find any opfamily containing the op, perhaps it is a
>> * operator. See if it has a negator that is in an
>> op_negated = false;
>> if (catlist->n_members == 0)
>> However, that's a bogus test, because btree_gist puts <> into an
>> opfamily. Thus, catlist->n_members == 1 even though we really do need to
>> look for the negator. Really, we need to unconditionally search for the
>> operator as well as unconditionally searching for the negator.
> Jeff Davis
In response to
pgsql-bugs by date
|Next:||From: David Hernández||Date: 2011-06-20 09:35:04|
|Subject: ¿Está el servidor en ejecución localmente y acept?==?ISO-8859-1?Q?ando conexiones en el socket de dominio Unix <</tmp/.s.PGSQL?==?ISO-8859-1?Q?.5432>>?|
|Previous:||From: Craig Ringer||Date: 2011-06-20 07:16:47|
|Subject: Re: BUG #6064: != NULL, <> NULL do not work [sec=UNCLASSIFIED]|
pgsql-testers by date
|Next:||From: Peder O. Klingenberg||Date: 2011-06-23 12:37:01|
|Subject: Documentation nitpick|
|Previous:||From: Jeff Davis||Date: 2011-06-19 17:23:10|
|Subject: Re: PG regression with row comparison when btree_gist is enabled