Jorge Bastos wrote: > hum, perhaps Paul could upgrade that in the SQL scripts :P > Paul, please upgrade that.
You mean downgrade? I wont fix that because TYPE=InnoDB is deprecated. ENGINE= has been supported since 4.1.2 The INSTALL file for dbmail-2.1 is incorrect. mysql-4.1.3+ is very likely required already for 2.1.x, and *will* definitely be a requirement for 2.2. > > I've tried: > mysql> CREATE TABLE dbmail_headername ( id BIGINT NOT > NULL AUTO_INCREMENT, headername VARCHAR(100) NOT NULL DEFAULT > '', PRIMARY KEY (id), UNIQUE (headername) ) engine=InnoDB; > ERROR 1005 (HY000): Can't create table './postfix/dbmail_headername.frm' > (errno: 121) > > using engine instead of type but nothing > the most strange is that i can create the table with myisam and later > convert it to innodb without any error. > > > > ----- Original Message ----- From: "Andy Blackshaw" <[EMAIL PROTECTED]> > To: "Jorge Bastos" <[EMAIL PROTECTED]> > Sent: Thursday, March 30, 2006 5:47 PM > Subject: Re: [Dbmail] (no subject) > > >> When you say "doesn't work" do you get any error message (try it at the >> command prompt if necessary), or in the mysql error log? Also what >> version of mysql are you running, I think one release of the 5 series >> deprecated TYPE=, should now use ENGINE=InnoDB. >> >> For 'Best' parameters would need info about server, expected traffic >> etc. but fwiw this the innodb section I'm using on a very modest server >> (pIII 600 512MB memory) serving ~ 200 Email accounts, mostly pop3. >> Mysql version is 4.1.11 >> >> innodb_data_home_dir = /var/lib/mysql/ >> innodb_data_file_path = >> ibdata1:1000M;ibdata2:3000M;ibdata3:1000M:autoextend:max:4000M >> innodb_log_group_home_dir = /var/lib/mysql/ >> innodb_log_arch_dir = /var/lib/mysql/ >> # You can set .._buffer_pool_size up to 50 - 80 % >> # of RAM but beware of setting memory usage too high >> set-variable = innodb_buffer_pool_size=192M >> set-variable = innodb_additional_mem_pool_size=20M >> # Set .._log_file_size to 25 % of buffer pool size >> set-variable = innodb_log_file_size=33554432 >> set-variable = innodb_log_buffer_size=8M >> innodb_flush_log_at_trx_commit=1 >> set-variable = innodb_lock_wait_timeout=50 >> >> This is probably not optimum, but has evolved and works pretty well, >> database serves mydns and some web sites as well as dbmail. >> Wether you need to allow for 8GB of data (or more) depends on what >> quotas you allow your users. >> You appear to have default setup at present, maybe no my.cnf file. If >> so locate a sample my-medium.cnf or my-large.cnf which normally come >> with mysql, and modify to suit using above as a guide if useful. >> If your specify new ibdata and log parameters (different from your show >> variables output) then you will need to drop the database, and delete >> any ibdata* and possibley ib_logfile* files from your mysql data >> directory before restarting. >> >> Andy >> >> On 30 Mar 2006 at 16:13, Jorge Bastos wrote: >> >> From: "Jorge Bastos" <[EMAIL PROTECTED]> >> To: <[EMAIL PROTECTED]> >> Subject: Re: [Dbmail] (no subject) >> Date sent: Thu, 30 Mar 2006 16:13:18 +0100 >> >>> it's strange... >>> >>> CREATE TABLE dbmail_replycache ( >>> to_addr varchar(100) NOT NULL default '', >>> from_addr varchar(100) NOT NULL default '', >>> handle varchar(100) NOT NULL default '', >>> lastseen datetime NOT NULL default '0000-00-00 00:00:00', >>> UNIQUE KEY replycache_1 (to_addr,from_addr, handle) >>> ) TYPE=InnoDB; >>> >>> ----- >>> doesn't work >>> ----- >>> >>> CREATE TABLE dbmail_replycache ( >>> to_addr varchar(100) NOT NULL default '', >>> from_addr varchar(100) NOT NULL default '', >>> handle varchar(100) NOT NULL default '', >>> lastseen datetime NOT NULL default '0000-00-00 00:00:00', >>> UNIQUE KEY replycache_1 (to_addr,from_addr, handle) >>> ) TYPE=myisam; >>> >>> ----- >>> works just fine >>> ----- >>> >>> and : >>> --- >>> show variables like '%innodb%'; >>> --- >>> >>> mysql> show variables like '%innodb%'; >>> +---------------------------------+------------------------+ >>> | Variable_name | Value | >>> +---------------------------------+------------------------+ >>> | have_innodb | YES | >>> | innodb_additional_mem_pool_size | 1048576 | >>> | innodb_autoextend_increment | 8 | >>> | innodb_buffer_pool_awe_mem_mb | 0 | >>> | innodb_buffer_pool_size | 8388608 | >>> | innodb_checksums | ON | >>> | innodb_commit_concurrency | 0 | >>> | innodb_concurrency_tickets | 500 | >>> | innodb_data_file_path | ibdata1:10M:autoextend | >>> | innodb_data_home_dir | | >>> | innodb_doublewrite | ON | >>> | innodb_fast_shutdown | 1 | >>> | innodb_file_io_threads | 4 | >>> | innodb_file_per_table | OFF | >>> | innodb_flush_log_at_trx_commit | 1 | >>> | innodb_flush_method | | >>> | innodb_force_recovery | 0 | >>> | innodb_lock_wait_timeout | 50 | >>> | innodb_locks_unsafe_for_binlog | OFF | >>> | innodb_log_arch_dir | | >>> | innodb_log_archive | OFF | >>> | innodb_log_buffer_size | 1048576 | >>> | innodb_log_file_size | 5242880 | >>> | innodb_log_files_in_group | 2 | >>> | innodb_log_group_home_dir | ./ | >>> | innodb_max_dirty_pages_pct | 90 | >>> | innodb_max_purge_lag | 0 | >>> | innodb_mirrored_log_groups | 1 | >>> | innodb_open_files | 300 | >>> | innodb_support_xa | ON | >>> | innodb_sync_spin_loops | 20 | >>> | innodb_table_locks | ON | >>> | innodb_thread_concurrency | 0 | >>> | innodb_thread_sleep_delay | 10000 | >>> +---------------------------------+------------------------+ >>> >>> >>> can you help me giving the best parameters to configure this? :) >>> >>> I never worked with innodb.. >>> >>> Jorge >>> >>> >>> >>> >>> ----- Original Message ----- From: "Andy Blackshaw" <[EMAIL PROTECTED]> >>> To: "Jorge Bastos" <[EMAIL PROTECTED]> >>> Sent: Thursday, March 30, 2006 3:40 PM >>> Subject: Re: [Dbmail] (no subject) >>> >>> >>> > On 30 Mar 2006 at 12:40, Jorge Bastos wrote: >>> > >>> >> >>> >> people, sorry my question >>> >> >>> >> im trying to create the innodb tables to use dbmail 2.1.x but >>> i >> can't >>> >> create them in innodb, mysql only lets mt create them in >>> myisam, >> is >>> >> there any special reason for this? >>> >> i think this ennabled by default in mysql >>> > >>> > It depends how you got your copy installed, some distros, only install >>> > the classic i.e. no innodb, by default, and you have to get mysql-max. >>> > You can check by doing >>> > show variables like '%inno% >>> > at the mysql command prompt, you should see >>> > have_innodb | YES >>> > and a lot of other info about the innodb setup i.e. what data and log >>> > files are allocated. >>> > If you have_innodb YES but no info for e.g. >>> > innodb_data_file_path >>> > then you may need to edit your my.cnf file to enable innodb, allocate >>> > its storage and log files etc. though I think it normally uses >>> defaults >>> > for these if you have no my.cnf. >>> > >>> > Andy >>> > >>> >>> >>> >> >> >> > > _______________________________________________ > Dbmail mailing list > Dbmail@dbmail.org > https://mailman.fastxs.nl/mailman/listinfo/dbmail > -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl
