Hi,
> I am facing the following problem.
>
> Our application sends a block of queries to postgres in a begin end
> block. If one of the queries take a long time to finish the whole
> transaction is assumed to be committed by the application even though
> the query is still running . This results in failure of all subsequent
> transactions.
>
> Although the application is programmed to catch all exceptions , it
> somehow is not able to figure out that the transaction is still not
> complete.
I may be missing something, but it seems to me that the problem
is your application wrongly assuming that queries taking a long
time to finish are assumed to be already committed?
--
Guillaume Cottenceau
