From: Teodor Sigaev <teodor@sigaev.ru>
To: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: Patches <pgsql-patches@postgresql.org>
Subject: Re: GIN improvements
Date: Fri, 06 Jun 2008 18:16:38 +0400
Message-ID: <484946C6.1080807@sigaev.ru> (raw)
In-Reply-To: <4849436F.30703@enterprisedb.com>
References: <483FD205.4090904@sigaev.ru>
<4849418C.6080909@sigaev.ru>
<4849436F.30703@enterprisedb.com>
> How about having a constant sized "fastupdate" buffer, of say 100 rows
> or a fixed number of pages, and when that becomes full, the next
> inserter will have to pay the price of updating the index and flushing
I'm not sure that is acceptable because flushing pending list may take several
seconds in unpredictable moment.
> the buffer. To keep that overhead out of the main codepath, we could
> make autovacuum to flush the buffers periodically.
Do you mean that GIN sends a "smoke signal" to the autovacuum launcher process
to ask about vacuum?
--
Teodor Sigaev E-mail: teodor@sigaev.ru
WWW: http://www.sigaev.ru/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-patches@postgresql.org
Cc: teodor@sigaev.ru, heikki@enterprisedb.com
Subject: Re: GIN improvements
In-Reply-To: <484946C6.1080807@sigaev.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox