Re: regular logging of checkpoint progress

From: Andy Colson <andy(at)squeakycode(dot)net>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Tomas Vondra <tv(at)fuzzy(dot)cz>
Subject: Re: regular logging of checkpoint progress
Date: 2011-09-05 18:02:46
Message-ID: 4E650EC6.7040703@squeakycode.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 09/05/2011 12:17 PM, Andy Colson wrote:
> Tomas, I cannot seem to see any of the patches you link here:
>
> https://commitfest.postgresql.org/action/patch_view?id=628
>
> Looks like you need to take the < > out of the messageid.
>
> -Andy
>

This patch seems to solve the problem of going back in time to solve a problem. (need time stamped log files to see if things where slow because of checkpoint).

Several people thought a view or some-non-log option would be better. Tomas replied "but I need to go back in time to post diagnose a problem", and I saw no replies to that.

Taking into account Noah's and Greg's "Displaying accumulated autovacuum cost" patch is also sending to logs, do we all now agree that this is proper way?

-Andy

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2011-09-05 18:13:58 Re: [GENERAL] pg_upgrade problem
Previous Message Tom Lane 2011-09-05 18:01:46 Re: Redundant bitmap index scans on smallint column