From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sudheer H R <sudheer.hr@tekenlight.com>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Socket (fd) to posters server getting closed. (libpq)
In-reply-to: <B84343DA-1078-444D-B259-A2C7C3CC6242@tekenlight.com>
References: <B84343DA-1078-444D-B259-A2C7C3CC6242@tekenlight.com>
Comments: In-reply-to Sudheer H R <sudheer.hr@tekenlight.com>
	message dated "Sun, 27 Jun 2021 19:32:06 +0530"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <3175543.1624803158.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 27 Jun 2021 10:12:38 -0400
Message-ID: <3175544.1624803158@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3175544.1624803158%40sss.pgh.pa.us>
Precedence: bulk

Sudheer H R <sudheer.hr@tekenlight.com> writes:
> I am writing a piece of software to connect to the Postgres database in =
the asynchronous manner and have used PQconnectStartParams, PQsendPrepare,=
 PQFlush , etc=E2=80=A6 in conjunction with libev.

> The established connection is used for a transaction, and then added to =
a pool of connections, and then subsequently retrieved from the pool for r=
euse.

> I notice that the retrieved connection has the socket fd closed, which l=
eads to an error o the nature:  could not receive data from server: Bad fi=
le descriptor

libpq itself will assuredly never close a socket that's associated with
an open connection.  You need to look elsewhere for the cause.

			regards, tom lane