Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 382F3B5DBD6 for ; Thu, 15 Sep 2011 06:43:07 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 79636-08 for ; Thu, 15 Sep 2011 09:42:59 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0-rc2 Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mail.postgresql.org (Postfix) with ESMTP id 3AAE1B5DC07 for ; Thu, 15 Sep 2011 06:42:59 -0300 (ADT) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1R48TC-0000cD-6L for pgsql-performance@postgresql.org; Thu, 15 Sep 2011 02:42:58 -0700 Date: Thu, 15 Sep 2011 02:42:58 -0700 (PDT) From: MirrorX To: pgsql-performance@postgresql.org Message-ID: <1316079778189-4806239.post@n5.nabble.com> In-Reply-To: <27b53c780e44d243118dc5de1b48c3a9.squirrel@sq.gransy.com> References: <1316004607207-4802634.post@n5.nabble.com> <1316005753084-4802699.post@n5.nabble.com> <0ac4fa43876e63ec84515656f233960f.squirrel@sq.gransy.com> <1316013240443-4803198.post@n5.nabble.com> <27b53c780e44d243118dc5de1b48c3a9.squirrel@sq.gransy.com> Subject: Re: cannot use multicolumn index MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.767 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, T_TO_NO_BRKTS_FREEMAIL=0.01, URI_HEX=1.122 X-Spam-Level: X-Archive-Number: 201109/224 X-Sequence-Number: 45000 thank you all for your advice. i will try the table partitioning approach to reduce the size of the tables and to be able to handle them more efficiently -- View this message in context: http://postgresql.1045698.n5.nabble.com/cannot-use-multicolumn-index-tp4802634p4806239.html Sent from the PostgreSQL - performance mailing list archive at Nabble.com.