Re: Regarding GIN Fast Update Technique - Mailing list pgsql-hackers

From Amit Langote
Subject Re: Regarding GIN Fast Update Technique
Date
Msg-id CA+HiwqH+r9OxdbFnoKSZRwgdrMAXH3On_8QJioq_A4a0u_NkAA@mail.gmail.com
Whole thread Raw
In response to Re: Regarding GIN Fast Update Technique  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Regarding GIN Fast Update Technique  (Andres Freund <andres@2ndquadrant.com>)
Re: Regarding GIN Fast Update Technique  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Jun 7, 2013 at 11:15 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Wed, Jun 5, 2013 at 10:06 PM, Amit Langote <amitlangote09@gmail.com> wrote:
>> At what point do the entries in the pending list are moved to the main
>> GIN data structure?
>> From documentation, I read that overflowing work_mem and vacuum are
>> two such causes; what about when the concerned backend is to exit and
>> autovacuum has not yet kicked in?
>
> I don't think there's any special handling for that case, nor do I
> think any is needed.
>

Okay, aside from that case, what else would move those to the main
structure? They (the entries in the unsorted pending list) are in the
local memory (work_mem?) of the backend, right?


--
Amit Langote



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Regarding GIN Fast Update Technique
Next
From: Andres Freund
Date:
Subject: Re: extensible external toast tuple support & snappy prototype