From: | Reid Thompson <Reid(dot)Thompson(at)ateb(dot)com> |
---|---|
To: | Filip Rembiałkowski <plk(dot)zuber(at)gmail(dot)com> |
Cc: | Paul Shapley <p(dot)shapley(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Cannot connect to server |
Date: | 2008-09-05 11:48:02 |
Message-ID: | 1220615282.16258.21.camel@raker.ateb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 2008-09-05 at 11:44 +0200, Filip Rembiałkowski wrote:
>
> is the server running (see process list, ps ax | grep postgres)
> does the socket file exist? (see filesystem, ls -l /tmp/.s.PGSQL.5432)
Since you say things work for several days, then stop -- make sure
there's no braindead automated cleanup of /tmp that is
removing /tmp/.s.PGSQL.5432
>
> it's possible that the client tries to connect via non-existing
> socket. it happens when server config is different from compiled-in
> defaults for socket location.
>
> in this case try to connect via TCP, this should help
From | Date | Subject | |
---|---|---|---|
Next Message | Aaron Burnett | 2008-09-05 13:16:41 | large inserts and fsync |
Previous Message | Magnus Hagander | 2008-09-05 11:10:44 | Re: max_stack_depth Exceeded |