From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: MVCC snapshot timing |
Date: | 2013-11-11 20:58:33 |
Message-ID: | 20131111205833.GC15562@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
On Mon, Nov 11, 2013 at 03:39:45PM -0500, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> 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 <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-11-12 01:59:35 | Re: MVCC snapshot timing |
Previous Message | Tom Lane | 2013-11-11 20:39:45 | Re: MVCC snapshot timing |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2013-11-11 21:00:59 | Re: alter_table regression test problem |
Previous Message | Tom Lane | 2013-11-11 20:50:19 | Re: subquery q2 does not have attribute 0 |