Re: strange 'vacuum verbose analyze' behaviour

From: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: strange 'vacuum verbose analyze' behaviour
Date: 2005-01-27 20:33:09
Message-ID: Pine.GSO.4.62.0501272332000.6701@ra.sai.msu.su
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 27 Jan 2005, Tom Lane wrote:

> Oleg Bartunov <oleg(at)sai(dot)msu(dot)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(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message ITAGAKI Takahiro 2005-01-27 21:28:32 Re: [HACKERS] WAL: O_DIRECT and multipage-writer
Previous Message Tom Lane 2005-01-27 20:32:39 Re: Security Release Packaging ...