Re: cache invalidation for PL/pgsql functions
От | Tom Lane |
---|---|
Тема | Re: cache invalidation for PL/pgsql functions |
Дата | |
Msg-id | 37826.1430501385@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: cache invalidation for PL/pgsql functions (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: cache invalidation for PL/pgsql functions
|
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: > On Fri, May 1, 2015 at 9:09 AM, Marko Tiikkaja <marko@joh.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
В списке pgsql-hackers по дате отправления: