[Mono-list] Data access delay using Npgsql

Reilly, Andrew Andrew.Reilly@luht.scot.nhs.uk
Mon, 16 Aug 2004 17:22:26 +0100

Hi Francisco,

Thanks for responding. I'm already passing the IP address directly so there
shouldn't be any name resolution issues.

Best wishes,


-----Original Message-----
From: Francisco Figueiredo Jr. [mailto:fxjrlists@yahoo.com.br]
Sent: 12 August 2004 00:21
To: Reilly, Andrew
Cc: mono-list@lists.ximian.com
Subject: Re: [Mono-list] Data access delay using Npgsql

Reilly, Andrew wrote:
> Hi all,

Hi Reilly.

> I've been experimenting with accessing a PostgreSQL database using Npgsql,
> but have come across a problem.
> Whenever I open a new NpgsqlConnection under the MS .NET runtime there is
> always a short delay of a few seconds, presumably while the client
> authenticates with the server. However, when the same program is run under
> mono the delay is almost imperceptible. This is frustrating because I tend
> to develop under VS.NET then distribute using mono.
> I'm running mono 1.0.1 with Npgsql 0.6 and the server is PostgreSQL 7.4.3.
> I've tried turning on logging support in Npgsql but it doesn't report
> anything relevant: the log starts from when the connection is actually
> established any everything works quickly after that. I've also tried
> relaxing the authentication settings of the database but this has no
> Does anyone have any suggestions as to what the cause of the problem might
> be?

Are you using the machine name as the address of server?
I received some reports about that only in ms.net as you said. I still 
didn't find why it would be doing this delay. I some time noticed that 
name resolution with ms.net took some time.
Please, try passing the ip address and let me know if you still have the 


Francisco Figueiredo Jr.

The information contained in this message may be confidential or legally privileged and is intended for the addressee only, If you have received this message in error or there are any problems please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden.