Re: COPY insert performance
От | Jeff Trout |
---|---|
Тема | Re: COPY insert performance |
Дата | |
Msg-id | 795D0AC7-3C39-4CE3-A105-921F35BAC8DF@torgo.978.org обсуждение исходный текст |
Ответ на | Re: COPY insert performance ("Chris Isaacson" <cisaacson@tradebotsystems.com>) |
Список | pgsql-performance |
On Jul 26, 2005, at 8:15 AM, Chris Isaacson wrote: > > I am using InnoDB with MySQL which appears to enforce true transaction > support. (http://dev.mysql.com/doc/mysql/en/innodb-overview.html) If > not, how is InnoDB "cheating"? > are you sure your tables are innodb? chances are high unless you explcitly stated "type = innodb" when creating that they are myisam. look at "show table status" output to verify. > > I've played with the checkpoint_segments. I noticed an enormous > improvement increasing from the default to 40, but neglible > improvement > thereafter. Do you have a recommendation for a value? there's been a thread on -hackers recently about checkpoint issues.. in a nut shell there isn't much to do. But I'd say give bizgres a try if you're going to be continually loading huge amounts of data. -- Jeff Trout <jeff@jefftrout.com> http://www.jefftrout.com/ http://www.stuarthamm.net/
В списке pgsql-performance по дате отправления: