From: | Robert Treat <rob(at)xzilla(dot)net> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Greg Smith <greg(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: We need to log aborted autovacuums |
Date: | 2011-01-05 22:56:51 |
Message-ID: | AANLkTi=Zz=3vh5x=+t+PG5b9XcVeZkVQYHHHxUZ8tVJ4@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 5, 2011 at 2:27 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>
>> If you could gather more info on whether this logging catches the
>> problem cases you're seeing, that would really be the right test for the
>> patch's usefulness. I'd give you solid 50/50 odds that you've correctly
>> diagnosed the issue, and knowing for sure would make advocating for this
>> logging a pretty easy sell to me at least.
>
> Well, I already resolved the issue through polling pg_locks. The issue
> was IIT sessions which lasted up to an hour, which we fixed in the
> application, so I don't have the test case available anymore. I'd have
> to generate a synthetic test case, and since I agree that a SQL-callable
> diagnostic is superior to logging, I don't think we should pursue the
> log levels further.
>
This is a great use case for user level tracing support. Add a probe
around these bits, and you can capture the information when you need
it.
Robert Treat
http://www.xzilla.net
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2011-01-05 23:06:11 | Re: We need to log aborted autovacuums |
Previous Message | Dimitri Fontaine | 2011-01-05 22:27:09 | Re: Streaming base backups |