| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Protect syscache from bloating with negative cache entries |
| Date: | 2017-12-17 03:25:48 |
| Message-ID: | CA+TgmoYtna_CP8GNsnEnNLBj-ZenmTp5Ygd-waMFM9KOjHOeGw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 13, 2017 at 11:20 PM, Kyotaro HORIGUCHI
<horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> Thank you very much for the valuable suggestions. I still would
> like to solve this problem and the
> a-counter-freely-running-in-minute(or several seconds)-resolution
> and pruning-too-long-unaccessed-entries-on-resizing seems to me
> to work enough for at least several known bloat cases. This still
> has a defect that this is not workable for a very quick
> bloating. I'll try thinking about the remaining issue.
I'm not sure we should regard very quick bloating as a problem in need
of solving. Doesn't that just mean we need the cache to be bigger, at
least temporarily?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-12-17 03:27:24 | Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager |
| Previous Message | Robert Haas | 2017-12-17 03:24:52 | Re: pg_(total_)relation_size and partitioned tables |