public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Tom Lane <[email protected]>
Cc: PostgreSQL-documentation <[email protected]>
Subject: Re: MVCC snapshot timing
Date: Wed, 13 Nov 2013 10:14:19 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>

On Mon, Nov 11, 2013 at 09:46:09PM -0500, Bruce Momjian wrote:
> On Mon, Nov 11, 2013 at 09:27:15PM -0500, Tom Lane wrote:
> > Bruce Momjian <[email protected]> writes:
> > > On Mon, Nov 11, 2013 at 08:59:35PM -0500, Tom Lane wrote:
> > >> 'Statement' might work.
> > 
> > > OK, updated patch attached.  Is "statement" too vague here?  SQL
> > > statement?  query?
> > 
> > "SQL statement" might be a good idea in the first sentence, but
> > I don't think you need to repeat it in the second.
> > 
> > What's bothering me about this wording is that you're talking about
> > statements and then suddenly reference transactions (as being "those
> > other things messing with your data").  This seems weirdly asymmetric,
> > since after all you could equally well be the one messing with their
> > data.
> 
> Yes, that bugged me too, but then I realized that you only see the
> changes from a transaction when it completes, not from each statement,
> e.g. you can never see changes between statements of a multi-statement
> transaction.
> 
> I used "SQL statement" in the updated, attached patch.

Applied.

-- 
  Bruce Momjian  <[email protected]>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +


-- 
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

view thread (17+ 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]
  Subject: Re: MVCC snapshot timing
  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