Re: proposal for 9.5: monitoring lock time for slow queries

From: "MauMau" <maumau307(at)gmail(dot)com>
To: "Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com>, "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>
Cc: "Michael Paquier" <michael(dot)paquier(at)gmail(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal for 9.5: monitoring lock time for slow queries
Date: 2014-08-19 13:44:22
Message-ID: 5655F5E79C8E46D7AA89C9DA003A1FD3@maumau
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From: "Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com>
> Is this supposed to be session-local data, or is it visible from remote
> sessions too? How durable is it supposed to be? Keep in mind that in
> case of a crash, all pgstats data is erased.

I want it to be visible from other sessions. I'm okay about the data
erasure during recovery. We can probably extend pg_statsinfo to save the
new info for long-term trend analysis. TBH, I want a feature like
pg_statsinfo in core.

Regards
MauMau

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2014-08-19 13:47:26 Re: Reporting the commit LSN at commit time
Previous Message MauMau 2014-08-19 13:35:49 Re: [patch] pg_copy - a command for reliable WAL archiving