Re: AW: AW: BLERe: AW: AW: relation ### modified while in use

From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
To: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: AW: AW: BLERe: AW: AW: relation ### modified while in use
Date: 2000-10-25 15:01:16
Message-ID: 3.0.5.32.20001026010116.028b6660@mail.rhyme.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 09:36 25/10/00 +0200, Zeugswetter Andreas SB wrote:
>
>> I have not followed the entire thread, but if you are in a serializable OR
>> repeatable-read transaction,
>
>Serializable and repeatable read are the same thing, different wording.

Not last time I looked. RR ensures that rows you have seen will still
return the same data, but allows a reexecuted cursor to return more rows.
Serializable means cursors always return expected data the second time they
are executed.

>> I would think that read-only statements will
>> need to keep some kind of lock on the rows they read (or the table).
>
>Yes, we were talking about the other isolation levels. Most,
>but not all of my mails in this thread state this difference.

The bit that worried me was that most emails only referred to serializable,
not RR (which they should have, I think).

----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2000-10-25 15:02:17 RE: Re: [INTERFACES] RE: JDBC now needs updates for lar ge objects
Previous Message Magnus Hagander 2000-10-25 14:58:02 RE: Bogus-looking SSL code in postmaster wait loop