Re: Doing better at HINTing an appropriate column within errorMissingColumn()
От | Michael Paquier |
---|---|
Тема | Re: Doing better at HINTing an appropriate column within errorMissingColumn() |
Дата | |
Msg-id | CAB7nPqTyPRNN8HiEmdMeCEk7tEDvxX6VEptGgU11udYd5MqrsQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Doing better at HINTing an appropriate column within errorMissingColumn() (Peter Geoghegan <pg@heroku.com>) |
Список | pgsql-hackers |
<div dir="ltr"><br /><div class="gmail_extra"><br /><div class="gmail_quote">On Tue, Dec 23, 2014 at 9:43 AM, Peter Geoghegan<span dir="ltr"><<a href="mailto:pg@heroku.com" target="_blank">pg@heroku.com</a>></span> wrote:<br /><blockquoteclass="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">OnMon, Dec 22, 2014 at 4:34 PM, Peter Geoghegan <<a href="mailto:pg@heroku.com">pg@heroku.com</a>> wrote:<br/> > To put it another way, creating a separate object obfuscates<br /> > scanRTEForColumn(), since it's theonly client of<br /> > updateFuzzyAttrMatchState().<br /><br /><br /></span>Excuse me. I mean *not* creating a separateobject -- having a unified<br /> state representation for the entire range-table, rather than having<br /> one perRTE and merging them one by one into an overall/final range<br /> table object.<span class="HOEnZb"></span><br /></blockquote></div><brclear="all" /></div><div class="gmail_extra">Patch moved to CF 2015-02.<br /></div><div class="gmail_extra">--<br /><div class="gmail_signature">Michael<br /></div></div></div>
В списке pgsql-hackers по дате отправления: