| From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
|---|---|
| To: | "Valerie Schneider DSI/DEV" <Valerie(dot)Schneider(at)meteo(dot)fr> |
| Cc: | <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: [GENERAL] Tuning queries on large database |
| Date: | 2004-08-05 13:26:29 |
| Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB34101AF22@Herge.rcsinc.local |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
I wrote:
> Another question:
> How are you benchmarking your queries? Are you running them from
within
> psql? Do you plan to run these queries from within an application?
>
> psql introduces some overhead because it has to scan the result set to
> determine the widths of the columns for formatting purposes. Try
> returning a result set inside the libpq library if you know C and
compare
> the times. Of course, if you are already using libpq, this moot. If
you
> do know libpq, try setting up a loop that fetches the data in 10k
block in
> a loop...I will wager that you can get this to run in under two
minutes
> (Q4).
Whoop, didn't see the aggregate...sorry :)
Merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | G u i d o B a r o s i o | 2004-08-05 14:33:20 | Temporary tables |
| Previous Message | Merlin Moncure | 2004-08-05 13:20:17 | Re: [GENERAL] Tuning queries on large database |