Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d5dBm-0001Uh-Ms for pgsql-hackers@arkaria.postgresql.org; Tue, 02 May 2017 19:10:23 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1d5dBm-0008R4-3R for pgsql-hackers@arkaria.postgresql.org; Tue, 02 May 2017 19:10:22 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d5dBl-0008Qj-Ci for pgsql-hackers@postgresql.org; Tue, 02 May 2017 19:10:21 +0000 Received: from mail.postgrespro.ru ([93.174.131.138]) by makus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d5dBd-0002jO-9l for pgsql-hackers@postgresql.org; Tue, 02 May 2017 19:10:20 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.postgrespro.ru (Postfix) with ESMTP id D3FE721C2582; Tue, 2 May 2017 22:10:10 +0300 (MSK) X-Virus-Scanned: Debian amavisd-new at postgrespro.ru Message-ID: <5908D991.4010009@postgrespro.ru> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1493752210; bh=ZZaW8koMPVrCzyym3BZdA0nbakLv24cDma2LJjrkeVA=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=VCmj80Oqvzfp7I/GskNFdeI7341vJLLSlySlWC6zSosEwd56S0Un+EWY1hp/BupyP Y8vrECzCpFcLMisb8wrIzbBkGbqcikr4icwtOGJb7vjlDouMpV5xlfJjNkaWNKSM5a 9S7zgm/Q+kP3BiFPBTo21npFFf0eP0cpx7R61084= Date: Tue, 02 May 2017 22:10:09 +0300 From: Konstantin Knizhnik User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Robert Haas CC: PostgreSQL Hackers Subject: Re: Bug in prepared statement cache invalidation? References: <25dba024-9850-1dc1-bb18-1a82a6dd2c33@postgrespro.ru> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org 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