| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | "PostgreSQL Bugs List" <pgsql-bugs(at)postgresql(dot)org> |
| Cc: | al(dot)an(at)sitvallee(dot)it |
| Subject: | Re: BUG #1088: Name resolution connecting to a database |
| Date: | 2004-03-02 15:39:40 |
| Message-ID: | 200403021539.40468.dev@archonet.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tuesday 02 March 2004 14:09, PostgreSQL Bugs List wrote:
> The following bug has been logged online:
>
> Bug reference: 1088
> Logged by: Antonino Albanese
> Email address: al(dot)an(at)sitvallee(dot)it
> Description: Name resolution connecting to a database
> trying to connect to the server with domain name
> takes long time, here an example:
> nino(at)server:~$ time psql -h server -d newtestdb -U download -c '\q'
>
> real 0m10.151s
> user 0m0.010s
> sys 0m0.000s
This looks like a problem in your DNS setup rather than PostgreSQL - the 10
minutes is a timeout. Possibly with reverse lookup. You may see similar
problems with a mailserver if you are running one (and mailserver lists are a
good place to search too).
You may want to investigate /etc/resolv.conf on both machines as well as the
dig/host commands. Don't forget it could be a problem with server A lookup up
server B or vice versa.
HTH
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Bohmer | 2004-03-02 16:22:56 | backend crash with certain statements/tables |
| Previous Message | Tom Lane | 2004-03-02 15:28:53 | Re: BUG #1088: Name resolution connecting to a database |