GIN fast update technique and work_mem

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: GIN fast update technique and work_mem
Date: 2013-10-24 09:40:46
Message-ID: CA+HiwqGF=OoLp1RWaM4r6EjuahNw_64nKPxWQGveb7nV2LBGuw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andres Freund 2013-10-24 10:26:01 Re: GIN fast update technique and work_mem
Previous Message Eelke Klein 2013-10-24 06:42:15 Wrong estimate in query plan