> As far as Postgres is concerned, there's no deadlock here, only a slow client
that could be true if we used explicit locks. all our accesses are of the
form "learn everything you need to know to do the transaction, then open the
database, do it, and close". there are some really long SELECT's
"Darko Prenosil" <[EMAIL PROTECTED]> writes:
> Here is changed fe-connect.c
Could we see a "diff -c" against what you started from, rather
than trying to intuit what changes you want to make?
regards, tom lane
---(end of broadcast)
> Non-Blocking Connection is not working under WIN32 build of PGSQL interface.
> I Spend some time to make it work.
> Here is changed fe-connect.c
>
> I did not check if all of non-blocking functions are working,
> but I checked PQsetnonblocking,PQisnonblocking,
> PQsendQuery, PQgetResult and fe
