| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Thomas Vatter <thomas(dot)vatter(at)network-inventory(dot)de> |
| Cc: | Tino Wildenhain <tino(at)wildenhain(dot)de>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: in memory views |
| Date: | 2006-05-10 15:45:06 |
| Message-ID: | 1147275906.9755.25.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, 2006-05-10 at 10:41, Thomas Vatter wrote:
> Scott Marlowe wrote:
> > What happens if you do this by declaring it as a cursor and then
> > fetching the first row?
> >
>
> I do executeQuery(), for the resultSet I do next() and return one row,
> but wait, I have to review the logic in this area, I can tell you
> tomorrow
A good short test is to run explain analyze on the query from the psql
command line. If it shows an execution time of significantly less than
what you get from you application, then it is likely that the real
problem is that your application is receiving the whole result set via
libpq and waiting for that. A cursor will solve that problem.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | me | 2006-05-10 15:45:37 | Re: in memory views |
| Previous Message | Thomas Vatter | 2006-05-10 15:41:01 | Re: in memory views |