Re: Feature request: Optimizer improvement

From: Jim Nasby <jim(at)nasby(dot)net>
To: Kevin Grittner <kgrittn(at)ymail(dot)com>
Cc: Joe Love <joe(at)primoweb(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Feature request: Optimizer improvement
Date: 2013-11-01 20:24:29
Message-ID: CB8882C4-C499-4203-B3E2-F6D1B8B915B5@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Oct 31, 2013, at 2:57 PM, Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:
> Joe Love <joe(at)primoweb(dot)com> wrote:
>
>> In postgres 9.2 I have a function that is relatively expensive.
>
> What did you specify in the COST clause on the CREATE FUNCTION
> statement?

Should that really matter in this case? ISTM we should always handle LIMIT before moving on to the SELECT clause…?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-11-01 20:30:19 Re: Handle LIMIT/OFFSET before select clause (was: Feature request: optimizer improvement)
Previous Message Jim Nasby 2013-11-01 20:21:43 Re: [BUGS] BUG #8573: int4range memory consumption