Postgres Pro
Downloads
Home   >   mailing lists

[PERFORM] Re: OLAP/reporting queries fall into nested loops over seq scans orother horrible planner choices - Mailing list pgsql-performance

From legrand legrand
Subject [PERFORM] Re: OLAP/reporting queries fall into nested loops over seq scans orother horrible planner choices
Date
Msg-id 1509720945908-0.post@n3.nabble.com
Whole thread Raw
In response to Re: [PERFORM] Re: OLAP/reporting queries fall into nested loops overseq scans or other horrible planner choices  (Gunther <raj@gusw.net>)
Responses Re: [PERFORM] Re: OLAP/reporting queries fall into nested loops overseq scans or other horrible planner choices
List pgsql-performance
Tree view 
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


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

pgsql-performance by date:

Previous
From: Gunther
Date:
Subject: Re: [PERFORM] Re: OLAP/reporting queries fall into nested loops overseq scans or other horrible planner choices
Next
From: Gunther
Date:
Subject: Re: [PERFORM] Re: OLAP/reporting queries fall into nested loops overseq scans or other horrible planner choices