Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cVRCJ-00057T-R4 for pgsql-hackers@arkaria.postgresql.org; Sun, 22 Jan 2017 23:05:19 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cVRCJ-0000Uq-E6 for pgsql-hackers@arkaria.postgresql.org; Sun, 22 Jan 2017 23:05:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cVRAu-0007Ji-Ag for pgsql-hackers@postgresql.org; Sun, 22 Jan 2017 23:03:52 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cVRAr-0000jv-2Y for pgsql-hackers@postgresql.org; Sun, 22 Jan 2017 23:03:51 +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 v0MN3fWS026169; Sun, 22 Jan 2017 18:03:41 -0500 From: Tom Lane To: Jim Nasby cc: Kyotaro HORIGUCHI , robertmhaas@gmail.com, craig@2ndquadrant.com, pgsql-hackers@postgresql.org Subject: Re: Protect syscache from bloating with negative cache entries In-reply-to: <683113d7-c7a7-1a0f-da7c-b197b08a6440@BlueTreble.com> References: <23492.1482264621@sss.pgh.pa.us> <20161221.102109.51106943.horiguchi.kyotaro@lab.ntt.co.jp> <20161226.173147.73783918.horiguchi.kyotaro@lab.ntt.co.jp> <19334.1485053684@sss.pgh.pa.us> <276bcca0-9bfd-e60f-243d-baf081b41946@BlueTreble.com> <683113d7-c7a7-1a0f-da7c-b197b08a6440@BlueTreble.com> Comments: In-reply-to Jim Nasby message dated "Sun, 22 Jan 2017 16:51:53 -0600" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <26167.1485126221.1@sss.pgh.pa.us> Date: Sun, 22 Jan 2017 18:03:41 -0500 Message-ID: <26168.1485126221@sss.pgh.pa.us> X-Pg-Spam-Score: -5.1 (-----) 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 Jim Nasby writes: >> Ahh, I hadn't considered that. So one idea would be to only track >> negative entries on caches where we know they're actually useful. That >> might make the performance hit of some of the other ideas more >> tolerable. Presumably you're much less likely to pollute the namespace >> cache than some of the others. > Ok, after reading the code I see I only partly understood what you were > saying. In any case, it might still be useful to do some testing with > CATCACHE_STATS defined to see if there's caches that don't accumulate a > lot of negative entries. There definitely are, according to my testing, but by the same token it's not clear that a shutoff check would save anything. 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