From: | Dave Cramer <Dave(at)micro-automation(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: setFetchSize() |
Date: | 2003-07-18 12:37:30 |
Message-ID: | 1058531850.1574.26.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
I stand corrected.
Dave
On Thu, 2003-07-17 at 22:54, Tom Lane wrote:
> Dave Cramer <Dave(at)micro-automation(dot)net> writes:
> > This isn't true any more, the backend supports with hold now, so you can
> > declare a cursor outside a transaction
>
> However, if the problem is that the query result is too large to hold in
> memory, then a WITH HOLD cursor is a terrible solution. You are simply
> moving the problem of coping with the fully-materialized query result
> out of the client and into the backend. Admittedly the backend is
> probably better able to cope than the client (at least it knows how to
> spill rows to disk...), but if you are trying to get good performance
> on huge result sets you do not want to use a held cursor, any more than
> you want to suck the whole result into client memory.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
--
Dave Cramer <Dave(at)micro-automation(dot)net>
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Tkach | 2003-07-18 14:18:45 | Re: Prepared Statements |
Previous Message | Patric Bechtel | 2003-07-18 11:43:09 | Re: setFetchSize [Viruschecked] [Viruschecked] |