From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Marko Tiikkaja <marko(at)joh(dot)to>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: cache invalidation for PL/pgsql functions |
Date: | 2015-05-01 17:29:45 |
Message-ID: | 37826.1430501385@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Fri, May 1, 2015 at 9:09 AM, Marko Tiikkaja <marko(at)joh(dot)to> wrote:
>> We recently hit a similar case in our production environment. What was
>> annoying about it is that there didn't seem to be a way for the application
>> to fix the issue by itself, short of reconnecting; even DISCARD ALL doesn't
>> help. If we can't fix the underlying issue, can we at least provide a way
>> for apps to invalidate these caches themselves, for example in the form of a
>> DISCARD option?
> It's been discussed before and I am in favor of it.
I'm not. We should fix the problem not expect applications to band-aid
around it. This would be particularly ill-advised because there are so
many applications that just blindly do DISCARD ALL when changing contexts.
Having said that, I'm not sure that it's easy to get to a solution :-(
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2015-05-01 17:36:41 | Re: recovery_target_action = pause & hot_standby = off |
Previous Message | Stephen Frost | 2015-05-01 17:16:15 | Re: feature freeze and beta schedule |