Re: Query not using Index

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Wei Shan <weishan(dot)ang(at)gmail(dot)com>
Cc: Andreas Kretschmer <akretschmer(at)spamfence(dot)net>, "pgsql-performance(at)postgresql(dot)org list" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Query not using Index
Date: 2016-03-27 19:20:36
Message-ID: CAMkU=1yoZ8g6ozqpSmY_FyhmcPkUCwOGRhoQBp4BR6uFzB3ogQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Sun, Mar 27, 2016 at 9:12 AM, Wei Shan <weishan(dot)ang(at)gmail(dot)com> wrote:
> Hi Andreas,
>
> The tablespace is not on SSD although I intend to do it within the next
> week. I actually tried reducing the random_page_cost to 0.2 but it doesn't
> help.

Setting random_page_cost to less than seq_page_cost is nonsensical.

You could try to increase cpu_tuple_cost to 0.015 or 0.02

Cheers,

Jeff

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Chris Cogdon 2016-03-31 17:03:27 Adding a ROLLUP switches to GroupAggregate unexpectedly
Previous Message Wei Shan 2016-03-27 16:12:43 Re: Query not using Index