| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Irodotos Terpizis <irodotosterpizis(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Printing page request trace from buffer manager |
| Date: | 2021-02-20 22:20:24 |
| Message-ID: | 20210220222024.GA19200@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Dec-08, Irodotos Terpizis wrote:
> Initially, I modified the code within the BufferAlloc method in the
> bufmgr.c file,
> to log the pages that were requested and were already in the cache,
> the pages that were evicted and the pages that
> replaced them. However, I feel that this might not be the most optimal
> way, as the log file is a mess and
> it is hard to analyze. I was wondering if there is a more optimal way
> to achieve this.
Hi Irodotos,
Did you find an answer to this question? Can you explain in what way
the log is a mess?
Maybe you need to start by defining how would you like the log file to
look.
--
Álvaro Herrera 39°49'30"S 73°17'W
"La conclusión que podemos sacar de esos estudios es que
no podemos sacar ninguna conclusión de ellos" (Tanenbaum)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-02-20 23:14:45 | Re: Extensions not dumped when --schema is used |
| Previous Message | Tom Lane | 2021-02-20 22:20:19 | Bizarre behavior of \w in a regular expression bracket construct |