Request a Demo
Home   >   mailing lists

Re: Doing better at HINTing an appropriate column within errorMissingColumn() - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Doing better at HINTing an appropriate column within errorMissingColumn()
Date
Msg-id CAB7nPqTyPRNN8HiEmdMeCEk7tEDvxX6VEptGgU11udYd5MqrsQ@mail.gmail.com
Whole thread Raw
In response to Re: Doing better at HINTing an appropriate column within errorMissingColumn()  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
Tree view


On Tue, Dec 23, 2014 at 9:43 AM, Peter Geoghegan <pg@heroku.com> wrote:
On Mon, Dec 22, 2014 at 4:34 PM, Peter Geoghegan <pg@heroku.com> wrote:
> To put it another way, creating a separate object obfuscates
> scanRTEForColumn(), since it's the only client of
> updateFuzzyAttrMatchState().


Excuse me. I mean *not* creating a separate object -- having a unified
state representation for the entire range-table, rather than having
one per RTE and merging them one by one into an overall/final range
table object.

Patch moved to CF 2015-02.
--
Michael

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: ctidscan as an example of custom-scan (Re: [v9.5] Custom Plan API)
Next
From: Michael Paquier
Date:
Subject: Re: Logical Replication Helpers WIP for discussion