Postgres Pro
Downloads
Home   >   mailing lists

Re: [PERFORM] Cursor vs Set Operation - Mailing list pgsql-performance

From Merlin Moncure
Subject Re: [PERFORM] Cursor vs Set Operation
Date
Msg-id CAHyXU0zhQeC+SfinvmjX1vSYdDfcxeukLV8_se7gMWyXM=S_tg@mail.gmail.com
Whole thread Raw
In response to [PERFORM] Cursor vs Set Operation  (patibandlakoshal <patibandlakoshal@gmail.com>)
List pgsql-performance
Tree view 
On Mon, Oct 30, 2017 at 5:51 PM, patibandlakoshal
<patibandlakoshal@gmail.com> 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  a little more specific.  In particular, I
have no idea what a 'cursor plan' is.  What precise operations did you
do?

merlin


-- 
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: Julien Rouhaud
Date:
Subject: Re: [PERFORM] Index-Advisor Tools
Next
From: Gunther
Date:
Subject: [PERFORM] OLAP/reporting queries fall into nested loops over seq scans or otherhorrible planner choices