Subject: Re: hot standby documentation
From: Simon Riggs <simon@2ndQuadrant.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Joshua Tolley <eggyknap@gmail.com>, pgsql-docs <pgsql-docs@postgresql.org>
In-Reply-To: <AANLkTil6Hdy2eVTctpR4vsgUMgdfsfgeQfe7lEwR0j2T@mail.gmail.com>
References: <AANLkTim808CHVifufyEjt7L-PofuxmTC2HOS2LF48se1@mail.gmail.com>
	<4c20b2ed.0134e70a.19ef.5b22@mx.google.com>
	<AANLkTil6Hdy2eVTctpR4vsgUMgdfsfgeQfe7lEwR0j2T@mail.gmail.com>
Content-Type: text/plain
Date: Wed, 23 Jun 2010 19:53:54 +0100
Message-Id: <1277319234.25074.2466.camel@ebony>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Tue, 2010-06-22 at 14:24 -0400, Robert Haas wrote:

> Fixed.  See attached.

I started reading this but by chunk seven I only agree with a couple of
these changes. None of them seem hugely important changes.

I'd suggest you make a pass of copy editing that doesn't seek to alter
the meanings or add information, so we can agree without discussing each
proposed change in detail. Definitely don't remove information.

It's not impossible to believe that temp tables could be written in the
future, so I disagree with the comments there.

We could also allow SELECT ... FOR SHARE during Hot Standby, simply by
making it same as normal SELECT, without any ill effects.

-- 
 Simon Riggs           www.2ndQuadrant.com