RE: Protect syscache from bloating with negative cache entries
| От | Tsunakawa, Takayuki |
|---|---|
| Тема | RE: Protect syscache from bloating with negative cache entries |
| Дата | |
| Msg-id | 0A3221C70F24FB45833433255569204D1FB98603@G01JPEXMBYT05 обсуждение исходный текст |
| Ответ на | Re: Protect syscache from bloating with negative cache entries (Bruce Momjian <bruce@momjian.us>) |
| Ответы |
Re: Protect syscache from bloating with negative cache entries
|
| Список | 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 по дате отправления: