Resetting libpq connections after an app error - Mailing list pgsql-hackers

From Daniele Varrazzo
Subject Resetting libpq connections after an app error
Date
Msg-id CA+mi_8Y6UZE9e__4BN0BoAODxE_-P_QHDZH7OLiyP0rQ415Mgg@mail.gmail.com
Whole thread Raw
Responses Re: Resetting libpq connections after an app error
List pgsql-hackers
Hello,

apologize for bumping the question to -hackers but I got no answer
from -general. If there is a better ML to post it let me know.

In a libpq application, if there is an application error between
PQsendQuery and PQgetResult, is there a way to revert a connection
back to an usable state (i.e. from transaction status ACTIVE to IDLE)
without using the network in a blocking way? We are currently doing
   while (NULL != (res = PQgetResult(conn->pgconn))) {       PQclear(res);   }

but this is blocking, and if the error had been caused by the network
down, we'll just get stuck in a poll() waiting for a timeout.

Thank you very much.

-- Daniele


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Restrict ALTER FUNCTION CALLED ON NULL INPUT (was Re: Not quite a security hole: CREATE LANGUAGE for non-superusers)
Next
From: Alvaro Herrera
Date:
Subject: Re: CHECK NO INHERIT syntax