Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 1D9B265020B for ; Wed, 23 Jul 2008 17:44:48 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 53247-10 for ; Wed, 23 Jul 2008 17:44:42 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id F3B27650111 for ; Wed, 23 Jul 2008 17:44:44 -0300 (ADT) Received: from perhan.alvh.no-ip.org (190-95-31-93.bk17-dsl.surnet.cl [190.95.31.93]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m6NKl6pb030876 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jul 2008 13:47:10 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 6AE1147C87; Wed, 23 Jul 2008 16:44:30 -0400 (CLT) Date: Wed, 23 Jul 2008 16:44:30 -0400 From: Alvaro Herrera To: Tom Lane Cc: Teodor Sigaev , Pgsql Hackers Subject: Re: [PATCHES] GIN improvements Message-ID: <20080723204430.GD3580@alvh.no-ip.org> References: <483FD205.4090904@sigaev.ru> <486BC501.6060605@sigaev.ru> <27880.1215810535@sss.pgh.pa.us> <487A6E0C.3090600@sigaev.ru> <8993.1216843701@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8993.1216843701@sss.pgh.pa.us> User-Agent: Mutt/1.5.18 (2008-05-17) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Wed, 23 Jul 2008 13:47:11 -0700 (PDT) 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: 200807/1095 X-Sequence-Number: 121355 Tom Lane wrote: > Teodor Sigaev writes: > I didn't get much further than that because I got discouraged after > looking at the locking issues around the pending-insertions list. > It's a mess: These are rather severe problems. Maybe there's a better solution, but perhaps it would be good enough to lock out concurrent access to the index while the bulkinsert procedure is working. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.