>> If you look at the "actual time" it's completing very quickly indeed.
>> - it must be something to do with either:
>> 1. Fetching/formatting
> the data
>>> 2. Transferring the data to the client.
> I do agree.
> happens if you only select half the rows? Does the time to run the
>> select halve?
> Yes, it does.
> Using pgAdmin, the time to get all 36
> rows is about 67500ms while it's 24235ms to get only 18 rows.
Hmm - I've seen reports about the traffic-shaping module not being
install/activated making large data transfers slow. That was on Windows
2000 though. Might be worth searching the mail archives - I'm afraid I
run PG on Linux mostly, so can't say for sure.
One other thing I'd test. Make a small table with text columns of the
same size and see how fast it is to select from that. If it's just as
slow then it's your network setup. If it's much faster then it's
something to do with the bytea type.
In response to
pgsql-performance by date
|Next:||From: Gauri Kanekar||Date: 2007-02-26 11:49:05|
|Subject: Query Planner|
|Previous:||From: firstname.lastname@example.org||Date: 2007-02-26 05:44:06|
|Subject: invalid page header in block 428 of relation "pg_attribute"|