From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
Cc: robertmhaas@gmail.com
Cc: craig@2ndquadrant.com
Cc: pgsql-hackers@postgresql.org
Subject: Re: Protect syscache from bloating with negative cache entries
Date: Sun, 22 Jan 2017 16:41:18 -0600
Message-ID: <276bcca0-9bfd-e60f-243d-baf081b41946@BlueTreble.com> (raw)
In-Reply-To: <19334.1485053684@sss.pgh.pa.us>
References: <CA+TgmoaMPbN5vvH33zLK7MR+PiCYWPvTHmSSrDab4vurLOXS-Q@mail.gmail.com>
<23492.1482264621@sss.pgh.pa.us>
<20161221.102109.51106943.horiguchi.kyotaro@lab.ntt.co.jp>
<20161226.173147.73783918.horiguchi.kyotaro@lab.ntt.co.jp>
<ecd7ba88-0484-54be-5b8a-c48848438aea@BlueTreble.com>
<19334.1485053684@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 1/21/17 8:54 PM, Tom Lane wrote:
> Jim Nasby <Jim.Nasby@bluetreble.com> writes:
>> The other (possibly naive) question I have is how useful negative
>> entries really are? Will Postgres regularly incur negative lookups, or
>> will these only happen due to user activity?
> It varies depending on the particular syscache, but in at least some
> of them, negative cache entries are critical for performance.
> See for example RelnameGetRelid(), which basically does a RELNAMENSP
> cache lookup for each schema down the search path until it finds a
> match.
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.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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: Jim.Nasby@BlueTreble.com, tgl@sss.pgh.pa.us, horiguchi.kyotaro@lab.ntt.co.jp, robertmhaas@gmail.com, craig@2ndquadrant.com
Subject: Re: Protect syscache from bloating with negative cache entries
In-Reply-To: <276bcca0-9bfd-e60f-243d-baf081b41946@BlueTreble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox