From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Regarding GIN Fast Update Technique |
Date: | 2013-06-07 14:28:56 |
Message-ID: | CA+HiwqH+r9OxdbFnoKSZRwgdrMAXH3On_8QJioq_A4a0u_NkAA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jun 7, 2013 at 11:15 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Wed, Jun 5, 2013 at 10:06 PM, Amit Langote <amitlangote09(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2013-06-07 14:30:53 | Re: extensible external toast tuple support & snappy prototype |
Previous Message | Robert Haas | 2013-06-07 14:15:24 | Re: Regarding GIN Fast Update Technique |