From: Kevin Grittner <kgrittn@ymail.com>
To: Stefan Keller <sfkeller@gmail.com>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: FTS performance issue - planner problem identified (but only partially resolved)
Date: Mon, 29 Jul 2013 13:28:56 -0700 (PDT)
Message-ID: <1375129736.38828.YahooMailNeo@web162901.mail.bf1.yahoo.com> (raw)
In-Reply-To: <CAFcOn2_Ei2nf+-odnWost0niAsvfcrsJe_LuV4X9P7KG0FJcQA@mail.gmail.com>
References: <CAFcOn2_Ei2nf+-odnWost0niAsvfcrsJe_LuV4X9P7KG0FJcQA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
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
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: kgrittn@ymail.com, sfkeller@gmail.com
Subject: Re: FTS performance issue - planner problem identified (but only partially resolved)
In-Reply-To: <1375129736.38828.YahooMailNeo@web162901.mail.bf1.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox