Re: How about a option to disable autovacuum cancellation on lock conflict?
От | Andres Freund |
---|---|
Тема | Re: How about a option to disable autovacuum cancellation on lock conflict? |
Дата | |
Msg-id | 20141202194149.GM2456@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: How about a option to disable autovacuum cancellation on lock conflict? (Jeff Janes <jeff.janes@gmail.com>) |
Ответы |
Re: How about a option to disable autovacuum cancellation
on lock conflict?
|
Список | pgsql-hackers |
On 2014-12-02 11:23:31 -0800, Jeff Janes wrote: > I think it would be more promising to work on downgrading lock strengths so > that fewer things conflict, and it would be not much more work than what > you propose. I think you *massively* underestimate the effort required to to lower lock levels. There's some very ugly corners you have to think about to do so. Just look at how long it took to implement the lock level reductions for ALTER TABLE - and those were the simpler cases. > What operations are people doing on a regular basis that take locks > which cancel vacuum? create index? Locking tables against modifications in this case. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: