| From: | patibandlakoshal <patibandlakoshal(at)gmail(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Cursor vs Set Operation |
| Date: | 2017-10-30 22:51:06 |
| Message-ID: | 1509403866560-0.post@n3.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | luisfpg | 2017-10-31 16:30:08 | Massive insert vs heavy contention in LWLock:buffer_content |
| Previous Message | Tom Lane | 2017-10-29 14:58:00 | Re: Cheaper subquery scan not considered unless offset 0 |