On Mon, Oct 30, 2017 at 5:51 PM, patibandlakoshal <patibandlakoshal@xxxxxxxxx> 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@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
