Re: [HACKERS] Re: type coersion (was OR clause status) - Mailing list pgsql-hackers

From Thomas G. Lockhart
Subject Re: [HACKERS] Re: type coersion (was OR clause status)
Date
Msg-id 35D10188.B58E861B@alumni.caltech.edu
Whole thread Raw
In response to Re: [HACKERS] Re: type coersion (was OR clause status)  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: [HACKERS] Re: type coersion (was OR clause status)
List pgsql-hackers
> I just tried adding the extra line, and initdb failed.  I wonder if we
> remove the oideqint4, if the parser will go for oideq?

If you want to try this as an experiment, so we can tell if this is a
possible solution, then great. I still have hopes that we can substitute
other parse trees and strategies within the index utilization routines,
so how about not committing things until we've tried a few options.

match_clause_to_indexkey() seems to be a starting point for what I want
to do. Will let you know how it goes...

                       - Tom

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Re: partial index
Next
From: adm@pu.go.id
Date:
Subject: HELP all women were raped during the May riots in Jakarta