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-31 23:12:17
Message-ID: 1225494737.3971.633.camel@ebony.2ndQuadrant (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Thu, 2008-10-30 at 10:13 +0000, Simon Riggs wrote:
> 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
> already.

Just a quick note to say that this approach has worked fine and I now
have both cache invalidation and locking working correctly.

Rather than submit something now in an unseemly rush I'll tidy up and
add it onto the list tomorrow after some tidy up.

 Simon Riggs 
 PostgreSQL Training, Services and Support

In response to

pgsql-hackers by date

Next:From: Gianni CiolliDate: 2008-11-01 00:01:54
Subject: Bitmap Indexes patch (was Re: Bitmap Indexes: requestfor feedback)
Previous:From: Simon RiggsDate: 2008-10-31 21:48:05
Subject: Re: Please make sure your patches are on the wiki page

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