| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Kevin Viraud <kevin(dot)viraud(at)rocket-internet(dot)de>, 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Weird CASE WHEN behaviour causing query to be suddenly very slow |
| Date: | 2015-04-07 23:38:38 |
| Message-ID: | 55246A7E.9060800@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 3/31/15 10:58 AM, Kevin Viraud wrote:
> Touche ! Thanks a lot.
>
> Looking more at the data yes it goes very often to ELSE Clause. And
> therefore reaching the MAX_CACHED_RES.
>
> In there anyway to increase that value ?
Sure, change it and re-compile. But be aware that increasing it will
probably increase the cost of some other stuff, so it's a tradeoff.
If this is that complex though you very likely would do better in
plperl, especially if you could pre-compile the RE's. AFAIK there's no
way to do that in Postgres, though it might be interesting to add that
ability.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Qingqing Zhou | 2015-04-07 23:50:53 | Re: Weird CASE WHEN behaviour causing query to be suddenly very slow |
| Previous Message | Jim Nasby | 2015-04-07 23:30:43 | Re: views much slower in 9.3 than 8.4 |