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

From patibandlakoshal
Subject [PERFORM] Cursor vs Set Operation
Date
Msg-id 1509403866560-0.post@n3.nabble.com
Whole thread Raw
Responses Re: [PERFORM] Cursor vs Set Operation  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-performance
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
































                                                    




--
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: Tom Lane
Date:
Subject: Re: [PERFORM] Cheaper subquery scan not considered unless offset 0
Next
From: luisfpg
Date:
Subject: [PERFORM] Massive insert vs heavy contention in LWLock:buffer_content