Re: Query planner wants to use seq scan

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Bertrand Paquet <bertrand(dot)paquet(at)doctolib(dot)fr>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Query planner wants to use seq scan
Date: 2015-10-28 03:07:38
Message-ID: 56303BFA.4010003@BlueTreble.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 10/27/15 3:56 PM, Bertrand Paquet wrote:
> Tonight, the index on the three field is used, may be my yesterday
> vacuum updated stats.

BTW, you can run just ANALYZE, which is *far* faster than a VACUUM on a
large table.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Javier Muro 2015-10-28 05:04:04 Scalability to more than 64 cores With PG 9.4 and RHEL 7.1 Kernel 3.10
Previous Message Jim Nasby 2015-10-28 02:59:12 Re: Partition Constraint Exclusion Limits