Re: pgsql: Fix (some of the) breakage introduced into query-cancel - Mailing list pgsql-committers

From Simon Riggs
Subject Re: pgsql: Fix (some of the) breakage introduced into query-cancel
Date
Msg-id 1262916686.19367.96522.camel@ebony
Whole thread Raw
In response to pgsql: Fix (some of the) breakage introduced into query-cancel  (tgl@postgresql.org (Tom Lane))
Responses Re: pgsql: Fix (some of the) breakage introduced into query-cancel
List pgsql-committers
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


pgsql-committers by date:

Previous
From: itagaki@postgresql.org (Takahiro Itagaki)
Date:
Subject: pgsql: pgBufferUsage needs PGDLLIMPORT for pg_stat_statements on
Next
From: fxjr@pgfoundry.org (User Fxjr)
Date:
Subject: npgsql - Npgsql2: [#1010746] NpgsqlDate.AddMonths(m):