Re: Query performance over a large proportion of data
От
Steve McLellan
Тема
Re: Query performance over a large proportion of data
Дата
Msg-id
cfca83d70903102030h3fdff9f6n6e55b4161a216a56@mail.gmail.com
Список
Дерево обсуждения
Query performance over a large proportion of data "Steve McLellan" <smclellan@mintel.com>
Re: Query performance over a large proportion of data Tom Lane <tgl@sss.pgh.pa.us>
Re: Query performance over a large proportion of
data "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Re: Query performance over a large proportion of data Tom Lane <tgl@sss.pgh.pa.us>
Re: Query performance over a large proportion of data Scott Marlowe <scott.marlowe@gmail.com>
Re: Query performance over a large proportion of data Scott Marlowe <scott.marlowe@gmail.com>
Re: Query performance over a large proportion of data decibel <decibel@decibel.org>
Re: Query performance over a large proportion of data Matteo Beccati <php@beccati.com>
"Kevin Grittner" <Kevin.Grittner@wicourts.gov>
03/10/2009 05:06 PM EST
> enable_seqscan = off
Not a good idea; some queries will optimize better with seqscans.
You can probably get the behavior you want using other adjustments.
The bullet to cure the headache, as Scott said.
You probably need to reduce random_page_cost. If your caching is
complete enough, you might want to set it equal to seq_page_cost
(never set it lower that seq_page_cost!) and possibly reduce both of
these to 0.1.
Thanks again, Steve
В списке pgsql-performance по дате отправления
