Skip site navigation (1) Skip section navigation (2)

Hot Standby and query cancel

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, Joachim Wieland <joe(at)mcknight(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Hot Standby and query cancel
Date: 2010-01-13 18:24:22
Message-ID: 1263407062.26654.11505.camel@ebony (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
We've been chewing around query cancel on Hot Standby and I think things
have got fairly confusing, hence a new thread.

I enclose a patch that includes all the things that we all agree on so
far, in my understanding

* Recovery conflict processing uses SIGUSR1 rather than shmem per Tom, 
while holding ProcArrayLock per Andres

* CONFLICT_MODE_ERROR throws ERROR when in a transaction, not idle and
not in subtransaction, otherwise becomes CONFLICT_MODE_FATAL per Tom and
other discussion

* Recovery abort message has additional detail, per Heikki

It doesn't include anything still under discussion, though is intended
as a base upon which further patches can progress independently.

* Infrastructure for supercancel, by Joachim Wieland

* Any of the many further ideas by Andres Freund

Please review this so we can move onto taking other issues one by one.
This is also a base for other HS work I need to complete.

I am still testing patch, so should be confident to commit tomorrow
barring issues.

 Simon Riggs 

Attachment: hs_cancel.2010_Jan_13.patch
Description: text/x-patch (22.0 KB)


pgsql-hackers by date

Next:From: Tom LaneDate: 2010-01-13 18:34:41
Subject: Re: [PATCH] remove redundant ownership checks
Previous:From: Tom LaneDate: 2010-01-13 18:21:21
Subject: Re: pg_dump sort order for functions

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group