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

Re: Hot Standby: Caches and Locks

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hot Standby: Caches and Locks
Date: 2008-10-30 10:13:22
Message-ID: 1225361602.3971.371.camel@ebony.2ndQuadrant (view raw or whole thread)
Lists: pgsql-hackers
On Tue, 2008-10-21 at 15:06 +0100, Simon Riggs wrote:

> We can't augment the commit/abort messages because
> we must cater for non-transactional invalidations also, plus commit
> xlrecs are already complex enough. So we log invalidations prior to
> commit, queue them and then trigger the send at commit (if it
> happens).

Augmenting the commit messages seems like the better approach. It allows
invalidation messages to be fired as they are read off the xlrec. Still
need the additional message type to handle nontransactional
invalidation. There are other messages possibly more complex than this

 Simon Riggs 
 PostgreSQL Training, Services and Support

In response to


pgsql-hackers by date

Next:From: Zdenek KotalaDate: 2008-10-30 10:39:45
Subject: Question about GetAttributeByNum(Name) ExecQual.c
Previous:From: Simon RiggsDate: 2008-10-30 10:04:57
Subject: Re: Updating FSM on recovery

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