| From: | Chester Kustarz <chester(at)arbor(dot)net> |
|---|---|
| To: | "Owens, Steve" <Steve(dot)Owens(at)xerox(dot)com> |
| Cc: | psql-general(at)postgresql(dot)org, "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Odd problem in 7.4.2? |
| Date: | 2004-09-02 18:11:38 |
| Message-ID: | Pine.BSO.4.44.0409021408480.23931-100000@detroit.arbor.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 2 Sep 2004, Owens, Steve wrote:
> Since PostgreSQL is configured by default to run only on Unix sockets,
> moving the machine shouldn't cause the server to fail to run, right?
> What am I missing?
You don't specify how it is failing to start up (hang, crash, etc.), but
I have seen before when "localhost" was not in hosts file that postgresql
hung for 5 minutes during startup while DNS resolution timed out. This
was due to the way one of the local sockets was bound. After waiting
for the timeout (30 second timeout with 6 retries) then postgres would
come up. It may have been the stats collector socket (UDP) that was the
culprit IIRC.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John DeSoi | 2004-09-02 18:29:23 | Re: stand-alone psql |
| Previous Message | operationsengineer1 | 2004-09-02 17:47:42 | Re: pgAccess via ssh? |