Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id CEEE2632FDB
	for <pgsql-hackers-postgresql.org@mail.postgresql.org>;
	Wed, 11 Feb 2009 10:53:46 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 17170-04
	for <pgsql-hackers-postgresql.org@mail.postgresql.org>;
	Wed, 11 Feb 2009 10:53:42 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from hook.sigaev.ru (hook.sigaev.ru [212.192.243.50])
	by mail.postgresql.org (Postfix) with ESMTP id 13A6C632FDA
	for <pgsql-hackers@postgresql.org>;
	Wed, 11 Feb 2009 10:53:43 -0400 (AST)
Received: by hook.sigaev.ru (Postfix, from userid 1003)
	id 8176F398F0; Wed, 11 Feb 2009 17:53:40 +0300 (MSK)
Received: from xor.sai.msu.ru (xor.sai.msu.ru [212.192.243.97])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: teodor)
	by hook.sigaev.ru (Postfix) with ESMTPSA id 56677398E2;
	Wed, 11 Feb 2009 17:53:36 +0300 (MSK)
Message-ID: <4992E670.5010507@sigaev.ru>
Date: Wed, 11 Feb 2009 17:53:36 +0300
From: Teodor Sigaev <teodor@sigaev.ru>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US;
	rv:1.8.1.19) Gecko/20081222 SeaMonkey/1.1.14
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: Jeff Davis <pgsql@j-davis.com>, Robert Haas <robertmhaas@gmail.com>,
	Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>,
	Pgsql Hackers <pgsql-hackers@postgresql.org>
Subject: Re: [PATCHES] GIN improvements
References: <483FD205.4090904@sigaev.ru> <1232348905.7281.114.camel@jdavis>
	<4974B002.3040202@sigaev.ru> <1232474489.23316.8.camel@jdavis>
	<49770FD4.5030600@sigaev.ru> <1232561271.23793.46.camel@jdavis>
	<497864DC.5080800@sigaev.ru> <4979BAF8.1000501@sigaev.ru>
	<16080.1233625091@sss.pgh.pa.us>
	<1233772747.3805.2.camel@dell.linuxdev.us.dell.com>
	<603c8f070902041140h35c2aeo8c4ed79cd16400f8@mail.gmail.com>
	<1233782589.3805.12.camel@dell.linuxdev.us.dell.com>
	<20441.1234209245@sss.pgh.pa.us>
In-Reply-To: <20441.1234209245@sss.pgh.pa.us>
Content-Type: text/plain; charset=KOI8-R; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none
X-Spam-Level: 
X-Archive-Number: 200902/565
X-Sequence-Number: 133855

> But the real bottom line is: if autovacuum is working properly, it
> should clean up the index before the list ever gets to the point where
> it'd be sane to turn off indexscans.  So I don't see why we need to hack
> the planner for this at all.  If any hacking is needed, it should be
> in the direction of making sure autovacuum puts sufficient priority
> on this task.

Autovacuum will start if table has GIN index with fastupdate=on and number of 
inserted tuple since last vacuum > autovacuum_vacuum_threshold.
-- 
Teodor Sigaev                                   E-mail: teodor@sigaev.ru
                                                    WWW: http://www.sigaev.ru/