Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 43AB8682EAE for ; Sat, 3 Dec 2011 11:16:04 -0400 (AST) Received: from sam.nabble.com ([216.139.236.26]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RWrJr-0004H4-Vw for pgsql-performance@postgresql.org; Sat, 03 Dec 2011 15:16:04 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1RWrJf-00055s-Fx for pgsql-performance@postgresql.org; Sat, 03 Dec 2011 07:15:51 -0800 Date: Sat, 3 Dec 2011 07:15:51 -0800 (PST) From: MirrorX To: pgsql-performance@postgresql.org Message-ID: <1322925351487-5044691.post@n5.nabble.com> In-Reply-To: <4EDA3BCD.30507@fuzzy.cz> References: <1322922869210-5044616.post@n5.nabble.com> <4EDA3BCD.30507@fuzzy.cz> Subject: Re: manually force planner to use of index A vs index B MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: 0.0 (/) X-Archive-Number: 201112/19 X-Sequence-Number: 45819 thx a lot for the reply. i will post the query plans when a new bulk insert will take place :) -- View this message in context: http://postgresql.1045698.n5.nabble.com/manually-force-planner-to-use-of-index-A-vs-index-B-tp5044616p5044691.html Sent from the PostgreSQL - performance mailing list archive at Nabble.com.