Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: 60 Seconds to connected to Postgresql using ODBC or PGAdmin
- From: Richard Broersma Jr <rabroersma(at)yahoo(dot)com>
- To: Adam M <gnuman1(at)gmail(dot)com>
- Cc: Postgresql ODBC List <pgsql-odbc(at)postgresql(dot)org>
- Subject: Re: 60 Seconds to connected to Postgresql using ODBC or PGAdmin
- Date: Wed, 28 Nov 2007 23:13:02 -0800 (PST)
- Message-id: <795968(dot)81507(dot)qm(at)web31815(dot)mail(dot)mud(dot)yahoo(dot)com>
--- On Wed, 11/28/07, Adam M <gnuman1(at)gmail(dot)com> wrote: > Whenever a connection takes that long of a time, and the > server is not > loaded like crazy, then it is most likely a reverse DNS > issue. > Sometimes a forward DNS issue. The delay is just the amount > of time > for the DNS lookup to timeout. In this case, the OP's servers is localhost. Would this indicate the DNS (foward|reverse) issue? Regards, Richard Broersma Jr.
- Follow-Ups:
- Re: 60 Seconds to connected to Postgresql using ODBC or PGAdmin
- From: Paul Lambert
- Re: 60 Seconds to connected to Postgresql using ODBC or PGAdmin
- References:
- Prev by Date: Re: 60 Seconds to connected to Postgresql using ODBC or PGAdmin
- Next by Date: Re: [GENERAL] 60 Seconds to connected to Postgresql using ODBC or PGAdmin
- Previous by thread: Re: 60 Seconds to connected to Postgresql using ODBC or PGAdmin
- Next by thread: Re: 60 Seconds to connected to Postgresql using ODBC or PGAdmin
- Indexes: