Re: [HACKERS] Protect syscache from bloating with negative cache entries
От | Robert Haas |
---|---|
Тема | Re: [HACKERS] Protect syscache from bloating with negative cache entries |
Дата | |
Msg-id | CA+TgmoaMPbN5vvH33zLK7MR+PiCYWPvTHmSSrDab4vurLOXS-Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Protect syscache from bloating with negative cache entries (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [HACKERS] Protect syscache from bloating with negative cache entries
|
Список | pgsql-hackers |
On Tue, Dec 20, 2016 at 10:09 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Craig Ringer <craig@2ndquadrant.com> writes: >> On 20 December 2016 at 21:59, Robert Haas <robertmhaas@gmail.com> wrote: >>> We could implement this by having >>> some process, like the background writer, >>> SendProcSignal(PROCSIG_HOUSEKEEPING) to every process in the system >>> every 10 minutes or so. > >> ... on a rolling basis. > > I don't understand why we'd make that a system-wide behavior at all, > rather than expecting each process to manage its own cache. Individual backends don't have a really great way to do time-based stuff, do they? I mean, yes, there is enable_timeout() and friends, but I think that requires quite a bit of bookkeeping. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: