Re: Remaining Streaming Replication Open Items - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Remaining Streaming Replication Open Items
Date
Msg-id 1270728056.8305.35.camel@ebony
Whole thread Raw
In response to Re: Remaining Streaming Replication Open Items  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Remaining Streaming Replication Open Items
List pgsql-hackers
On Thu, 2010-04-08 at 07:53 -0400, Robert Haas wrote:

> > I do. I see no reason to do the latter, ever, so should not be added to
> > any TODO.
> 
> Well, stopping recovery earlier would mean fewer locks, which would
> mean a better chance for the read-only backends to finish their work
> and exit quickly.  But I'm not sure how much it's worth worrying
> about.

The purpose of the lock is to prevent access to objects when they are in
inappropriate states for access. If we stopped startup and allowed
access, how do we know that things are in sufficiently good state to
allow access? We don't. If the Startup process is holding a lock then
that is the only safe thing to do. Otherwise we might allow access to a
table with a partially built index or other screw ups.

-- Simon Riggs           www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Remaining Streaming Replication Open Items
Next
From: Robert Haas
Date:
Subject: Re: Remaining Streaming Replication Open Items