pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Slow performance on Windows .NET and OleDb
19+ messages / 12 participants
[nested] [flat]

* Slow performance on Windows .NET and OleDb
@ 2006-03-28 12:14  Greg Quinn <greg@officium.co.za>
  0 siblings, 2 replies; 19+ messages in thread

From: Greg Quinn @ 2006-03-28 12:14 UTC (permalink / raw)
  To: pgsql-performance

Hello,

I have just installed PostGreSql 8.1 on my Windows XP PC. I created a simple 
table called users with 4 varchar fields.

I am using the OleDb connection driver. In my .NET application, I populate 
3000 records into the table to test PostGreSql's speed. It takes about 3-4 
seconds.

Even worse is displaying the 3000 records in a ListView control. It takes 
about 7 seconds. In MySQL, the exact same table and application displays the 
same 3000 records in under 1/2 second!!!

Why is PostGreSql so slow compared to MySQL? What do you recommend I do to 
speed up? It is such a simple query and small database. 





^ permalink  raw  reply  [nested|flat] 19+ messages in thread

* Re: Slow performance on Windows .NET and OleDb
@ 2006-03-28 14:10  Merlin Moncure <mmoncure@gmail.com>
  parent: Greg Quinn <greg@officium.co.za>
  1 sibling, 0 replies; 19+ messages in thread

From: Merlin Moncure @ 2006-03-28 14:10 UTC (permalink / raw)
  To: Greg Quinn <greg@officium.co.za>; +Cc: pgsql-performance

On 3/28/06, Greg Quinn <greg@officium.co.za> wrote:
> I am using the OleDb connection driver. In my .NET application, I populate
> 3000 records into the table to test PostGreSql's speed. It takes about 3-4
> seconds.

have you tried:
1. npgsql .net data provider
2. odbc ado.net bridge

merlin



^ permalink  raw  reply  [nested|flat] 19+ messages in thread

* Re: Slow performance on Windows .NET and OleDb
@ 2006-03-28 17:32  Jim C. Nasby <jnasby@pervasive.com>
  parent: Greg Quinn <greg@officium.co.za>
  1 sibling, 1 reply; 19+ messages in thread

From: Jim C. Nasby @ 2006-03-28 17:32 UTC (permalink / raw)
  To: Greg Quinn <greg@officium.co.za>; +Cc: pgsql-performance

On Tue, Mar 28, 2006 at 02:14:00PM +0200, Greg Quinn wrote:
> Hello,
> 
> I have just installed PostGreSql 8.1 on my Windows XP PC. I created a 
> simple table called users with 4 varchar fields.
> 
> I am using the OleDb connection driver. In my .NET application, I populate 
> 3000 records into the table to test PostGreSql's speed. It takes about 3-4 
> seconds.
> 
> Even worse is displaying the 3000 records in a ListView control. It takes 
> about 7 seconds. In MySQL, the exact same table and application displays 
> the same 3000 records in under 1/2 second!!!

Have you vacuumed recently? This smells like it might be a table bloat
problem.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



^ permalink  raw  reply  [nested|flat] 19+ messages in thread

* Re: Slow performance on Windows .NET and OleDb
@ 2006-03-28 17:52  Joshua D. Drake <jd@commandprompt.com>
  parent: Jim C. Nasby <jnasby@pervasive.com>
  0 siblings, 2 replies; 19+ messages in thread

From: Joshua D. Drake @ 2006-03-28 17:52 UTC (permalink / raw)
  To: Jim C. Nasby <jnasby@pervasive.com>; +Cc: Greg Quinn <greg@officium.co.za>; pgsql-performance

Jim C. Nasby wrote:
> On Tue, Mar 28, 2006 at 02:14:00PM +0200, Greg Quinn wrote:
>> Hello,
>>
>> I have just installed PostGreSql 8.1 on my Windows XP PC. I created a 
>> simple table called users with 4 varchar fields.
>>
>> I am using the OleDb connection driver. In my .NET application, I populate 
>> 3000 records into the table to test PostGreSql's speed. It takes about 3-4 
>> seconds.
>>
>> Even worse is displaying the 3000 records in a ListView control. It takes 
>> about 7 seconds. In MySQL, the exact same table and application displays 
>> the same 3000 records in under 1/2 second!!!
> 
> Have you vacuumed recently? This smells like it might be a table bloat
> problem.


