Re: json api WIP patch - Mailing list pgsql-hackers

From Tom Lane
Subject Re: json api WIP patch
Date
Msg-id 25624.1359759826@sss.pgh.pa.us
Whole thread Raw
In response to Re: json api WIP patch  (Daniel Farina <daniel@heroku.com>)
Responses Re: json api WIP patch  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Daniel Farina <daniel@heroku.com> writes:
> On Fri, Feb 1, 2013 at 2:08 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>> I think it's smarter for us to ship functions, and let users wrap them
>> in operators if they so choose.  It's not difficult for people who

> The problem being: even though pg_operator resolves to functions in
> pg_proc, they have distinct identities as far as the planner is
> concerned w.r.t selectivity estimation and index selection.

Yeah, this is surely not a workable policy unless we first move all
those planner smarts to apply to functions not operators.  And rewrite
all the index AM APIs to use functions not operators, too.  Now this is
something that's been a wish-list item right along, but actually doing
it has always looked like a great deal of work for rather small reward.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: proposal - assign result of query to psql variable
Next
From: Tom Lane
Date:
Subject: Re: autovacuum not prioritising for-wraparound tables