From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
---|---|
To: | Carlo Stonebanks <stonec(dot)register(at)sympatico(dot)ca> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: How do you control IMMUTABLE PG PROC results? |
Date: | 2010-11-05 05:58:52 |
Message-ID: | 20101105055852.GA3767@depesz.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Nov 04, 2010 at 08:24:14PM -0400, Carlo Stonebanks wrote:
> We have procs that would benefit from returning IMMUTABLE results.
> The procs are dependent on external tables that rarely change, but
> when they DO change, it would be great if we could expire the cache
> that the procs read from so that the procs are forced to re-evaluate
> the results.
>
> Is this possible?
>
> How do I know how many possible results are cached?
in addition to what Leif responded, please note that immutable functions
*do not* cache results.
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/gtalk: depesz(at)depesz(dot)com / aim:depeszhdl / skype:depesz_hdl / gg:6749007
From | Date | Subject | |
---|---|---|---|
Next Message | Henry C. | 2010-11-05 07:19:20 | Which is faster: md5() or hashtext()? |
Previous Message | Leif Biberg Kristensen | 2010-11-05 01:48:52 | Re: How do you control IMMUTABLE PG PROC results? |