Date: Tue, 15 Sep 2015 21:45:44 -0700 (MST)
From: gmb <gmbouwer@gmail.com>
To: pgsql-sql@postgresql.org
Message-ID: <1442378744681-5866097.post@n5.nabble.com>
In-Reply-To: 
 <CAOBG12=eaYK5Zsgdu9Oes3s5jeQv8Feb9arMKBR6rk+pOERiNg@mail.gmail.com>
References: <1442318204445-5865953.post@n5.nabble.com>
 <CAOBG12=eaYK5Zsgdu9Oes3s5jeQv8Feb9arMKBR6rk+pOERiNg@mail.gmail.com>
Subject: Re: View not using index
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

Thanks for the reply, Brice.


Brice Andr=C3=A9 wrote
>    - If your test DB has so few data that it is not efficient to use the
>    index, this last will not be used. You should probably try to insert
> more
>    data before performing the test
>    - the query planner uses table statistics to decide if it uses an
> index.
>    But, if those statistics are not up-to-date, the choice can be not
> optimal.
>    You should maybe try to look at 'Analyse' command to get more info :

As I said, the data in my production env is populated but I'm getting the
same results, even after running ANALYZE on the tables.


--
View this message in context: http://postgresql.nabble.com/View-not-using-i=
ndex-tp5865953p5866097.html
Sent from the PostgreSQL - sql mailing list archive at Nabble.com.


--=20
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql