Re: determine snapshot after obtaining locks for first statement

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Markus Wanner" <markus(at)bluegap(dot)ch>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: determine snapshot after obtaining locks for first statement
Date: 2009-12-17 18:20:50
Message-ID: 4B2A2222020000250002D721@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Are we sure that's a precise and complete description? I don't
> have a problem with putting a description just like that in the
> docs, but I'm not yet convinced it's right.

Well, I thought it was when I typed it. You mentioned referencing
other columns in the updated rows; I'll test to see how that
behaves.

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2009-12-17 18:26:35 Re: COPY IN as SELECT target
Previous Message Tom Lane 2009-12-17 18:18:10 Re: determine snapshot after obtaining locks for first statement