postgresql and sockets

[Krzysztof Duleba]

Corinna Vinschen wrote:

> > However, `psql -h localhost -p 5432' succeeds. So in fact the socket
is
> > still there, but the link stored in /tmp/.s.PGSQL.5432 is broken.
>
> That's rather unlikely.  Could you show us an strace of the above
failing
> psql call?  Perhaps there's some interesting information in there.
>
>
> Corinna

There are 3 cases, so I attach 3 straces.

str1 is the case when `psql' failed.

str2 is the case for `psql -h localhost -p 5432'. psql goes directly for
the socket here.

str3 is a clean strace for `psql', just after restarting postgresql
service.

Regards
Krzysztof Duleba
-------------- next part --------------
A non-text attachment was scrubbed...
Name: str1
Type: application/octet-stream
Size: 27410 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20050503/89e44c10/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: str2
Type: application/octet-stream
Size: 43260 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20050503/89e44c10/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: str3
Type: application/octet-stream
Size: 39262 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20050503/89e44c10/attachment-0002.obj>
-------------- next part --------------
--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/