public inbox for [email protected]  

help / color / mirror / Atom feed

From: 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:14:41 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<1277319234.25074.2466.camel@ebony>
	<[email protected]>

On Wed, Jun 23, 2010 at 3:05 PM, Robert Haas <[email protected]> wrote:
>> We could also allow SELECT ... FOR SHARE during Hot Standby, simply by
>> making it same as normal SELECT, without any ill effects.
>
> True.

Actually, wait a minute.  Why wouldn't we need to lock the tuples on
the standby just as we do on the primary?  Sure, there can't be
another user transaction modifying those tuples, but WAL replay could
still modify them.

Anyhow, I think that's beside the point.  The documentation just says
what Hot Standby does, not what it might do in a future release.  And
I don't think this patch changes that very much at all.

-- 
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