Re: Protect syscache from bloating with negative cache entries

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Protect syscache from bloating with negative cache entries
Date: 2017-01-14 00:36:18
Message-ID: c205fe42-1a02-92f4-5df3-fd469b95b89b@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2017-01-14 04:36:05 Re: [COMMITTERS] pgsql: Fix a bug in how we generate partition constraints.
Previous Message Peter Geoghegan 2017-01-14 00:24:48 Re: Packages: Again