From: | Maik Wiege <mswiege(at)gmx(dot)de> |
---|---|
To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: get row count from a "cursor resultset" |
Date: | 2005-07-06 23:33:46 |
Message-ID: | 42CC6A5A.2000605@gmx.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Oliver Jowett wrote:
> Ok, some digging in pgAdmin's svn web interface seems to indicate that
> pgadmin is not actually doing anything special here -- it does the full
> query via libpq's PQexec(), retrieving all the tuples (and hence can
> count them) but only does the work to construct a user interface
> displaying them all after that "lots of rows, retrieve anyway?" dialog
> has been answered.
>
> You could check this by looking at pgadmin's memory footprint while
> retrieving a big resultset.
Thank you for your answers! Yes, this explains it, it is realy using
much memory. But what can I do about my problem? Isn't this a very
common problem? Can't imagine any user querying a database and does not
want to be informed how many results he got...
Thanks for any help
Maik
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2005-07-06 23:35:59 | Re: get row count from a "cursor resultset" |
Previous Message | Oliver Jowett | 2005-07-06 22:50:50 | Re: get row count from a "cursor resultset" |