Re: strange 'vacuum verbose analyze' behaviour - Mailing list pgsql-hackers

From Tom Lane
Subject Re: strange 'vacuum verbose analyze' behaviour
Date
Msg-id 22985.1106852816@sss.pgh.pa.us
Whole thread Raw
In response to strange 'vacuum verbose analyze' behaviour  (Oleg Bartunov <oleg@sai.msu.su>)
Responses Re: strange 'vacuum verbose analyze' behaviour
List pgsql-hackers
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.

It is a bit odd that nothing is getting deleted from "ipix_ind" ...
is that a partial index?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Patent issues and 8.1
Next
From: "Marc G. Fournier"
Date:
Subject: Security Release Packaging ...