| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
| Cc: | Joost Kraaijeveld <J(dot)Kraaijeveld(at)Askesis(dot)nl>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pgsql-Performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Performance PG 8.0 on dual opteron / 4GB / 3ware |
| Date: | 2005-11-07 17:45:31 |
| Message-ID: | 436F92BB.7040807@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Dave Page wrote:
>>
>>
>>Now *I* am confused. What does PgAdmin do more than giving
>>the query to
>>the database?
>
>
> Nothing - it just uses libpq's pqexec function. The speed issue in
> pgAdmin is rendering the results in the grid which can be slow on some
> OS's due to inefficiencies in some grid controls with large data sets.
> That's why we give 2 times - the first is the query runtime on the
> server, the second is data retrieval and rendering (iirc, it's been a
> while).
yrnc.
Query runtime includes data transfer to the client, i.e. until libpq
returns the set, second time is retrieving data from libpq and rendering.
Regards,
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Enrico Weigelt | 2005-11-07 18:07:38 | Index + mismatching datatypes [WAS: index on custom function; explain] |
| Previous Message | PostgreSQL | 2005-11-07 17:22:16 | Re: 8.1 iss |