Re: Allowing extensions to supply operator-/function-specific info - Mailing list pgsql-hackers

From Paul Ramsey
Subject Re: Allowing extensions to supply operator-/function-specific info
Date
Msg-id 48F6F422-4F50-4DA6-A6A1-13C4AA1B9D27@cleverelephant.ca
Whole thread Raw
In response to Re: Allowing extensions to supply operator-/function-specific info  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Allowing extensions to supply operator-/function-specific info
List pgsql-hackers


On Mar 4, 2019, at 2:52 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

Paul Ramsey <pramsey@cleverelephant.ca> writes:
Gotcha, done and now have an implementation that passes all our regression tests.

Very cool!  So the next step, I guess, is to address your original problem
by cranking up the cost estimates for these functions --- have you tried
that yet?  In principle you should be able to do that and not have any
bad planning side-effects, but this is all pretty new territory so maybe
some problems remain to be ironed out.

BTW, if you'd like me to review the code you added for this, I'd be happy
to do so.  I've never looked at PostGIS' innards, but probably I can make
sense of the code for this despite that.

I would be ecstatic for a review, I’m sure I’ve left a million loose threads dangling.

P.




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Allowing extensions to supply operator-/function-specific info
Next
From: Thomas Munro
Date:
Subject: Re: Rare SSL failures on eelpout