agora inbox for pgsql-hackers@postgresql.org
help / color / mirror / Atom feedFrom: Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
To: Robert Haas <robertmhaas@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Bug in prepared statement cache invalidation?
Date: Tue, 02 May 2017 22:10:09 +0300
Message-ID: <5908D991.4010009@postgrespro.ru> (raw)
In-Reply-To: <CA+TgmoZ82H=rwDGWCgJ5yG7ebQ7WtcQbkfBf6ZTQYawPEFr0Kw@mail.gmail.com>
References: <25dba024-9850-1dc1-bb18-1a82a6dd2c33@postgrespro.ru>
<CA+TgmoZ__GT0C=8y_xgq68dHACWx==+Y1iCAnarfOMg6MBjf-g@mail.gmail.com>
<d9a10e11-aa3e-aef8-722a-edc0c5d8e0dc@postgrespro.ru>
<CA+TgmoZ82H=rwDGWCgJ5yG7ebQ7WtcQbkfBf6ZTQYawPEFr0Kw@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 05/02/2017 09:30 PM, Robert Haas wrote:
>> I am not sure how critical is this problem. Definitely it rarely happens,
>> but lack of normal workarounds (restart backend, recreate function?) seems
>> to be disappointing.
> The problem goes away if you reconnect. The problematic cache is only
> backend-lifetime.
>
Most of clients are not connected to the Postgres directly, them are using some kind of connection pooling.
It means that backends are never restarted. And it will be necessary to restart the whole service just because we do not have
dependency tracking mechanism for PL code. Even invalidation of all functions in case of DDL seems to be more acceptable solution.
--
Konstantin Knizhnik
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
view thread (9+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: k.knizhnik@postgrespro.ru, robertmhaas@gmail.com
Subject: Re: Bug in prepared statement cache invalidation?
In-Reply-To: <5908D991.4010009@postgrespro.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox