From: | Lukas Kahwe Smith <smith(at)pooteeweet(dot)org> |
---|---|
To: | Greg Smith <gsmith(at)gregsmith(dot)com> |
Subject: | Re: L |
Date: | 2007-08-14 08:03:36 |
Message-ID: | 46C161D8.4070903@pooteeweet.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-www |
Greg Smith wrote:
> On Mon, 13 Aug 2007, Lukas Kahwe Smith wrote:
>
>> in the current version of your document you only talk about key
>> buffers, but these will not affect all storage engines! I am not a DB
>> tuning expert, so this should be double checked.
>
> The way I read their documentation, that tunable works the same way for
> all the storage engines. If that's not the case, that's a mistake in
> the MySQL documentation I link to. I'll put a note about it if you can
> find evidence otherwise.
http://www.databasejournal.com/features/mysql/article.php/3367871
"While the key_buffer_size is the variable to target for MyISAM tables,
for InnoDB tables, it is innodb_buffer_pool_size."
Obviously key_buffer_size does affect all storage engines, since MyISAM
is the core internal storage engine used for MySQL internals.
> That "implicit commit" stuff is good to know, will add a pointer to that
> next time I'm touching the document. It goes along with the general
> theme of sloppy implementation I've been weaving in that document.
Actually very few RDBMS support transactional DDL, though right this
second I do not remember what they do in case you issue DDL inside a
transaction. I would assume/hope that they give you an error and not do
an implicit commit.
regards,
Lukas
From | Date | Subject | |
---|---|---|---|
Next Message | Luke Lonergan | 2007-08-14 08:10:45 | Re: L |
Previous Message | Markus Schiltknecht | 2007-08-14 07:06:47 | Re: DBA-Village Poll |
From | Date | Subject | |
---|---|---|---|
Next Message | Luke Lonergan | 2007-08-14 08:10:45 | Re: L |
Previous Message | Dave Page | 2007-08-14 06:37:28 | Re: Features list |