Re: Hot Standby on git - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Hot Standby on git
Date
Msg-id 4ACF77E7.6040603@enterprisedb.com
Whole thread Raw
In response to Re: Hot Standby on git  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs wrote:
>> Tom Lane wrote:
>>> [ scratches head ... ]  Why is hot standby messing with this sort of
>>> thing at all?  It sounds like a performance optimization that should
>>> be considered separately, and *later*.
>> Yeah, I too considered just ripping it out. Simon is worried that
>> locking all the lock partitions and scanning the locks table can take a
>> long time. We do that in the master, while holding both ProcArrayLock
>> and XidGenLock in exclusive mode (hmm, why is shared not enough?), so
>> there is some grounds for worry. OTOH, it's only done once per checkpoint.
> 
> I could live with ripping it out, but what we have now doesn't make
> sense, to me.

Ok, let's just rip it out for now.

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


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Hot Standby on git
Next
From: Robert Haas
Date:
Subject: Re: Hot Standby 0.2.1