>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
