Re: Autovacuum of pg_shdepend

Поиск
Список
Период
Сортировка
От Ondřej Světlík
Тема Re: Autovacuum of pg_shdepend
Дата
Msg-id f7d6e8ef-5147-e34e-a19d-c4ea6fbaa33f@flexibee.eu
обсуждение исходный текст
Ответ на Re: Autovacuum of pg_shdepend  (Ondřej Světlík <osvetlik@flexibee.eu>)
Ответы Re: Autovacuum of pg_shdepend  (Albe Laurenz <laurenz.albe@wien.gv.at>)
Список pgsql-admin
Dne 4.5.2016 v 22:08 Ondřej Světlík napsal(a):
> Dne 4.5.2016 v 20:52 Victor Yegorov napsal(a):
>> 2016-05-04 18:08 GMT+03:00 Ondřej Světlík <osvetlik@flexibee.eu
>> <mailto:osvetlik@flexibee.eu>>:
>>
>>     we have a strange problem with autovacuum. We have three workers,
>>     but usually only one works and two are waiting as they are all
>>     trying to process table pg_shdepend which is shared between all
>>     databases.
>>
>>
>> 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, we have a working autovacuum on one of our clusters
> again. That's awesome :-).
>
> Ondřej


Hello again,

as this is still not fixed in any released version and the problem
occurred again, let me ask one question. Which form of manual VACUUM is
sufficient to prevent wraparound? Is it VACUUM FREEZE or do I have to
use VACUUM FULL?

Thanks in advance,

Ondřej


В списке pgsql-admin по дате отправления:

Предыдущее
От: Bryan Ward
Дата:
Сообщение: Re: Revoke delete on a table for super user
Следующее
От: Albe Laurenz
Дата:
Сообщение: Re: Autovacuum of pg_shdepend