RE: Protect syscache from bloating with negative cache entries - Mailing list pgsql-hackers

From Tsunakawa, Takayuki
Subject RE: Protect syscache from bloating with negative cache entries
Date
Msg-id 0A3221C70F24FB45833433255569204D1FB98603@G01JPEXMBYT05
Whole thread Raw
In response to Re: Protect syscache from bloating with negative cache entries  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Protect syscache from bloating with negative cache entries
List pgsql-hackers
From: Bruce Momjian [mailto:bruce@momjian.us]
> > That being said, having a "minimal size" threshold before starting with
> > the time-based eviction may be a good idea.
> 
> Agreed.  I see the minimal size as a way to keep the systems tables in
> cache, which we know we will need for the next query.

Isn't it the maximum size, not minimal size?  Maximum size allows to keep desired amount of system tables in memory as
wellas to control memory consumption to avoid out-of-memory errors (OS crash!).  I'm wondering why people want to take
adifferent approach to catcatch, which is unlike other PostgreSQL memory e.g. shared_buffers, temp_buffers, SLRU
buffers,work_mem, and other DBMSs.
 


Regards
Takayuki Tsunakawa





pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: grouping_planner refactoring
Next
From: "Tsunakawa, Takayuki"
Date:
Subject: RE: Libpq support to connect to standby server as priority