| From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
|---|---|
| To: | Kasahara Tatsuhito <kasahara(dot)tatsuhito(at)gmail(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: Creating a function for exposing memory usage of backend process |
| Date: | 2020-06-26 06:42:31 |
| Message-ID: | CALj2ACUOT0oJs3z7Za4T8tzTOjaW_i0zXZK=VgC0JwuLZ4QvUg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
While going through the mail chain on relation, plan and catalogue
caching [1], I'm thinking on the lines that is there a way to know the
current relation, plan and catalogue cache sizes? If there is a way
already, please ignore this and it would be grateful if someone point
me to that.
Posting this here as I felt it's relevant.
If there is no such way to know the cache sizes and other info such as
statistics, number of entries, cache misses, hits etc. can the
approach discussed here be applied?
If the user knows the cache statistics and other information, may be
we can allow user to take appropriate actions such as allowing him to
delete few entries through a command or some other way.
I'm sorry, If I'm diverting the topic being discussed in this mail
thread, please ignore if it is irrelevant.
With Regards,
Bharath Rupireddy.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Quan Zongliang | 2020-06-26 06:44:40 | bugfix: invalid bit/varbit input causes the log file to be unreadable |
| Previous Message | Amit Kapila | 2020-06-26 06:17:42 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |