Re: controlling autovacuum during the day.
От | John Lister |
---|---|
Тема | Re: controlling autovacuum during the day. |
Дата | |
Msg-id | F0567BC539DF4B15AE66583CA56A6546@squarepi.com обсуждение исходный текст |
Ответ на | Re: controlling autovacuum during the day. ("John Lister" <john.lister-ps@kickstone.com>) |
Ответы |
Re: controlling autovacuum during the day.
|
Список | pgsql-admin |
> John Lister wrote: > >> bizarre... Its been turned off for a while, but from memory the >> autovacuum process was causing the table it was running on to be locked >> - I assumed this was an equivalent to VACUUM FULL - causing all other >> connections to wait until it had finished. Could this happen another way, >> i thought the other vacuum options acted passively... I'll turn it back >> on and see what happens... > > Maybe you're doing ALTER TABLE or something else that is blocked behind > vacuum? Vacuum doesn't block INSERT, UPDATE or DELETE, but it can block > other operations that want exclusive locks on the table. > > What Postgres version is this anyway? Now running 8.3, but this was on 8.2. This was just with standard updates, etc I guess i need to turn autovacuum back on to see what happens...
В списке pgsql-admin по дате отправления: