Re: postgre vs MySQL
| От | Olexandr Melnyk |
|---|---|
| Тема | Re: postgre vs MySQL |
| Дата | |
| Msg-id | d5f60f0c0803120859l5a1c961bub628bf415f2f5f73@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: postgre vs MySQL (Reece Hart <reece@harts.net>) |
| Список | pgsql-general |
You can make a backup in MySQL in several ways:
1) Using mysqldump;
2) Lock tables and copy their files one-by-one (MyISAM-only);
3) Shutdown server and copy all files (can be a slave in a replicated setup);
4) Using InnoDB hot backup (commercial tool);
--
Sincerely yours,
Olexandr Melnyk
http://omelnyk.net/
1) Using mysqldump;
2) Lock tables and copy their files one-by-one (MyISAM-only);
3) Shutdown server and copy all files (can be a slave in a replicated setup);
4) Using InnoDB hot backup (commercial tool);
On 3/12/08, Reece Hart <reece@harts.net> wrote:
On Tue, 2008-03-11 at 06:47 -0700, rrahul wrote:Any major clients of the two.
You can add you own points too.
Perhaps someone can comment on current MySQL backups procedures. I believe that MySQL used to (still does?) require shutdown to be backed up. I don't know whether this was true for all engines or whether it might have been fixed. Having to shutdown a database to make a backup is a non-starter for anything that other than a toy (or read-only) databases.
-Reece
--
Sincerely yours,
Olexandr Melnyk
http://omelnyk.net/
В списке pgsql-general по дате отправления: