Now that we have log_checkpoints, consider resubmitting this with just
the new information you want to add. Thanks.
---
Satoshi Nagayasu wrote:
> Hi all,
>
> Here is a brand new patch to log a checkpointing load informatio
Greg,
Thanks for comments.
Greg Smith wrote:
> The idea of using pg_rusage_init is a new one though; I hadn't thought the
> CPU usage info was interesting enough to figure out how to collect it.
> The way the patch mentioned above works it would be hard to squeeze it in
> the line usefully for
On Tue, 12 Jun 2007, Satoshi Nagayasu wrote:
Here is a brand new patch to log a checkpointing load information
to tune the bgwriter parameter.
There is a work in progress patch that logs this and additional checkpoint
information being reviewed in hopes of making it into the 8.3 build. See
2007/6/13, Alvaro Herrera <[EMAIL PROTECTED]>:
Well, more I/O numbers would be more interesting than CPU stats ...
Well, I think so too, and I attempted to print block in / out using getrusage(),
but I couldn't get them because they were always zero (on my linux).
I still can't understand the
Satoshi Nagayasu wrote:
> Hi all,
>
> Here is a brand new patch to log a checkpointing load information
> to tune the bgwriter parameter.
>
> When you enable trace_checkpoint parameter and process
> the checkpoint, the bgwriter logs the number of
> flushed buffer pages and the elapsed time.
I do
Hi all,
Here is a brand new patch to log a checkpointing load information
to tune the bgwriter parameter.
When you enable trace_checkpoint parameter and process
the checkpoint, the bgwriter logs the number of
flushed buffer pages and the elapsed time.
Hi all,
Here is a brand new patch to log a checkpointing load information
to tune the bgwriter parameter.
When you enable trace_checkpoint parameter and process
the checkpoint, the bgwriter logs the number of
flushed buffer pages and the elapsed time.
