List:Internals« Previous MessageNext Message »
From:Marko Mäkelä Date:June 20 2007 3:30pm
Subject:Re: CREATE INDEX is not committed?
View as plain text  
On Wed, Jun 20, 2007 at 06:11:39PM +0500, Ramil Kalimullin wrote:
> Hi Marko, Guilhem!
> 
> Thanks for pointing at the problem.
> Is there a bug report filed (nice to have it recorded)?

Not that I know.  The bug can't be repeated on stock mysqld (only with
our internal branch that implements ha_innobase::add_index()).  I hope
that it isn't a problem.

> I'll attend to the issue tomorrow.

I'll keep track on this after my summer vacation (June 22 - July 31).

	Marko
Thread
CREATE INDEX is not committed?Marko Mäkelä13 Jun
  • Re: CREATE INDEX is not committed?Guilhem Bichot13 Jun
    • Re: CREATE INDEX is not committed?Marko Mäkelä13 Jun
      • Re: CREATE INDEX is not committed?Guilhem Bichot13 Jun
        • Re: CREATE INDEX is not committed?Marko Mäkelä18 Jun
          • Re: CREATE INDEX is not committed?Marko Mäkelä18 Jun
            • Re: CREATE INDEX is not committed?Guilhem Bichot18 Jun
              • Re: CREATE INDEX is not committed?Marko Mäkelä20 Jun
                • Re: CREATE INDEX is not committed?Ramil Kalimullin20 Jun
                  • Re: CREATE INDEX is not committed?Marko Mäkelä20 Jun
          • Re: CREATE INDEX is not committed?Guilhem Bichot18 Jun
Re: CREATE INDEX is not committed?Marko Mäkelä21 Jun
  • Smart ALTER TABLE dropping non-existing tmp table (Re: CREATEINDEX is not committed?)Marko Mäkelä13 Aug