Re: Index-only scan for btree_gist turns bpchar to char

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Japin Li <japinli(at)hotmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Index-only scan for btree_gist turns bpchar to char
Date: 2022-01-07 09:00:30
Message-ID: 78443f7c-ee21-ced2-c807-693929254231@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello,
07.01.2022 09:26, Japin Li wrote:
> On Fri, 07 Jan 2022 at 03:21, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2022-01-07 09:03:29 Re: ICU for global collation
Previous Message Kyotaro Horiguchi 2022-01-07 08:29:55 Re: In-placre persistance change of a relation