Re: Query performance

From: Tom Lane
Subject: Re: Query performance
Date: ,
Msg-id: 4960.1110572472@sss.pgh.pa.us
(view: Whole thread, Raw)
In response to: Re: Query performance  ("Lou O'Quin")
List: pgsql-performance

Tree view

Query performance  ("Lou O'Quin", )
 Re: Query performance  (Tom Lane, )
 Re: Query performance  ("Lou O'Quin", )
  Re: Query performance  (Tom Lane, )
 Re: Query performance  ("Lou O'Quin", )
 Re: Query performance  ("Steinar H. Gunderson", )
  Re: Query performance  (Antonio Batovanja, )
   Re: Query performance  (Christopher Kings-Lynne, )
 Re: Query performance  (Erwin Brandstetter, )
 Re: Query performance  (Erwin Brandstetter, )

"Lou O'Quin" <> writes:
> Hi Tom.  I referenced the status line of pgAdmin.  Per the pgAdmin help
> file:
>
> "The status line will show how long the last query took to complete. If a
> dataset was returned, not only the elapsed time for server execution is
> displayed, but also the time to retrieve the data from the server to the
> Data Output page."

Well, you should probably ask the pgadmin boys exactly what they are
measuring.  In any case, the Postgres server overlaps query execution
with result sending, so I don't think it's possible to get a pure
measurement of just one of those costs --- certainly not by looking at
it only from the client end.

BTW, one factor to consider is that if the test client machines weren't
all the same speed, that would have some impact on their ability to
absorb 15K records ...

            regards, tom lane


pgsql-performance by date:

From: Josh Berkus
Date:
Subject: Re: Postgres on RAID5
From: PFC
Date:
Subject: Re: Questions about 2 databases.