You should run the select query from the psql utility to determine if
it's PostgreSQL, or your OleDb driver that's being slow. It takes like
185ms on one of my tables to get 7000 rows.
Greg Quinn wrote:
>> how many rows does it return ? a few, or a lot ?
>
> 3000 Rows - 7 seconds - very slow
>
> Which client library may have a problem? I am using OleDb, though
> haven't tried the .NET connector yet.
>
> Network configuration?? I am running it off my home PC with no network.
> It is P4 2.4 with 1 Gig Ram. Windows XP
>
> ----- Original Message ----- From: "PFC" <lists@peufeu.com>
> To: "Greg Quinn" <greg@officium.co.za>
> Sent: Wednesday, March 29, 2006 11:02 AM
> Subject: Re: [PERFORM] Slow performance on Windows .NET and OleDb
>
>
>>
>>> select * from users
>>> which returns 4 varchar fields, there is no where clause
>>
>> how many rows does it return ? a few, or a lot ?
>>
>>> Yes, I am running the default postgres config. Basically I have been
>>> a MySQL user and thought I would like to check out PostGreSql.
>>
>> Good idea...
>>
>> From the tests I made, on simple queries like yours, with no joins,
>> speed pf pg 8.x is about the same as mysql 5.x ; that is to say very
>> fast. If you have a performance problem on something so basic, and
>> moreover on windows, it smells like a problem in the client library,
>> or in the TCP transport between client and server.
>> I remember messages saying postgres on windows was slow some time ago
>> here, and it turned out to be a problem in the network configuration
>> of the machine.
>>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
--
Christopher Kings-Lynne
Technical Manager
CalorieKing
Tel: +618.9389.8777
Fax: +618.9389.8444
chris.kings-lynne@calorieking.com
www.calorieking.com