Re: [HACKERS] Block level parallel vacuum WIP - Mailing list pgsql-hackers

From Claudio Freire
Subject Re: [HACKERS] Block level parallel vacuum WIP
Date
Msg-id CAGTBQpZt9AWDwhDunLkkCG_WTNxYmv-007ePUAhn7+piCDYdYA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Block level parallel vacuum WIP  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: [HACKERS] Block level parallel vacuum WIP  (David Steele <david@pgmasters.net>)
List pgsql-hackers
On Tue, Jan 10, 2017 at 6:42 AM, Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>> Does this work negate the other work to allow VACUUM to use >
>> 1GB memory?
>
> Partly yes. Because memory space for dead TIDs needs to be allocated
> in DSM before vacuum worker launches, parallel lazy vacuum cannot use
> such a variable amount of memory as that work does. But in
> non-parallel lazy vacuum, that work would be effective. We might be
> able to do similar thing using DSA but I'm not sure that is better.

I think it would work well with DSA as well.

Just instead of having a single segment list, you'd have one per worker.

Since workers work on disjoint tid sets, that shouldn't pose a problem.

The segment list can be joined together later rather efficiently
(simple logical joining of the segment pointer arrays) for the index
scan phases.



pgsql-hackers by date:

Previous
From: Claudio Freire
Date:
Subject: Re: [HACKERS] Block level parallel vacuum WIP
Next
From: Robert Haas
Date:
Subject: Re: [DOCS] [HACKERS] Questionable tag usage