Re: mvcc.sgml make up

From: Volkan YAZICI <volkan(dot)yazici(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: mvcc.sgml make up
Date: 2005-12-05 20:56:52
Message-ID: 7104a7370512051256x77f49d25ye2fa0332791a42b9@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

On 12/5/05, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> SELECT * FROM foo WHERE col > 4;
> SELECT * FROM foo WHERE col > 5;

Ofcourse two different SELECT queries are (probably) gonna return
different results. If this is the point you want to underline in the
documentation, just rip that sentence off.

From the documentation:
«Notice that two successive SELECT commands can see different data,
even though they are within a single transaction, if other transactions
commit changes during execution of the first SELECT.»
It's not interesting to see "two different SELECT queries" will return
different results. As I understand from the above statement, the point
in here is that the "same SELECT queries" may return different results
too.

Anyway, this what I understand from documentation. I just tried to
clarify the argument. If most of you think this just confuses more and
wrong, than just ignore the patch.

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2005-12-05 21:10:09 Re: mvcc.sgml make up
Previous Message Tom Lane 2005-12-05 20:37:19 Re: [PATCHES] snprintf() argument reordering not working