| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | patibandlakoshal <patibandlakoshal(at)gmail(dot)com> |
| Cc: | postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Cursor vs Set Operation |
| Date: | 2017-11-01 16:28:12 |
| Message-ID: | CAHyXU0zhQeC+SfinvmjX1vSYdDfcxeukLV8_se7gMWyXM=S_tg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Oct 30, 2017 at 5:51 PM, patibandlakoshal
<patibandlakoshal(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gunther | 2017-11-02 00:28:41 | OLAP/reporting queries fall into nested loops over seq scans or other horrible planner choices |
| Previous Message | Julien Rouhaud | 2017-10-31 20:04:12 | Re: Index-Advisor Tools |