Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cJM2g-0007DE-AG for pgsql-hackers@arkaria.postgresql.org; Tue, 20 Dec 2016 15:09:26 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cJM2f-0004Cw-Ol for pgsql-hackers@arkaria.postgresql.org; Tue, 20 Dec 2016 15:09:25 +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 1cJM2f-0004A2-3B for pgsql-hackers@postgresql.org; Tue, 20 Dec 2016 15:09:25 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cJM2b-0004bo-SS for pgsql-hackers@postgresql.org; Tue, 20 Dec 2016 15:09:23 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id uBKF9Ir4030869; Tue, 20 Dec 2016 10:09:18 -0500 From: Tom Lane To: Craig Ringer cc: Robert Haas , Kyotaro HORIGUCHI , "pgsql-hackers@postgresql.org" Subject: Re: Protect syscache from bloating with negative cache entries In-reply-to: References: <20161219.201505.11562604.horiguchi.kyotaro@lab.ntt.co.jp> Comments: In-reply-to Craig Ringer message dated "Tue, 20 Dec 2016 22:47:17 +0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <30867.1482246558.1@sss.pgh.pa.us> Date: Tue, 20 Dec 2016 10:09:18 -0500 Message-ID: <30868.1482246558@sss.pgh.pa.us> X-Pg-Spam-Score: -5.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 Craig Ringer writes: > On 20 December 2016 at 21:59, Robert Haas wrote: >> We could implement this by having >> some process, like the background writer, >> SendProcSignal(PROCSIG_HOUSEKEEPING) to every process in the system >> every 10 minutes or so. > ... on a rolling basis. I don't understand why we'd make that a system-wide behavior at all, rather than expecting each process to manage its own cache. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers