Re: Assertion failure on hot standby - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Assertion failure on hot standby
Date
Msg-id 1290852339.2981.1022.camel@ebony
Whole thread Raw
In response to Re: Assertion failure on hot standby  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, 2010-11-26 at 18:35 -0500, Tom Lane wrote:
> Speaking of which, is there any code in there to ensure that a
> deadlock
> in the standby is resolved by killing HS queries and not the replay
> process?  Because deadlocks are certainly going to be possible no
> matter
> what. 

Locks cause query conflicts, so any attempt to take a lock that is
blocked will be resolved before a deadlock takes place. So that
situation does not arise in the startup process. 

-- Simon Riggs           http://www.2ndQuadrant.com/books/PostgreSQL Development, 24x7 Support, Training and Services



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: ToDo: enhanced diagnostic for plpgsql
Next
From: Quan Zongliang
Date:
Subject: Patch BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory