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

> -Original Message- > From: pgsql-performance-ow...@postgresql.org [mailto:pgsql-performance- > ow...@postgresql.org] On Behalf Of Gunther > Sent: Wednesday, November 01, 2017 20:29 > To: pgsql-performance@postgresql.org > Subject: [PERFORM] OLAP/reporting queries fall into nested loops o

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

Hi, this is Gunther, have been with PgSQL for decades, on an off this list. Haven't been on for a long time making my way just fine. But there is one thing that keeps bothering me both with Oracle and PgSQL. And that is the preference for Nested Loops. Over the years the archives have question

Re: [PERFORM] Cursor vs Set Operation

On Mon, Oct 30, 2017 at 5:51 PM, patibandlakoshal wrote: > From performance standpoint I thought set operation was better than Cursor. > But I found Cursor to be more effective than Set operation. Is there a way > we can force optimizer to use cursor plan. QUERY PLAN You're going to have to be

[PERFORM] Cursor vs Set Operation

>From performance standpoint I thought set operation was better than Cursor. But I found Cursor to be more effective than Set operation. Is there a way we can force optimizer to use cursor plan. QUERY PLAN