Re: Update on true serializable techniques in MVCC

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <zb(at)cybertec(dot)at>,<robertmhaas(at)gmail(dot)com>, <laurenz(dot)albe(at)wien(dot)gv(dot)at>
Cc: <andres(at)anarazel(dot)de>,<alvherre(at)commandprompt(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Update on true serializable techniques in MVCC
Date: 2009-12-17 13:30:25
Message-ID: 4B29DE11020000250002D68E@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Albe Laurenz" wrote:
> I would say that in the case of a table scan, the whole table will
> be SILOCKed. I guess that's pretty much unavoidable if you want
> serializability.

Agreed.

-Kevin

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2009-12-17 13:38:27 Re: Hot Standby and prepared transactions
Previous Message Kevin Grittner 2009-12-17 13:26:48 Re: determine snapshot after obtaining locks for first statement