Re: Query optimization problem

Richard Huxton wrote:
> Peter wrote:
>>
>> Query returned successfully with no result in 600 ms.
>>
>> Why SELECT takes 3+ second to execute? Is it something to do with my
>> Postgres server optimization, or PgAdmin does not show correct data
>> retrieval runtime (leaks over into query runtime or something)?
>
> Data transfer and display time usually.
>
> Try SELECT count(*) FROM ... instead and see if the times are closer.
>

The display time in pgAdmin 1.6 and above is negligible (ie.
microseconds). That's why it no longer shows 2 times as previous
versions did.

Regards, Dave.