Re: Index-only scan for btree_gist turns bpchar to char - Mailing list pgsql-hackers

From Alexander Lakhin
Subject Re: Index-only scan for btree_gist turns bpchar to char
Date
Msg-id 78443f7c-ee21-ced2-c807-693929254231@gmail.com
Whole thread Raw
In response to Re: Index-only scan for btree_gist turns bpchar to char  (Japin Li <japinli@hotmail.com>)
Responses Re: Index-only scan for btree_gist turns bpchar to char
List pgsql-hackers
Hello,
07.01.2022 09:26, Japin Li wrote:
> On Fri, 07 Jan 2022 at 03:21, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> In any case, if we do need same() to implement the identical
> behavior to bpchareq(), then the other solution isn't sufficient
> either.
>
> So in short, it seems like we ought to do some compatibility testing
> and see if this code misbehaves at all with an index created by the
> old code.  I don't particularly want to do that ... any volunteers?
>
> Thanks for your patch, it looks good to me.  I'm not sure how to test this.
I will test it tomorrow.

Best regards,
Alexander



pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: In-placre persistance change of a relation
Next
From: Julien Rouhaud
Date:
Subject: Re: ICU for global collation