| 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: | 2007-11-29 07:13:02 |
| Message-ID: | 795968.81507.qm@web31815.mail.mud.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-odbc |
--- 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2007-11-29 07:38:15 | Re: 60 Seconds to connected to Postgresql using ODBC or PGAdmin |
| Previous Message | Adam M | 2007-11-29 07:08:49 | Re: 60 Seconds to connected to Postgresql using ODBC or PGAdmin |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2007-11-29 07:38:15 | Re: 60 Seconds to connected to Postgresql using ODBC or PGAdmin |
| Previous Message | Adam M | 2007-11-29 07:08:49 | Re: 60 Seconds to connected to Postgresql using ODBC or PGAdmin |