[MTOS-dev] Making MT Transaction Safe

[Alvar Freude]

Hi,

-- Hirotaka Ogawa <hirotaka.ogawa at gmail.com> wrote:

> At almost every invocations, MT::App touches the same row of mt_blog
> table, and then rebuilds files, and finally commits.  In such case, I
> think, other threads are blocked until the previous commit finished.

hmmm, something in mt_blog gets *updated*?
All columns look to me to be read only while rebuilding.

I looked in a SQL log of a complete rebuild (small test blog): the only 
updates are two (!) updates of mt_session and session_start is updated.


And usually the session MUST be locked during a request, otherwise there 
may be a lot of problems (and therefore e.g. Apache::Session::Postgres 
makes a SELECT ... FOR UPDATE). MT does only a simple select, this might 
result in broken session data.

For long running queries there might be another session handling with no 
blocking.


Ciao
  Alvar

-- 
** Alvar C.H. Freude, http://alvar.a-blast.org/
** http://www.assoziations-blaster.de/
** http://www.wen-waehlen.de/
** http://odem.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
Url : http://www.sixapart.com/pipermail/mtos-dev/attachments/20080313/0d0f2679/attachment.bin