Re: Cursor vs Set Operation

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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Mark Dilger 2017-11-01 18:03:28 Re: proposal: schema variables
Previous Message Pavel Stehule 2017-11-01 05:56:03 Re: proposal: schema variables