Re: [PERFORM] More detail on settings for pgavd?
| От | Greg Stark |
|---|---|
| Тема | Re: [PERFORM] More detail on settings for pgavd? |
| Дата | |
| Msg-id | 877k1t2pkq.fsf@stark.dyndns.tv обсуждение исходный текст |
| Ответ на | Re: [PERFORM] More detail on settings for pgavd? (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: [PERFORM] More detail on settings for pgavd?
|
| Список | pgsql-hackers |
Tom Lane <tgl@sss.pgh.pa.us> writes: > Josh Berkus <josh@agliodbs.com> writes: > > BTW, do we have any provisions to avoid overlapping vacuums? That is, to > > prevent a second vacuum on a table if an earlier one is still running? > > Yes, VACUUM takes a lock that prevents another VACUUM on the same table. The second vacuum waits for the lock to become available. If the situation got really bad there could end up being a growing queue of vacuums waiting. I'm not sure how likely this is as the subsequent vacuums appear to finish quite quickly though. But then the largest table I have to play with fits entirely in memory. -- greg
В списке pgsql-hackers по дате отправления: