List:Internals« Previous MessageNext Message »
From:Michael Widenius Date:August 20 2001 12:11pm
Subject:Re: adding INSERT support to MERGE tables
View as plain text  
Hi!

>>>>> "Sergei" == Sergei Golubchik <serg@stripped> writes:

Sergei> Hi!
Sergei> On Aug 18, Michael Widenius wrote:
>> 
Sergei> Also, INSERT_METHOD should also go to MRG file, for isam layer to know it.
>> 
>> Why?
>> It's should be enough for MySQL to know about this.

Sergei> It CAN be done that way - that is to pass INSERT_METHOD as an argument
Sergei> to mrg_write().

Sergei> But to be consistent it should be stored on isam layer - it's isam
> information,
Sergei> and MySQL shouldn't ever worry about it.

It's actually MYISAM-MERGE information and not MyISAM. 

If we define the INSERT to be a dynamic property that is always to be
sent to mrg_write(), then it's a MySQL problem.

Sergei> Also in ROUND_ROBIN it has somehow to preserve the last-target-table number
Sergei> on shutdown. This will change MRG files from simple ``ls *.MYI >
> table.MRG''
Sergei> to something more complex. In ROUND_ROBIN they also won't be read-only.
>> 
>> Sorry, but I didn't get that.

Sergei> Well, suppose you have three tables in MERGE, and INSERT_METHOD=ROUND_ROBIN
Sergei> First insert goes to the first table, the second one - to the second.
Sergei> Now one does ``mysql.server stop; mysql.server start'' - or simply mysqld
Sergei> dies and safe_mysqld restarts it. I would prefer the first insert after
> restart
Sergei> to go to the third table.

I don't think that Benjamin is planing a round_robin.
I actually don't think this would be very useful extension anyway.
(One can't even do this to speed up inserts as the table locks on
the MERGE file would interfere with this).
If one needs things like this, then it's better to use a hardware
raid.

Regards,
Monty
Thread
adding INSERT support to MERGE tablesBenjamin Pflugmann17 Aug
  • Re: adding INSERT support to MERGE tablesSergei Golubchik17 Aug
    • Re: adding INSERT support to MERGE tablesMichael Widenius17 Aug
      • Re: adding INSERT support to MERGE tablesBenjamin Pflugmann30 Aug
        • Re: adding INSERT support to MERGE tablesSergei Golubchik30 Aug
          • Re: adding INSERT support to MERGE tablesBenjamin Pflugmann30 Aug
        • Re: adding INSERT support to MERGE tablesMichael Widenius30 Aug
          • Re: adding INSERT support to MERGE tablesBenjamin Pflugmann30 Aug
            • Re: adding INSERT support to MERGE tablesMichael Widenius1 Sep
              • Re: adding INSERT support to MERGE tablesBenjamin Pflugmann5 Sep
                • Re: adding INSERT support to MERGE tablesMichael Widenius6 Sep
                  • Re: adding INSERT support to MERGE tablesBenjamin Pflugmann10 Sep
                    • Re: adding INSERT support to MERGE tablesBenjamin Pflugmann11 Sep
                      • Re: adding INSERT support to MERGE tablesMichael Widenius12 Sep
                        • Re: adding INSERT support to MERGE tablesBenjamin Pflugmann12 Sep
                          • Re: adding INSERT support to MERGE tablesMichael Widenius13 Sep
                            • Re: adding INSERT support to MERGE tablesBenjamin Pflugmann18 Sep
                      • Re: adding INSERT support to MERGE tablesMichael Widenius22 Sep
                      • Re: adding INSERT support to MERGE tablesMichael Widenius24 Sep
                        • Re: adding INSERT support to MERGE tablesBenjamin Pflugmann27 Sep
    • Re: adding INSERT support to MERGE tablesSergei Golubchik17 Aug
      • Re: adding INSERT support to MERGE tablesBenjamin Pflugmann17 Aug
      • Re: adding INSERT support to MERGE tablesMichael Widenius18 Aug
        • Re: adding INSERT support to MERGE tablesSergei Golubchik18 Aug
          • Re: adding INSERT support to MERGE tablesMichael Widenius20 Aug
RE: adding INSERT support to MERGE tablesThe Tilghman20 Aug