On Thu, 2010-01-07 at 16:29 +0000, Tom Lane wrote:

> Instead of that, undo the original optimizations that threw away
> QueryCancelPending anytime we were starting or finishing a command
> read, and instead discard the cancel request within ProcessInterrupts
> if we find that there is no HS reason for forcing a cancel and we are
> DoingCommandRead.

Is there a reason why we are calling DisableNotifyInterrupt() and
DisableCatchupInterrupt() before we call ProcessInterrupts() and again
within it?

-- 
 Simon Riggs           www.2ndQuadrant.com

In response to

• pgsql: Fix (some of the) breakage introduced into query-cancel at 2010-01-07 16:29:58 from Tom Lane

Responses

• Re: pgsql: Fix (some of the) breakage introduced into query-cancel at 2010-01-08 02:51:24 from Tom Lane

pgsql-committers by date

Next:	From: User Fxjr	Date: 2010-01-08 02:32:58
	Subject: npgsql - Npgsql2: [#1010746] NpgsqlDate.AddMonths(m):
Previous:	From: Takahiro Itagaki	Date: 2010-01-08 00:48:56
	Subject: pgsql: pgBufferUsage needs PGDLLIMPORT for pg_stat_statements on