List:Commits« Previous MessageNext Message »
From:Ann W. Harrison Date:October 23 2008 9:41pm
Subject:Re: bzr commit into mysql-6.0-falcon-team branch (vvaintroub:2875)
Bug#38186, Bug#39789
View as plain text  
Vlad,

> 
> Keep in mind, that all possible tablespaces are created in memory and on
> disk during pass1() or in Tablespace::boostrap(). They are never deleted 
> until REDO phase comes. REDO does not recreate Tablespaces - why should it,
> they are already present after the pass1.

That's not what I would expect.  All possible tablespaces should
be tracked in memory during pass1, but only the ones that will
survive at the end should ever be created.  The other should be
marked as old instantiations, and all actions on them should be
skipped after pass1.


> IF they are not present during pass1 or pass2, we ultimately suck during in
> recovery on IO::read().

What is IO::read() reading?


Best,

Ann
> 
>
Thread
bzr commit into mysql-6.0-falcon-team branch (vvaintroub:2875) Bug#38186,Bug#39789Vladislav Vaintroub21 Oct
RE: bzr commit into mysql-6.0-falcon-team branch (vvaintroub:2875)Bug#38186, Bug#39789Vladislav Vaintroub23 Oct
RE: bzr commit into mysql-6.0-falcon-team branch (vvaintroub:2875)Bug#38186, Bug#39789Vladislav Vaintroub23 Oct
  • Re: bzr commit into mysql-6.0-falcon-team branch (vvaintroub:2875)Bug#38186, Bug#39789Ann W. Harrison23 Oct
    • RE: bzr commit into mysql-6.0-falcon-team branch (vvaintroub:2875)Bug#38186, Bug#39789Vladislav Vaintroub24 Oct
      • Re: bzr commit into mysql-6.0-falcon-team branch (vvaintroub:2875)Bug#38186, Bug#39789Jim Starkey24 Oct
        • RE: bzr commit into mysql-6.0-falcon-team branch (vvaintroub:2875)Bug#38186, Bug#39789Vladislav Vaintroub24 Oct
          • Re: bzr commit into mysql-6.0-falcon-team branch (vvaintroub:2875)Bug#38186, Bug#39789Jim Starkey26 Oct
RE: bzr commit into mysql-6.0-falcon-team branch (vvaintroub:2875)Bug#38186, Bug#39789Vladislav Vaintroub24 Oct