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

Re: Hot Standby on git

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hot Standby on git
Date: 2009-09-30 06:33:29
Message-ID: 4AC2FBB9.7060304@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Looking at the changes to StartupMultiXact, you're changing the locking
so that both MultiXactOffsetControlLock and MultiXactMemberControlLock
are acquire first before changing anything. Why? Looking at the other
functions in that file, all others that access both files are happy to
acquire one lock at a time, like StartupMultiXact does without the patch.

-- 
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

In response to

Responses

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2009-09-30 06:33:44
Subject: Re: Hot Standby on git
Previous:From: Rajanikant ChirmadeDate: 2009-09-30 06:03:51
Subject: Re: how to use eclipse when debugging postgreSQL backend

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