Re: OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices

From: legrand legrand <legrand_legrand(at)hotmail(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices
Date: 2017-11-03 14:55:45
Message-ID: 1509720945908-0.post@n3.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

To limit NL usage, wouldn't a modified set of Planner Cost Constants
https://www.postgresql.org/docs/current/static/runtime-config-query.html
<https://www.postgresql.org/docs/current/static/runtime-config-query.html>

seq_page_cost
random_page_cost
cpu_tuple_cost
cpu_index_tuple_cost
cpu_operator_cost

be more hash join freindly (as Oracle' optimizer_index_cost_adj )?

--
Sent from: http://www.postgresql-archive.org/PostgreSQL-performance-f2050081.html

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Gunther 2017-11-03 15:13:35 Re: Re: OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices
Previous Message Gunther 2017-11-03 14:51:31 Re: Re: OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices