From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
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 03:12:33 |
Message-ID: | 3E7931A1.6124DAD6@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
> 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
AccessShare table locks are only needed.
What is wrong with it ?
regards,
Hiroshi Inoue
http://www.geocities.jp/inocchichichi/psqlodbc/
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-03-20 03:13:14 | Re: cursors outside transactions |
Previous Message | Hiroshi Inoue | 2003-03-20 03:09:25 | Re: A bad behavior under autocommit off mode |