Skip site navigation (1) Skip section navigation (2)

Re: Why should such a simple query over indexed columns be so slow?

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Alessandro Gagliardi <alessandro(at)path(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Why should such a simple query over indexed columns be so slow?
Date: 2012-01-30 22:24:24
Message-ID: CAOR=d=2z1JjcK_97aLMNA-Q=3OFDD2yByg80fM5yuJkrcdTv-Q@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Mon, Jan 30, 2012 at 3:19 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Mon, Jan 30, 2012 at 2:55 PM, Alessandro Gagliardi
> <alessandro(at)path(dot)com> wrote:
>> I set random_page_cost to 2 (with enable_seqscan on) and get the same
>> performance I got with enable_seqscan off.
>> So far so good. Now I just need to figure out how to set it globally. :-/
>
> alter database set random_page_cost=2.0;

That should be:

alter database dbnamegoeshere set random_page_cost=2.0;



-- 
To understand recursion, one must first understand recursion.

In response to

Responses

pgsql-performance by date

Next:From: Alessandro GagliardiDate: 2012-01-30 22:26:47
Subject: Re: Why should such a simple query over indexed columns be so slow?
Previous:From: Scott MarloweDate: 2012-01-30 22:19:16
Subject: Re: Why should such a simple query over indexed columns be so slow?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group