[PERFORM] Re: Query planner gaining the ability to replanning after start of query execution.

As a first step, before relaunching the query with a new plan I would be happy to be able to get information about sql queries having wrong estimates. Maybe thoses SQL queries could be collected using something similar to "auto_explain" module (tracing finished or cancelled queries). If the "corr

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

To limit NL usage, wouldn't a modified set of Planner Cost Constants 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_ope

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

Hello, may I suggest you to look at https://github.com/ossc-db/pg_hint_plan that mimics Oracle hints syntax Regards PAscal -- Sent from: http://www.postgresql-archive.org/PostgreSQL-performance-f2050081.html -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To m

Re: [PERFORM] postgresql tuning with perf

Once again you are speaking about edb port of postgresql. The edb pl sql code is not public. This is not the good place to get support: please ask your edb contract manager. If you want support hère: please rewrite your oracle proc in pl pqsql, share that code and commit strategy ... Postgres doesn

Re: [PERFORM] postgresql tuning with perf

Please share how you monitor your perfs. At less duration for each plpgsql proc / oracle proc. Please share your plpgsql code, and commit strategy. (for support with edb please check with your contract manager) -- Sent from: http://www.postgresql-archive.org/PostgreSQL-performance-f2050081.ht

Re: [PERFORM] postgresql tuning with perf

Hi, could you providence the code used with PG ? Has table dept_new an index/pk on c1 ? Do you analyze this table after loading it ? Regards PAscal -- Sent from: http://www.postgresql-archive.org/PostgreSQL-performance-f2050081.html -- Sent via pgsql-performance mailing list (pgsql-performa