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

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

From: Alessandro Gagliardi <alessandro(at)path(dot)com>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: 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:26:47
Message-ID: CAAB3BB+HOQmdTkL0gSYtFOWtP7q=Qtr10R6yHU+idFEpHi5kVA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
Got it (with a little bit of klutzing around). :) Thanks!

On Mon, Jan 30, 2012 at 2:24 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>wrote:

> 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

pgsql-performance by date

Next:From: Carlo StonebanksDate: 2012-01-30 23:15:17
Subject: Re: pl/pgsql functions outperforming sql ones?
Previous:From: Scott MarloweDate: 2012-01-30 22:24:24
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