Re: Helping planner to chose sequential scan when it improves performance - Mailing list pgsql-general

From David Rowley
Subject Re: Helping planner to chose sequential scan when it improves performance
Date
Msg-id CAApHDvo-NrtZ08bRvdmKo=iNEkLLL0VwTKBziES8t1vKtQKRyg@mail.gmail.com
Whole thread Raw
In response to Helping planner to chose sequential scan when it improves performance  ("Patrick O'Toole" <patrick.otoole@sturdy.ai>)
Responses Re: Helping planner to chose sequential scan when it improves performance  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-general
On Wed, 14 Jun 2023 at 07:28, Patrick O'Toole <patrick.otoole@sturdy.ai> wrote:
> Maybe we are barking up the wrong tree with the previous questions. Are there other configuration parameters we
shouldconsider first to improve performance in situations like the one illustrated?
 

random_page_cost and effective_cache_size are the main settings which
will influence plan A vs plan B.  Larger values of
effective_cache_size will have the planner apply more seq_page_costs
to the index scan.  Lower values of effective_cache_size will mean
more pages will be assumed to cost random_page_cost.

David



pgsql-general by date:

Previous
From: Marc Millas
Date:
Subject: Re: bug or lacking doc hint
Next
From: Tom Lane
Date:
Subject: Re: bug or lacking doc hint