Re: Hot Standby: Caches and Locks

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 www.2ndQuadrant.com
PostgreSQL Training, Services and Support