Thread: 60 Seconds to connected to Postgresql using ODBC or PGAdmin

--- On Wed, 11/28/07, Finn Lassen <dcio@AxiomInt.com> wrote:

Can anyone else comment on what problems could be causing these slow connections problems?


> Meanwhile, I don't understand why it now takes exactly
> 60 seconds to connect to the database whether I use pgAdmin or my
> connection string from within VB.

This is very odd.  Since you are having a problem with your connection time on both pgAdmin(which doesn't use ODBC to
connect)and ODBC connects, I would assume that you must be having an issue that is non-odbc related.   

> I thought I had seen a comment about this somewhere, but can't find it
> now. I've tried changing Connection Pooling in the OBDC Data Source
> Administrator for the PostgreSQL ANSI driver, but doesn't have any
> effect (or maybe just reloading the server configuration is not enough?

If this were an ODBC connection Issue, i would first make sure that all of ODBC logging was disabled on your client
computer. ODBC logging can really kill performance. 

The windows ODBC tracing is found in the ODBC Datasource Administrator form -> tracing -> [Stop tracing now] & [Stop
VisualStudio Analyzer now]. 

I guess it is impossible for postgresql ODBC logging to be taking place since you using a DNSless connection and have
setany parameters to start the logging. 

If all of the logging is already off, try turning turning on the Myloging and CommLogin by setting the appropriate
settingin your DNS-less connection string.  If you post these logs, It will help others on the ODBC mailing list to
troubleshoot where your problem is coming from. 

Also on a side note, it is important to remember that many of the subscribers to the Postgresql mailing list are
bombardedwith countless emails on a daily basis.   

Do to the voluminous amount of emails, I am pretty sure that most subscribers pick and choose which emails they will
readpurely based on the interest generated by the email's subject heading.   

So to help encourage more subscribes to participate, it is important to make your subject headings very specific (to
thepoint) and to make them as eye catching as possible.  You'll notice that I've alter your email subject a bit.
Hopefullyit will help get a few more people to join in on this thread. 

There is nothing wrong with tackling a very difficult but general problem with postgresql by sending seperate emails
withdifferent subject heading the specifically address only the individual facets of the overall problem.  Different
peoplewill probably respond to different facets of your overall problem. 

Regarding the test case I sent to you, how many columns should I try to create in a table in order to reproduce the
problemyou where having with needing OIDs created in your tables? 

Regards,
Richard Broersma Jr.

Richard Broersma Jr wrote:
> --- On Wed, 11/28/07, Finn Lassen <dcio@AxiomInt.com> wrote:
>
> Can anyone else comment on what problems could be causing these slow connections problems?
>
>
>> Meanwhile, I don't understand why it now takes exactly
>> 60 seconds to connect to the database whether I use pgAdmin or my
>> connection string from within VB.

Name lookups. Something is trying to look up a name, failing and it's
timing out after 60 seconds.

Could be DNS, or WINS (or whatever MS' current name resolution system is
called). It could be either end of the connection too, if for example
something on the server is logging the names of connecting clients.

Try a couple of name lookups (forward and reverse) from each end and see
what happens.

--
   Richard Huxton
   Archonet Ltd

--- On Wed, 11/28/07, Richard Huxton <dev@archonet.com> wrote:
> Name lookups. Something is trying to look up a name,
> failing and it's
> timing out after 60 seconds.

It seems the OP's connection string was set to localhost.  Would this still indicate a Name Loopup problem?

Regards,
Richard

Richard Broersma Jr wrote:

> It seems the OP's connection string was set to localhost.  Would this still indicate a Name Loopup problem?
>

Do you have some some firewall running ? Also is there a localhost entry
in your hosts file(e.g /etc/hosts or C:/windows/system32/drivers/etc) ?

Peter

Richard Broersma Jr wrote:
> --- On Wed, 11/28/07, Richard Huxton <dev@archonet.com> wrote:
>> Name lookups. Something is trying to look up a name, failing and
>> it's timing out after 60 seconds.
>
> It seems the OP's connection string was set to localhost.  Would this
> still indicate a Name Loopup problem?

That would make it unlikely.

The only other option that occurs to me would be some firewall type of
package that's taking a long time to allow a connection. It would be an
odd bit of security software that timed out and then *allowed* the
connection to proceed.

Hmm - it looks like the wireshark network sniffer is available for
Windows (http://www.wireshark.org/) - I'd be tempted to install that and
connect to an external IP and see what packets go where. That will save
a lot of head-scratching.

--
   Richard Huxton
   Archonet Ltd

Richard Broersma Jr wrote:
> --- On Wed, 11/28/07, Richard Huxton <dev@archonet.com> wrote:
>> Name lookups. Something is trying to look up a name,
>> failing and it's
>> timing out after 60 seconds.
>
> It seems the OP's connection string was set to localhost.  Would this still indicate a Name Loopup problem?
>

If there is no entry (or an incorrect one) in /etc/hosts for localhost -
then yes - try to connect to 127.0.0.1 and see if that makes a difference.

Also if it is set to do namelookup before referring to /etc/hosts it can
have similar probs.


--

Shane Ambler
pgSQL@Sheeky.Biz

Get Sheeky @ http://Sheeky.Biz