public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Tom Lane <[email protected]>
Cc: PostgreSQL-documentation <[email protected]>
Subject: Re: MVCC snapshot timing
Date: Mon, 11 Nov 2013 15:58:33 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>
On Mon, Nov 11, 2013 at 03:39:45PM -0500, Tom Lane wrote:
> Bruce Momjian <[email protected]> writes:
> > I received a private email report that our introductory MVCC
> > documentation is unclear about when a snapshot is taken. I have
> > adjusted the wording in the attached patch to be less precise about
> > snapshot timing. Snapshot timing is controlled by the session isolation
> > level, which I don't think we want to cover in this introductory
> > paragraph.
>
> I'm not really seeing the point of s/transaction/session/ here.
> The phrasing is a bit awkward and maybe could be improved, but I think you
> should keep it referring to transactions.
Well, the problem with the original wording is that we don't take a new
snapshot for every transaction in the default read-committed mode.
Would you prefer I refer to statements, e.g.:
This means that while querying a database each statement sees
This is our default behavior.
--
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