This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: postgresql and sockets
On May 3 22:12, Krzysztof Duleba wrote:
> Corinna Vinschen wrote:
>
> > I have the strange feeling that the file isn't recognized as socket
> > anymore for some reason. When you called `cat /tmp/.s.PGSQL.5432',
> > did you use Cygwin's cat? If the file would have been recognized as
> > socket, you shouldn't have been able to read the content of the file.
> > The correct result would have been:
> >
> > $ cat /tmp/.s.PGSQL.5432
> > cat: /tmp/.s.PGSQL.5432: No such device or address
>
> I used Cygwin's cat. The output above is what I get too when postgresql is
> restarted.
>
> > So I'm wondering if something happened before the call to psql, so that
> > the file has been... well, "downgraded" to a normal file instead of a
> > socket file. Socket files have the system attribute set, for instance.
> > If you remove this, the file is not recognized as socket file anymore.
>
> I sent another email that didn't make it to the list somehow. The point
> was that the socket file breaks after some time (about 10 minutes) no
> matter if it was used at all. So I might as well restart postgres, wait 10
> minutes, and it will be broken.
>
> In the meantime this line will appear in the postgresql's log:
>
> WARNING: dup(0) failed after 3195 successes: Bad file descriptor
>
> I'm not sure if it has anything to do.
Hmm, there's no good reason for that, except if the number of open sockets
or the number of sockets in the TIME_WAIT state is hitting a system limit.
Normal dup2 on the socket works fine for me.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader mailto:cygwin@cygwin.com
Red Hat, Inc.
--
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/