Re: cursors outside transactions

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dave Cramer <Dave(at)micro-automation(dot)net>, Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: cursors outside transactions
Date: 2003-03-20 02:59:03
Message-ID: 200303200259.h2K2x3d00764@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hiroshi Inoue wrote:
> > I don't see how you can class out of memory in the same likelyhood as
> > out of disk --- sure they are both real possible failures, but clearly
> > the latter is more rare and giving folks backing store for large result
> > sets is a big win in my book.
>
> Other than the out of disk/memory problem, there 's
> another problem. What I expect of cursors is the
> constant response time while handling them.

Cursors outside transactions either need materialization or long-lived
locks --- I don't see any other possibilities, and most feel
materialization is the best.

Do you see another option?

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 2003-03-20 03:08:00 Re: Nested transactions: low level stuff
Previous Message Thomas T. Thai 2003-03-20 02:56:24 Re: string || NULL ambiguity