| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: MVCC snapshot timing |
| Date: | 2013-11-12 01:59:35 |
| Message-ID: | 20331.1384221575@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Mon, Nov 11, 2013 at 03:39:45PM -0500, Tom Lane wrote:
>> I'm not really seeing the point of s/transaction/session/ here.
> 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.
We take at least one snapshot per transaction, in any mode. Referring
to sessions makes it even further away from being a useful concept.
> Would you prefer I refer to statements, e.g.:
'Statement' might work.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-11-12 02:19:54 | Re: MVCC snapshot timing |
| Previous Message | Bruce Momjian | 2013-11-11 20:58:33 | Re: MVCC snapshot timing |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-11-12 02:13:48 | Re: Clang 3.3 Analyzer Results |
| Previous Message | Andrew Dunstan | 2013-11-12 00:15:36 | Re: pg_dump and pg_dumpall in real life |