Re: autovacuum maintenance_work_mem
От | Alvaro Herrera |
---|---|
Тема | Re: autovacuum maintenance_work_mem |
Дата | |
Msg-id | 1289934213-sup-3051@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: autovacuum maintenance_work_mem (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: autovacuum maintenance_work_mem
|
Список | pgsql-hackers |
Excerpts from Josh Berkus's message of mar nov 16 15:52:14 -0300 2010: > > > I think the difficulty is figuring out what to get the existing > > workers to give us some memory when a new one comes along. You want > > the first worker to potentially use ALL the memory... until worker #2 > > arrives. > > Yeah, doing this would mean that you couldn't give worker #1 all the > memory, because on most OSes it can't release the memory even if it > wants to. Hmm, good point. > Relevant to this is the question: *when* does vacuum do its memory > allocation? Is memory allocation reasonably front-loaded, or does > vacuum keep grabbing more RAM until it's done? All at start. -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-hackers по дате отправления: