public inbox for [email protected]
help / color / mirror / Atom feedCursor vs Set Operation
2+ messages / 2 participants
[nested] [flat]
* Cursor vs Set Operation
@ 2017-10-30 22:51 patibandlakoshal <[email protected]>
0 siblings, 1 reply; 2+ messages in thread
From: patibandlakoshal @ 2017-10-30 22:51 UTC (permalink / raw)
To: pgsql-performance
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Cursor vs Set Operation
@ 2017-11-01 16:28 Merlin Moncure <[email protected]>
parent: patibandlakoshal <[email protected]>
0 siblings, 0 replies; 2+ messages in thread
From: Merlin Moncure @ 2017-11-01 16:28 UTC (permalink / raw)
To: patibandlakoshal <[email protected]>; +Cc: pgsql-performance
On Mon, Oct 30, 2017 at 5:51 PM, patibandlakoshal
<[email protected]> 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 ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2017-11-01 16:28 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2017-10-30 22:51 Cursor vs Set Operation patibandlakoshal <[email protected]>
2017-11-01 16:28 ` Merlin Moncure <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox