| From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
|---|---|
| To: | Nicolas Aubert <aubertnicolas11(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: vacuum analyse waiting |
| Date: | 2016-03-21 15:35:38 |
| Message-ID: | 20160321153537.GA14547@depesz.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Mon, Mar 21, 2016 at 04:26:40PM +0100, Nicolas Aubert 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
>
I'm sure there are more columns in pg_locks.
What you need to find is the rows with pid of vacuum, that have granted
= 'false', and see what the lock is on (the columns you ignored).
Then you check what has conflicting locks on the required things.
Best regards,
depesz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | bricklen | 2016-03-21 15:37:06 | Re: vacuum analyse waiting |
| Previous Message | Nicolas Aubert | 2016-03-21 15:26:40 | Re: vacuum analyse waiting |