Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cSCKb-0005Dw-Et for pgsql-hackers@arkaria.postgresql.org; Sat, 14 Jan 2017 00:36:29 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cSCKa-000771-Rc for pgsql-hackers@arkaria.postgresql.org; Sat, 14 Jan 2017 00:36:28 +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 1cSCKZ-000764-19 for pgsql-hackers@postgresql.org; Sat, 14 Jan 2017 00:36:27 +0000 Received: from mail-wm0-x231.google.com ([2a00:1450:400c:c09::231]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cSCKT-0003oO-Vz for pgsql-hackers@postgresql.org; Sat, 14 Jan 2017 00:36:26 +0000 Received: by mail-wm0-x231.google.com with SMTP id c85so86424081wmi.1 for ; Fri, 13 Jan 2017 16:36:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=e0HVLxYoqBrpd85EHXQ5qedOQWmmIWB+l/deQGNjMDY=; b=QOI0/TN9k8MVVECjeAuhM4cleHsu2d8fAWz9qQwgJfWPTdtRmol+8j44Ti4+nph4PY sTAXL9+zeRIhk1evhKB8DCpXemnEanmEQVheuxGXcI7bmcRdfBcr+FQWNw6IfUzb1ZEm VNiQTK2dtkE4EYSWmkttA1u16cSvW5cgPsPRTZAXVeyS9vP3ODl25hVwe1K/4zds3rfM lSJHqXuaBTuSdh6JHlB5AsNnQHYE5EKFcirJ56HkHA3QziKXkOWSOVgP37CEmBG7Rlnn AdQL12tDhbmFqRnaKRuqIUToQxNrD1bkKtItAq2YZ23WeI4J7Zg/LjgSEwty4yWPyFPb xXig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=e0HVLxYoqBrpd85EHXQ5qedOQWmmIWB+l/deQGNjMDY=; b=VLZRJMEKqm8qYKzEBuhW/rkeEMSmLvQ/dbfgYdVt8m3u8rcXW6e+vccsBx43YwSg95 BsYSUgb5Q24l3z1jJy2ZhiYt+4zf0wBarayPT/px4K+9OyJnz8XJhuaTfVQRK/ELY5fs EkvUXiB4ITu8qtf4M56IfHBHu7n3v7637xXsLaDcaVRej4BYkY5em4QzR+oW+Oz4bKOz iikkVo/D4GZNm6d5AtGb+BTyd5QlNz/jlcOQiOa/LT0Cd/kiGNquKJu6Rq8jRFOARtBB xHKo2BmhmnsrdpyZ8HdCUmBrnFdqDeYpxpZdRdEIqGZQrkcOKhTfzeTSiBhyGff5v10s Pzhw== X-Gm-Message-State: AIkVDXKpBVL+jCmTn0500KdceRpbxaJte/D6/OP2MbmW0FzVOGr6RZ1ubdJH3OAHi59AVYi4kVa4hY/iJMkkcZpWm6R6BhTafu7Rgduc0bljrP4oTOZmJL/ZF8AjGpy70xK77Rr1ox9RnvZOgI6y3kPGXXSPG5C2NDsXpQlXkMvEWV7zcJghk1vhFRaNlHbJkGiBR0TMVpfn X-Received: by 10.28.225.215 with SMTP id y206mr3971455wmg.138.1484354179840; Fri, 13 Jan 2017 16:36:19 -0800 (PST) Received: from [10.137.2.17] (ip-89-177-46-65.net.upcbroadband.cz. [89.177.46.65]) by smtp.gmail.com with ESMTPSA id c132sm2503502wme.21.2017.01.13.16.36.18 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Jan 2017 16:36:19 -0800 (PST) Subject: Re: Protect syscache from bloating with negative cache entries To: pgsql-hackers@postgresql.org References: <30868.1482246558@sss.pgh.pa.us> <23492.1482264621@sss.pgh.pa.us> <4647.1484315911@sss.pgh.pa.us> <30626.1484348321@sss.pgh.pa.us> <20170113230631.uuq3ioq2qlyjio5q@alap3.anarazel.de> From: Tomas Vondra Message-ID: Date: Sat, 14 Jan 2017 01:36:18 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20170113230631.uuq3ioq2qlyjio5q@alap3.anarazel.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) 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 01/14/2017 12:06 AM, Andres Freund wrote: > Hi, > > > On 2017-01-13 17:58:41 -0500, Tom Lane wrote: >> But, again, the catcache isn't the only source of per-process bloat >> and I'm not even sure it's the main one. A more holistic approach >> might be called for. > > It'd be helpful if we'd find a way to make it easy to get statistics > about the size of various caches in production systems. Right now > that's kinda hard, resulting in us having to make a lot of > guesses... > What about a simple C extension, that could inspect those caches? Assuming it could be loaded into a single backend, that should be relatively acceptable way (compared to loading it to all backends using shared_preload_libraries). -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers