From: | Nicolas Aubert <aubertnicolas11(at)gmail(dot)com> |
---|---|
To: | bricklen <bricklen(at)gmail(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: vacuum analyse waiting |
Date: | 2016-03-22 06:35:03 |
Message-ID: | CAEnLzzUf2=nMZtU7CEa3LAZF60p_waEirF_aHCOY3ZxQOm864A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I'm a little lost in solving this problem.
The process vacuum waiting to disappeared. I do not think it is completed
successfully.
How to verify that the vacuum passes successfully?
How to prevent it happening in modewaiting?
2016-03-21 16:37 GMT+01:00 bricklen <bricklen(at)gmail(dot)com>:
>
> On Mon, Mar 21, 2016 at 8:26 AM, Nicolas Aubert <aubertnicolas11(at)gmail(dot)com
> > wrote:
>
>> the vacuum process is the 22510
>> here is what I found in pg_locks
>>
>>
>> virtualtransaction | pid | mode | granted | fastpath
>>
>> ------------+---------------+---------+-------+----------+--------------------+-------+--------------------------+---------+----------
>>
>> 3/376480 | 22510 | ExclusiveLock | t |
>> | | | | |
>> 3/376480 | 22510 | ShareUpdateExclusiveLock | f | f
>>
>
> Have a look at the lock dependency queries at
> https://wiki.postgresql.org/wiki/Lock_dependency_information for more
> information about what is holding the locks.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ferrell, Denise D CTR NSWCDD, H11 | 2016-03-22 14:44:27 | Passing parameters |
Previous Message | Dmitrii Golub | 2016-03-21 23:25:44 | Re: Out of memory psql import! |