From: | Gregg Jaskiewicz <gryzman(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: autovacuum locks |
Date: | 2012-03-02 11:22:22 |
Message-ID: | CAJY59_ihzDeZ-S-qGPqcK4a_A90pRQ8D_yEA6MGD8BhcoCi-iw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Looking at the system bit more now, it look like 'waiting' states are
changing for both the query and autovacuum in pg_stat_activity.
But very slowly. It looks like they both got into that sort of state
that keeps them on the edge of starvation.
So this isn't really a deadlock, but rather very poor performance in
this corner case.
This is a test system, so I can harvest some more data from it.
Already got core files for autovacuum and query connections.
I'm hoping for more suggestions as to how to gather more intel - so
that could be useful to you guys.
Unfortunately my knowledge about locking mechanisms in postgresql is
rather poor, other then the basic one.
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2012-03-02 11:25:35 | Re: Bugs/slowness inserting and indexing cubes |
Previous Message | Gregg Jaskiewicz | 2012-03-02 11:12:39 | Re: autovacuum locks |