Re: postgre vs MySQL - Mailing list pgsql-general

From Olexandr Melnyk
Subject Re: postgre vs MySQL
Date
Msg-id d5f60f0c0803120859l5a1c961bub628bf415f2f5f73@mail.gmail.com
Whole thread Raw
In response to Re: postgre vs MySQL  (Reece Hart <reece@harts.net>)
List 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); 

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

--  Reece Hart, http://harts.net/reece/, GPG:0x25EC91A0 



--
Sincerely yours,
Olexandr Melnyk
http://omelnyk.net/

pgsql-general by date:

Previous
From: "Dave Page"
Date:
Subject: PostgreSQL user documentation wiki open for business
Next
From: Tom Lane
Date:
Subject: Re: ERROR: text search configuration "pg_catalog.english" does not exist