This could be a lot of things...

He is probably running the default postgresql.conf which is going to 
perform horribly.

What is your work_mem? shared_buffers?

Are you passing a where clause? If so is there an index on the field 
that is subject to the clause?

When you do the population, is it via inserts or copy?

Joshua D. Drake


-- 

             === The PostgreSQL Company: Command Prompt, Inc. ===
       Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
       Providing the most comprehensive  PostgreSQL solutions since 1997
                      http://www.commandprompt.com/





^ permalink  raw  reply  [nested|flat] 19+ messages in thread

* Re: Slow performance on Windows .NET and OleDb
@ 2006-03-29 06:22  Greg Quinn <greg@officium.co.za>
  parent: Joshua D. Drake <jd@commandprompt.com>
  1 sibling, 2 replies; 19+ messages in thread

From: Greg Quinn @ 2006-03-29 06:22 UTC (permalink / raw)
  To: pgsql-performance

The query is,

select * from users

which returns 4 varchar fields, there is no where clause

Yes, I am running the default postgres config. Basically I have been a MySQL 
user and thought I would like to check out PostGreSql. So I did a quick 
performance test. The performance was so different that I thought PostGreSQL 
was nothing compared to MySQL, but now it seems its just a few configuration 
options. Strange how the defult config would be so slow...

I have begun reading the documentation but am not too sure what options I 
can quickly tweak to get good performance, could somebody give me some tips?

Thanks


----- Original Message ----- 
From: "Joshua D. Drake" <jd@commandprompt.com>
To: "Jim C. Nasby" <jnasby@pervasive.com>
Cc: "Greg Quinn" <greg@officium.co.za>; <pgsql-performance@postgresql.org>
Sent: Tuesday, March 28, 2006 7:52 PM
Subject: Re: [PERFORM] Slow performance on Windows .NET and OleDb


> Jim C. Nasby wrote:
>> On Tue, Mar 28, 2006 at 02:14:00PM +0200, Greg Quinn wrote:
>>> Hello,
>>>
>>> I have just installed PostGreSql 8.1 on my Windows XP PC. I created a 
>>> simple table called users with 4 varchar fields.
>>>
>>> I am using the OleDb connection driver. In my .NET application, I 
>>> populate 3000 records into the table to test PostGreSql's speed. It 
>>> takes about 3-4 seconds.
>>>
>>> Even worse is displaying the 3000 records in a ListView control. It 
>>> takes about 7 seconds. In MySQL, the exact same table and application 
>>> displays the same 3000 records in under 1/2 second!!!
>>
>> Have you vacuumed recently? This smells like it might be a table bloat
>> problem.
>
>
> This could be a lot of things...
>
> He is probably running the default postgresql.conf which is going to 
> perform horribly.
>
> What is your work_mem? shared_buffers?
>
> Are you passing a where clause? If so is there an index on the field that 
> is subject to the clause?
>
> When you do the population, is it via inserts or copy?
>
> Joshua D. Drake
>
>
> -- 
>
>             === The PostgreSQL Company: Command Prompt, Inc. ===
>       Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
>       Providing the most comprehensive  PostgreSQL solutions since 1997
>                      http://www.commandprompt.com/
>
> 





^ permalink  raw  reply  [nested|flat] 19+ messages in thread

* Re: Slow performance on Windows .NET and OleDb
@ 2006-03-29 06:24  Greg Quinn <greg@officium.co.za>
  parent: Joshua D. Drake <jd@commandprompt.com>
  1 sibling, 1 reply; 19+ messages in thread

From: Greg Quinn @ 2006-03-29 06:24 UTC (permalink / raw)
  To: pgsql-performance

Via insert

> 
> When you do the population, is it via inserts or copy?
> 
> Joshua D. Drake
> 
> 
> -- 
> 
>             === The PostgreSQL Company: Command Prompt, Inc. ===
>       Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
>       Providing the most comprehensive  PostgreSQL solutions since 1997
>                      http://www.commandprompt.com/
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>       choose an index scan if your joining column's datatypes do not
>       match
>




^ permalink  raw  reply  [nested|flat] 19+ messages in thread

* Re: Slow performance on Windows .NET and OleDb
@ 2006-03-29 06:58  Ruben Rubio Rey <ruben@rentalia.com>
  parent: Greg Quinn <greg@officium.co.za>
  1 sibling, 1 reply; 19+ messages in thread

From: Ruben Rubio Rey @ 2006-03-29 06:58 UTC (permalink / raw)
  To: pgsql-performance

Greg Quinn wrote:

> The query is,
>
> select * from users
>
> which returns 4 varchar fields, there is no where clause
>
> Yes, I am running the default postgres config. Basically I have been a 
> MySQL user and thought I would like to check out PostGreSql. So I did 
> a quick performance test. The performance was so different that I 
> thought PostGreSQL was nothing compared to MySQL, but now it seems its 
> just a few configuration options. Strange how the defult config would 
> be so slow...

My english is poor but im gonna try to explain it:

Default configuration in postgres its not for good performance, its just 
design to make it working in any computer. Thats why u have to try to 
custom default config file.

Anyway, people says that mysql is faster (and lighter) than postgres (at 
least with mysql 3.x vs postgres 7.4), but postgres is more advanced and 
its much harder to get data corrupted.

But there is something that you should known about postgres. Postgres 
creates statistics of usage, and when you "vacumm", it optimizes each 
table depending of usage.

So:
 - You should custom config file.
 - You should vacumm it, as someone recomended before.
 - Do u have any indexes? Remove it. To get all rows you do not need it
 
Note that I just have use it under Linux, i have no idea about how 
should it work on Windows.





^ permalink  raw  reply  [nested|flat] 19+ messages in thread

* Re: Slow performance on Windows .NET and OleDb
@ 2006-03-29 07:16  Chris <dmagick@gmail.com>
  parent: Ruben Rubio Rey <ruben@rentalia.com>
  0 siblings, 0 replies; 19+ messages in thread

From: Chris @ 2006-03-29 07:16 UTC (permalink / raw)
  To: Ruben Rubio Rey <ruben@rentalia.com>; +Cc: pgsql-performance

Ruben Rubio Rey wrote:
> Greg Quinn wrote:
> 
>> The query is,
>>
>> select * from users
>>
>> which returns 4 varchar fields, there is no where clause
>>
>> Yes, I am running the default postgres config. Basically I have been a 
>> MySQL user and thought I would like to check out PostGreSql. So I did 
>> a quick performance test. The performance was so different that I 
>> thought PostGreSQL was nothing compared to MySQL, but now it seems its 
>> just a few configuration options. Strange how the defult config would 
>> be so slow...

> - Do u have any indexes? Remove it. To get all rows you do not need it

I wouldn't do that. Postgres needs indexing just like any other database.

It might affect this query but it's not going to help other queries.

-- 
Postgresql & php tutorials
http://www.designmagick.com/



^ permalink  raw  reply  [nested|flat] 19+ messages in thread

* Re: Slow performance on Windows .NET and OleDb
@ 2006-03-29 11:00  Greg Quinn <greg@officium.co.za>
  parent: Greg Quinn <greg@officium.co.za>
  1 sibling, 3 replies; 19+ messages in thread

From: Greg Quinn @ 2006-03-29 11:00 UTC (permalink / raw)
  To: pgsql-performance

> 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.
> 





^ permalink  raw  reply  [nested|flat] 19+ messages in thread

* Re: Slow performance on Windows .NET and OleDb
@ 2006-03-29 11:21  Markus Schaber <schabi@logix-tt.com>
  parent: Greg Quinn <greg@officium.co.za>
  0 siblings, 0 replies; 19+ messages in thread

From: Markus Schaber @ 2006-03-29 11:21 UTC (permalink / raw)
  To: Greg Quinn <greg@officium.co.za>; +Cc: pgsql-performance

Hi, Greg,

Greg Quinn wrote:
>>> I populate 3000 records into the table to test PostGreSql's speed.
>>> It takes about 3-4 seconds.
>> When you do the population, is it via inserts or copy?
> Via insert

Are those inserts encapsulated into a single transaction? If not, that's
the reason why it's so slow, every transaction sync()s through to the disk.

Markus

-- 
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf.     | Software Development GIS

Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org



^ permalink  raw  reply  [nested|flat] 19+ messages in thread

* Re: Slow performance on Windows .NET and OleDb
@ 2006-03-29 11:40  PFC <lists@peufeu.com>
  parent: Greg Quinn <greg@officium.co.za>
  2 siblings, 0 replies; 19+ messages in thread

From: PFC @ 2006-03-29 11:40 UTC (permalink / raw)
  To: Greg Quinn <greg@officium.co.za>; pgsql-performance


> 3000 Rows - 7 seconds - very slow

	On my PC (athlon 64 3000+ running Linux), selecting 3000 rows with 4  
columns out of a 29 column table takes about 105 ms, including time to  
transfer the results and convert them to native Python objects. It takes  
about 85 ms on a test table with only those 4 columns.

	There is definitely a problem somewhere on your system.

	I'd suggest running this query in an infinite loop. Logically, it should  
use 100% processor, with postgres using some percentage (30% here) and  
your client using some other percentage (70% here). Is your processor used  
to the max ?



^ permalink  raw  reply  [nested|flat] 19+ messages in thread

* Re: Slow performance on Windows .NET and OleDb
@ 2006-03-29 14:05  Merlin Moncure <mmoncure@gmail.com>
  parent: Greg Quinn <greg@officium.co.za>
  2 siblings, 0 replies; 19+ messages in thread

From: Merlin Moncure @ 2006-03-29 14:05 UTC (permalink / raw)
  To: Greg Quinn <greg@officium.co.za>; +Cc: pgsql-performance

On 3/29/06, Greg Quinn <greg@officium.co.za> 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.


esilo=# create temp table use_npgsql as select v, 12345 as a, 'abcdef'
as b, 'abcdef' as c, 4 as d from generate_series(1,100000) v;

SELECT
Time: 203.000 ms
esilo=# explain analyze select * from use_npgsql;
                                                    QUERY PLAN
-------------------------------------------------------------------------------------------------------------------
 Seq Scan on use_npgsql  (cost=0.00..1451.16 rows=61716 width=76)
(actual time=0.007..176.106 rows=100000 loops=1)
 Total runtime: 336.809 ms
(2 rows)

I just pulled out 100k rows in about 1/3 second.    The problem is not
your postgresql configuration.  Your problem is possibly in the oledb
driver.  The last time I looked at it, it was not production ready.

http://pgfoundry.org/frs/?group_id=1000140&release_id=407

Merlin



^ permalink  raw  reply  [nested|flat] 19+ messages in thread

* Re: Slow performance on Windows .NET and OleDb
@ 2006-03-30 01:21  Christopher Kings-Lynne <chris.kings-lynne@calorieking.com>
  parent: Greg Quinn <greg@officium.co.za>
  2 siblings, 1 reply; 19+ messages in thread

From: Christopher Kings-Lynne @ 2006-03-30 01:21 UTC (permalink / raw)
  To: Greg Quinn <greg@officium.co.za>; +Cc: pgsql-performance

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




^ permalink  raw  reply  [nested|flat] 19+ messages in thread

* [Solved] Slow performance on Windows .NET and OleDb
@ 2006-03-30 05:57  Greg Quinn <greg@officium.co.za>
  parent: Christopher Kings-Lynne <chris.kings-lynne@calorieking.com>
  0 siblings, 1 reply; 19+ messages in thread

From: Greg Quinn @ 2006-03-30 05:57 UTC (permalink / raw)
  To: pgsql-performance

This problem was caused by the OleDb driver. I used a 3rd party .NET 
provider and it worked, 8000 rows in just over 100ms!

Can somebody send me a sample connection string for the PostGreSql native 
.net driver please? I'm battling to find a valid connection string.

Thanks





^ permalink  raw  reply  [nested|flat] 19+ messages in thread

* Re: [Solved] Slow performance on Windows .NET and OleDb
@ 2006-03-30 14:34  Dave Dutcher <dave@tridecap.com>
  parent: Greg Quinn <greg@officium.co.za>
  0 siblings, 1 reply; 19+ messages in thread

From: Dave Dutcher @ 2006-03-30 14:34 UTC (permalink / raw)
  To: 'Greg Quinn' <greg@officium.co.za>; pgsql-performance

I use Npgsql, and the connection string I use is real simple:

Server=192.168.0.36;Database=mydb;User Id=myuserid;Password=123456

Hope that helps,

Dave

> -----Original Message-----
> From: pgsql-performance-owner@postgresql.org
[mailto:pgsql-performance-
> owner@postgresql.org] On Behalf Of Greg Quinn
> Sent: Wednesday, March 29, 2006 11:57 PM
> To: pgsql-performance@postgresql.org
> Subject: [PERFORM] [Solved] Slow performance on Windows .NET and OleDb
> 
> This problem was caused by the OleDb driver. I used a 3rd party .NET
> provider and it worked, 8000 rows in just over 100ms!
> 
> Can somebody send me a sample connection string for the PostGreSql
native
> .net driver please? I'm battling to find a valid connection string.
> 
> Thanks
> 
> 
> 
> ---------------------------(end of
broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>        subscribe-nomail command to majordomo@postgresql.org so that
your
>        message can get through to the mailing list cleanly




^ permalink  raw  reply  [nested|flat] 19+ messages in thread

* Re: [Solved] Slow performance on Windows .NET and OleDb
@ 2006-03-31 20:49  Antoine <melser.anton@gmail.com>
  parent: Dave Dutcher <dave@tridecap.com>
  0 siblings, 0 replies; 19+ messages in thread

From: Antoine @ 2006-03-31 20:49 UTC (permalink / raw)
  To: Dave Dutcher <dave@tridecap.com>; +Cc: Greg Quinn <greg@officium.co.za>; pgsql-performance

This is a blatant thread steal... but here we go...
Do people have any opinions on the pgsql driver? How does it compare
with the odbc in terms of performance? Is it fully production ready?
The boss wants to go .net (instead of Java, which is my preference...)
- will I have to spend my time defending postgres against
mysql/postgres/sqlserver?
Cheers
Antoine
ps. I try my best not to steal threads but sometimes... :-)

On 30/03/06, Dave Dutcher <dave@tridecap.com> wrote:
> I use Npgsql, and the connection string I use is real simple:
>
> Server=192.168.0.36;Database=mydb;User Id=myuserid;Password=123456
>
> Hope that helps,
>
> Dave
>
> > -----Original Message-----
> > From: pgsql-performance-owner@postgresql.org
> [mailto:pgsql-performance-
> > owner@postgresql.org] On Behalf Of Greg Quinn
> > Sent: Wednesday, March 29, 2006 11:57 PM
> > To: pgsql-performance@postgresql.org
> > Subject: [PERFORM] [Solved] Slow performance on Windows .NET and OleDb
> >
> > This problem was caused by the OleDb driver. I used a 3rd party .NET
> > provider and it worked, 8000 rows in just over 100ms!
> >
> > Can somebody send me a sample connection string for the PostGreSql
> native
> > .net driver please? I'm battling to find a valid connection string.
> >
> > Thanks
> >
> >
> >
> > ---------------------------(end of
> broadcast)---------------------------
> > TIP 1: if posting/reading through Usenet, please send an appropriate
> >        subscribe-nomail command to majordomo@postgresql.org so that
> your
> >        message can get through to the mailing list cleanly
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>


--
This is where I should put some witty comment.



^ permalink  raw  reply  [nested|flat] 19+ messages in thread

* Re: [Solved] Slow performance on Windows .NET and OleDb
@ 2006-03-31 23:27  Magnus Hagander <mha@sollentuna.net>
  0 siblings, 2 replies; 19+ messages in thread

From: Magnus Hagander @ 2006-03-31 23:27 UTC (permalink / raw)
  To: Antoine <melser.anton@gmail.com>; Dave Dutcher <dave@tridecap.com>; +Cc: Greg Quinn <greg@officium.co.za>; pgsql-performance

> This is a blatant thread steal... but here we go...
> Do people have any opinions on the pgsql driver?

It's very nice.

> How does it compare with the odbc in terms of performance?

I haven't measured specifically, but if you're tlaking .net it should be
better. It's all in managed code, so you won't pay the repeated penalty
of switching down to unmanaged and back all the time (the
.net-ODBC-bridge is known not to be very fast). As a bonus your program
will run in an environment where the CAS policy prevents native code. 
And I've never had any performance problems with it myself.


> Is it fully production ready?

I beleive so. I've been using it for a long time with zero problems.
While I don't use many of the exotic features in it, I doubt most people
do ;-) Don't get scared by the claim it's in beta - IIRC there's an RC
out any day now, and it's been stable long before 1.0. But it's always a
good idea to browse through the list of known bugs and see if one will
likely hit you...


//Magnus



^ permalink  raw  reply  [nested|flat] 19+ messages in thread

* Re: [Solved] Slow performance on Windows .NET and OleDb
@ 2006-04-01 09:54  Antoine <melser.anton@gmail.com>
  parent: Magnus Hagander <mha@sollentuna.net>
  1 sibling, 0 replies; 19+ messages in thread

From: Antoine @ 2006-04-01 09:54 UTC (permalink / raw)
  To: Magnus Hagander <mha@sollentuna.net>; +Cc: Dave Dutcher <dave@tridecap.com>; Greg Quinn <greg@officium.co.za>; pgsql-performance

On 01/04/06, Magnus Hagander <mha@sollentuna.net> wrote:
> > This is a blatant thread steal... but here we go...
> > Do people have any opinions on the pgsql driver?
>
> It's very nice.
...

Thanks for the tips - i'll try a couple of test apps soon.
Cheers
Antoine




--
This is where I should put some witty comment.



^ permalink  raw  reply  [nested|flat] 19+ messages in thread

* Re: [Solved] Slow performance on Windows .NET and OleDb
@ 2006-04-01 19:23  Merlin Moncure <mmoncure@gmail.com>
  parent: Magnus Hagander <mha@sollentuna.net>
  1 sibling, 0 replies; 19+ messages in thread

From: Merlin Moncure @ 2006-04-01 19:23 UTC (permalink / raw)
  To: Magnus Hagander <mha@sollentuna.net>; +Cc: Antoine <melser.anton@gmail.com>; Dave Dutcher <dave@tridecap.com>; Greg Quinn <greg@officium.co.za>; pgsql-performance

On 3/31/06, Magnus Hagander <mha@sollentuna.net> wrote:
> > This is a blatant thread steal... but here we go...
> > Do people have any opinions on the pgsql driver?

> I beleive so. I've been using it for a long time with zero problems.
> While I don't use many of the exotic features in it, I doubt most people
> do ;-) Don't get scared by the claim it's in beta - IIRC there's an RC
> out any day now, and it's been stable long before 1.0. But it's always a
> good idea to browse through the list of known bugs and see if one will
> likely hit you...

Up until a few months ago the npgsql driver was missing a few features
that made it easier to work with typed datasets in the IDE...I would
use the odbc driver to create the dataset at design time and work with
it at run time with the npgsql driver.

Lately though, it seems there is no reason not use the npgsql driver.

Merlin



^ permalink  raw  reply  [nested|flat] 19+ messages in thread


end of thread, other threads:[~2006-04-01 19:23 UTC | newest]

Thread overview: 19+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-03-28 12:14 Slow performance on Windows .NET and OleDb Greg Quinn <greg@officium.co.za>
2006-03-28 14:10 ` Merlin Moncure <mmoncure@gmail.com>
2006-03-28 17:32 ` Jim C. Nasby <jnasby@pervasive.com>
2006-03-28 17:52   ` Joshua D. Drake <jd@commandprompt.com>
2006-03-29 06:22     ` Greg Quinn <greg@officium.co.za>
2006-03-29 06:58       ` Ruben Rubio Rey <ruben@rentalia.com>
2006-03-29 07:16         ` Chris <dmagick@gmail.com>
2006-03-29 11:00       ` Greg Quinn <greg@officium.co.za>
2006-03-29 11:40         ` PFC <lists@peufeu.com>
2006-03-29 14:05         ` Merlin Moncure <mmoncure@gmail.com>
2006-03-30 01:21         ` Christopher Kings-Lynne <chris.kings-lynne@calorieking.com>
2006-03-30 05:57           ` Greg Quinn <greg@officium.co.za>
2006-03-30 14:34             ` Dave Dutcher <dave@tridecap.com>
2006-03-31 20:49               ` Antoine <melser.anton@gmail.com>
2006-03-29 06:24     ` Greg Quinn <greg@officium.co.za>
2006-03-29 11:21       ` Markus Schaber <schabi@logix-tt.com>
2006-03-31 23:27 Re: [Solved] Slow performance on Windows .NET and OleDb Magnus Hagander <mha@sollentuna.net>
2006-04-01 09:54 ` Antoine <melser.anton@gmail.com>
2006-04-01 19:23 ` Merlin Moncure <mmoncure@gmail.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox