Re: timeout implementation issues

On Sat, 30 Mar 2002, Tom Lane wrote:

> Au contraire, it is not assuming anything.  It is sending off a cancel
> request and then waiting to see what happens.  Maybe the query will be
> canceled, or maybe it will complete normally, or maybe it will fail
> because of some error unrelated to the cancel request.  In any case the
> backend *will* eventually report completion/error status, and the
> frontend does not assume anything until it gets that report.

Ah, okay; this was not my understanding. I'll look at the code again.

> Why does it need to know that?  When it gets the error report back, it
> can notice that the error says "Query aborted by timeout" (or however we
> phrase it) ... but I'm not seeing why it should care.

I just meant it needed to know that the process had stopped prematurely; I
didn't mean it needed to know why.

I'll get back to you after doing a little more research.

j