Skip site navigation (1) Skip section navigation (2)

Re: Weird behaviour on Solaris: recv() returns ENOENT

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Forest Wilkinson <lyris-pg(at)tibit(dot)com>
Cc: pgsql-interfaces(at)postgresql(dot)org, dfs(at)roaringpenguin(dot)com
Subject: Re: Weird behaviour on Solaris: recv() returns ENOENT
Date: 2003-06-27 03:57:54
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
Forest Wilkinson <lyris-pg(at)tibit(dot)com> writes:
> I'm having a similar problem, but instead of ENOENT I'm getting what
> appears to be ECONNREFUSED.  (PQresultStatus() says "Connection
> refused".)  This is on a Solaris 9 box, with Postgres 7.3.2 and 7.3.3,
> using libpq in a multithreaded program.  At the same time, postgres

libpq is not as thread-safe as the documentation alleges :-(.  The
library itself doesn't do anything un-thread-safe, but it calls several
libc routines that are not thread-safe on many platforms.  We are trying
to fix this for 7.4.

I am not certain that this is the explanation for your problems though.
IIRC, most of the known gotchas occur during connection startup, and
would not explain a failure in a running connection.

Are you both honoring the restriction that two threads can't
concurrently do operations on the same PGconn object?  We provide
no locking that would make that safe, but consider it the application's
responsibility to do so if needed.  I strongly suspect that David's
problem is of this ilk, less sure about Forest's.

			regards, tom lane

In response to

pgsql-interfaces by date

Next:From: David F. SkollDate: 2003-06-27 12:46:30
Subject: Re: Weird behaviour on Solaris: recv() returns ENOENT
Previous:From: Philip YarraDate: 2003-06-27 02:31:24
Subject: Re: ECPG thread success (kind of) on Linux

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group