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 -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
