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

From Simon Riggs
Subject Re: Assertion failure on hot standby
Date
Msg-id 1290787882.2981.35.camel@ebony
Whole thread Raw
In response to Re: Assertion failure on hot standby  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Fri, 2010-11-26 at 17:53 +0200, Heikki Linnakangas wrote:
> Hmm, 
> looking at the code, we also allow RowShareLock and RowExclusiveLock
> in 
> the standby. You can't actually insert/update/delete tuples or set
> xmax 
> as SELECT FOR SHARE does on standby, though, so why do we allow that? 

It was considered sensible to allow PREPARE on DML on a standby, which
required those lock levels. Archives...

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



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Assertion failure on hot standby
Next
From: Bruce Momjian
Date:
Subject: libpq/Makefile cleanup abandoned