GIN fast update technique and work_mem - Mailing list pgsql-general

From Amit Langote
Subject GIN fast update technique and work_mem
Date
Msg-id CA+HiwqGF=OoLp1RWaM4r6EjuahNw_64nKPxWQGveb7nV2LBGuw@mail.gmail.com
Whole thread Raw
Responses Re: GIN fast update technique and work_mem  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-general
Hi,

While going through the documentation for GIN fast update technique, I read -

"...or if the pending list becomes too large (larger than work_mem),
the entries are moved to the main GIN data structure using the same
bulk insert techniques used during initial index creation."

The "work_mem" links to work_mem setting documentation.

Whereas in the src/backend/access/gin/README, as one of the features
of GIN, I read  -

"...* Optimized index creation (Makes use of maintenance_work_mem to accumulate
    postings in memory.)"

So, which one is it - work_mem or maintenance_work_mem?

Or are these things unrelated?


--
Amit


pgsql-general by date:

Previous
From: Eelke Klein
Date:
Subject: Wrong estimate in query plan
Next
From: Andres Freund
Date:
Subject: Re: GIN fast update technique and work_mem