From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: GIN fast update technique and work_mem |
Date: | 2013-10-24 10:26:01 |
Message-ID: | 20131024102601.GA1197176@alap2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2013-10-24 18:40:46 +0900, Amit Langote wrote:
> 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?
Yes. One is about the initial index creation, the other about insertions
into an existing index.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Rémi Cura | 2013-10-24 12:04:56 | GIST index : order Hack : getting the order used by CLUSTER .. USING my_index |
Previous Message | Amit Langote | 2013-10-24 09:40:46 | GIN fast update technique and work_mem |