public inbox for [email protected]
help / color / mirror / Atom feedFrom: Robert Haas <[email protected]>
To: Simon Riggs <[email protected]>
Cc: Joshua Tolley <[email protected]>
Cc: pgsql-docs <[email protected]>
Subject: Re: hot standby documentation
Date: Wed, 23 Jun 2010 15:05:33 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <1277319234.25074.2466.camel@ebony>
References: <[email protected]>
<[email protected]>
<[email protected]>
<1277319234.25074.2466.camel@ebony>
On Wed, Jun 23, 2010 at 2:53 PM, Simon Riggs <[email protected]> wrote:
> 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.
I've actually removed very little. The current text repeats some
information or splits up related facts across different paragraphs.
> It's not impossible to believe that temp tables could be written in the
> future, so I disagree with the comments there.
The text I wrote does not say that temp tables could not be written in
the future. It simply says why they cannot be written now.
> We could also allow SELECT ... FOR SHARE during Hot Standby, simply by
> making it same as normal SELECT, without any ill effects.
True.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
view thread (8+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: hot standby documentation
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox