Re: Hot Standy introduced problem with query cancel behavior - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Hot Standy introduced problem with query cancel behavior
Date
Msg-id 1262883690.19367.85877.camel@ebony
Whole thread Raw
In response to Re: Hot Standy introduced problem with query cancel behavior  (Joachim Wieland <joe@mcknight.de>)
Responses Re: Hot Standy introduced problem with query cancel behavior  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 2010-01-07 at 14:45 +0100, Joachim Wieland wrote:

> @Simon: Is there a reason why you have not yet removed recoveryConflictMode
> from PGPROC?

Unfortunately we still need a mechanism to mark which backends have been
cancelled already. Transaction state for virtual transactions isn't
visible on the procarray, so we need something there to indicate that a
backend has been sent a conflict. Otherwise we'd end up waiting for it
endlessly. The name will be changing though.

-- Simon Riggs           www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: Devrim GÜNDÜZ
Date:
Subject: Re: Streaming replication and postmaster signaling
Next
From: "David E. Wheeler"
Date:
Subject: Re: Testing with concurrent sessions