Re: strange 'vacuum verbose analyze' behaviour
От | Oleg Bartunov |
---|---|
Тема | Re: strange 'vacuum verbose analyze' behaviour |
Дата | |
Msg-id | Pine.GSO.4.62.0501272332000.6701@ra.sai.msu.su обсуждение исходный текст |
Ответ на | Re: strange 'vacuum verbose analyze' behaviour (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
On Thu, 27 Jan 2005, Tom Lane wrote: > Oleg Bartunov <oleg@sai.msu.su> writes: >> Day ago we run 'vacuum verbose analyze;' and now we're observing >> strange output (see below). We see many repeated passes through the >> table 'usno' and all indices (2). > > Nothing strange about it: that's how vacuum deals with large tables. > You can reduce the number of passes over the indexes by increasing > maintenance_work_mem (aka vacuum_mem). It looks like you have that > set to 16MB, which is enough to hold about 2.79M 6-byte CTIDs. When > that fills up, we have to go and clean out the corresponding index > entries before we resume scanning the heap. > thanks for info, just increased maintenance_work_mem and will see > It is a bit odd that nothing is getting deleted from "ipix_ind" ... > is that a partial index? no. wsdb=# \d ipix_ind Index "public.ipix_ind" Column | Type --------+-------- ipix | bigint btree, for table "public.usno" > > regards, tom lane > Regards, Oleg _____________________________________________________________ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83
В списке pgsql-hackers по дате отправления: