Subject: Re: Autovacuum of pg_shdepend
References: <572A1072.5080308@flexibee.eu>
 <CAGnEbojHefZpb=ywyJV1JAm5MA1epoOy9h7e0h5=_KSey6cSEQ@mail.gmail.com>
To: pgsql-admin@postgresql.org
From: =?UTF-8?B?T25kxZllaiBTdsSbdGzDrWs=?= <osvetlik@flexibee.eu>
Message-ID: <572A4982.7080209@flexibee.eu>
Date: Wed, 4 May 2016 21:12:02 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: 
 <CAGnEbojHefZpb=ywyJV1JAm5MA1epoOy9h7e0h5=_KSey6cSEQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

> I hit the same issue when we've migrated out all large objects (~200Gb
> total), I've executed `vacuumlo` and then all autovacuums started to
> process `pg_shdepend`.
> They've been picking on this table over and over again from different
> databases, but were stopping on the truncation phase due to other
> autovacuums were waiting on the same table.
>
> I ended up manually vacuuming this table in the database, that was
> cleaned up, and also in the `postgres` DB. It fixed the case for me.
> This was on 9.0.23 though.
>
> --
> Victor Y. Yegorov


Thank you very much, Victor, I am going to try your solution. In fact, 
I'm already trying :-).

With regards,

Ondřej


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin