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-12 02:46:09 |
Message-ID: | 20131112024609.GG15562@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
On Mon, Nov 11, 2013 at 09:27:15PM -0500, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> 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.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
Attachment | Content-Type | Size |
---|---|---|
mvcc.diff | text/x-diff | 1.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | David Johnston | 2013-11-12 03:25:59 | Re: MVCC snapshot timing |
Previous Message | Tom Lane | 2013-11-12 02:27:15 | Re: MVCC snapshot timing |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2013-11-12 03:17:24 | Re: Heavily modified big table bloat even in auto vacuum is running |
Previous Message | Fabrízio de Royes Mello | 2013-11-12 02:43:43 | Re: pg_dump and pg_dumpall in real life |