| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | sandeep satpal <sandeep(at)it(dot)iitb(dot)ac(dot)in> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Issue is changing _bt_compare function and |
| Date: | 2005-10-08 17:16:34 |
| Message-ID: | 20051008171634.GA5648@surnet.cl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
sandeep satpal wrote:
> The _bt_compare function in "nbtree.c" file calls "FunctionCall2" and it
> passes two arguments , one is the scankey which we want to search on and
> other key is on current b-tree node.
>
> My problem is I want to pass three parameter and the third argument will
> be used for taking decision during comparision that whether I want
> case-sensitive comparision or case-insensitive.
This is certainly the wrong layer to be making these changes. Have you
considered using the citext type? If it doesn't suit you, you could use
it as a foundation for developing your own.
What you need to change is the function stored in the scankey.
--
Alvaro Herrera http://www.amazon.com/gp/registry/DXLWNGRJD34
Voy a acabar con todos los humanos / con los humanos yo acabaré
voy a acabar con todos / con todos los humanos acabaré (Bender)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-10-08 18:10:00 | Re: avoid pulling up subquerys that contain volatile functions? |
| Previous Message | Jaime Casanova | 2005-10-08 15:51:14 | avoid pulling up subquerys that contain volatile functions? |