Hello.
At Thu, 21 Mar 2019 15:51:40 -0400, Robert Haas <robertmhaas@gmail.com> wrote in
<CA+TgmobkRtLb5frmEF5t9U=d+iV9c5emtN+NrRS_xrHaH1Z20A@mail.gmail.com>
> On Tue, Mar 19, 2019 at 3:59 AM Kyotaro HORIGUCHI
> <horiguchi.kyotaro@lab.ntt.co.jp> wrote:
> > The leader doesn't continue heap-scan while index vacuuming is
> > running. And the index-page-scan seems eat up CPU easily. If
> > index vacuum can run simultaneously with the next heap scan
> > phase, we can make index scan finishes almost the same time with
> > the next round of heap scan. It would reduce the (possible) CPU
> > contention. But this requires as the twice size of shared
> > memoryas the current implement.
>
> I think you're approaching this from the wrong point of view. If we
> have a certain amount of memory available, is it better to (a) fill
> the entire thing with dead tuples once, or (b) better to fill half of
> it with dead tuples, start index vacuuming, and then fill the other
> half of it with dead tuples for the next index-vacuum cycle while the
> current one is running? I think the answer is that (a) is clearly
Sure.
> better, because it results in half as many index vacuum cycles.
The "problem" I see there is it stops heap scanning on the leader
process. The leader cannot start the heap scan until the index
scan on workers end.
The heap scan is expected not to stop by the half-and-half
stratregy especially when the whole index pages are on
memory. But it is not always the case, of course.
> We can't really ask the user how much memory it's OK to use and then
> use twice as much. But if we could, what you're proposing here is
> probably still not the right way to use it.
Yes. I thought that I wrote that with such implication. "requires
as the twice size" has negative implications as you wrote above.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
