Re: Re: [PERFORM] performance drop when function argument is evaluated in WHERE clause

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gerardo Herzig <gherzig(at)fmed(dot)uba(dot)ar>
Cc: pgsql-performance(at)postgresql(dot)org, pgsql-sql <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Re: [PERFORM] performance drop when function argument is evaluated in WHERE clause
Date: 2014-04-08 17:41:37
Message-ID: 19249.1396978897@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance pgsql-sql

Gerardo Herzig <gherzig(at)fmed(dot)uba(dot)ar> writes:
> Tom, thanks (as allways) for your answer. This is a 9.1.12. I have to say, im not very happy about if-elif-else'ing at all.
> The "conditional filter" es a pretty common pattern in our functions, i would have to add (and maintain) a substantial amount of extra code.

In that case consider moving to 9.2 or later. I believe it'd handle
this scenario better.

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message uher dslij 2014-04-08 19:58:52 Re: Performance regressions in PG 9.3 vs PG 9.0
Previous Message Gerardo Herzig 2014-04-08 17:33:27 Re: [PERFORM] performance drop when function argument is evaluated in WHERE clause

Browse pgsql-sql by date

  From Date Subject
Next Message Andreas Joseph Krogh 2014-05-01 12:51:10 Optimize query for listing un-read messages
Previous Message Gerardo Herzig 2014-04-08 17:33:27 Re: [PERFORM] performance drop when function argument is evaluated in WHERE clause