Re: [HACKERS] Help: fmgr_info: function 0: cache lookup failed
От | Bruce Momjian |
---|---|
Тема | Re: [HACKERS] Help: fmgr_info: function 0: cache lookup failed |
Дата | |
Msg-id | 199907072132.RAA11182@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] Help: fmgr_info: function 0: cache lookup failed (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [HACKERS] Help: fmgr_info: function 0: cache lookup failed
|
Список | pgsql-hackers |
Tom, was this dealth with? > "D'Arcy" "J.M." Cain <darcy@druid.net> writes: > >>>> I tried just setting oprcanhash to true but that didn't do it. Can > >>>> you suggest what fields I need to look at in pg_operator? > >> > >> oprrest and oprjoin > > > OK, I did this and it worked. I'll go work on the documentation now. > > OK, I see the problem: btreesel() and friends blithely assume that the > operator used in an index will have a selectivity function (oprrest). > > I can see two reasonable fixes: > * Default to an 0.5 estimate if no oprrest link (this is what the > optimizer does for operators that have no oprrest). > * Generate an error message along the lines of "index operators must > have a restriction selectivity estimator", if we think that they > really really oughta. > > I'm not sure which way to jump. The former would be more friendly for > people just starting to develop index support for a new data type ... > but then they might never realize that lack of an estimator is hurting > performance for them. Comments? > > regards, tom lane > > -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
В списке pgsql-hackers по дате отправления: