Postgres Pro
Downloads
Home   >   mailing lists

Re: FTS performance issue - planner problem identified (but only partially resolved) - Mailing list pgsql-performance

From Kevin Grittner
Subject Re: FTS performance issue - planner problem identified (but only partially resolved)
Date
Msg-id 1375129736.38828.YahooMailNeo@web162901.mail.bf1.yahoo.com
Whole thread Raw
In response to FTS performance issue - planner problem identified (but only partially resolved)  (Stefan Keller <sfkeller@gmail.com>)
Responses Re: FTS performance issue - planner problem identified (but only partially resolved)
List pgsql-performance
Tree view 
Stefan Keller <sfkeller@gmail.com> wrote:

> Finally, setting random_page_cost to 1 helps also - but I don't
> like this setting neither.

Well, you should learn to like whichever settings best model your
actual costs given your level of caching and your workload.  ;-)
FWIW, I have found page costs less volatile and easier to tune
with cpu_tuple_cost increased.  I just always start by bumping
that to 0.03.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-performance by date:

Previous
From: Jeff Janes
Date:
Subject: Re: How is memory allocated/used by Postgresql Database connections
Next
From: Stefan Keller
Date:
Subject: Re: FTS performance issue - planner problem identified (but only partially resolved)