Re: What can we learn from MySQL?
От | Matthew T. O'Connor |
---|---|
Тема | Re: What can we learn from MySQL? |
Дата | |
Msg-id | 58232.192.154.91.225.1082725121.squirrel@192.154.91.225 обсуждение исходный текст |
Ответ на | Re: What can we learn from MySQL? (Fabien COELHO <coelho@cri.ensmp.fr>) |
Ответы |
Re: What can we learn from MySQL?
Re: What can we learn from MySQL? |
Список | pgsql-hackers |
> There are two issues here : ease-of-use for admin and basic users. > > On for former point, admin ease-of-use, A little story a few month ago. > > I succeeded in advising production people here to switch some applications > from a mysql database, which was working perfectly, to a postgres > database. A few weeks later, the performances were desastrous. 30 seconds > to get an answer to a simple select on a 1500 entries tables. After > investigation, the problems were: > > - no vacuum, although there were daily "DELETE FROM tables;" > to empty all the data and reload from another source. > > - no analyze, because the admin did not know about it. My goal is to have pg_autovacuum integrated into the backend for 7.5. I don't know if it will default to being turned on or off, I'm sure that will be a discussion, but if it is defaulted to on, then this whole problem of having to train newbies about vacuum should just go away. Matthew
В списке pgsql-hackers по дате отправления: