Re: postgre vs MySQL

From: "Olexandr Melnyk" <omelnyk(at)gmail(dot)com>
To: "Reece Hart" <reece(at)harts(dot)net>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: postgre vs MySQL
Date: 2008-03-12 15:59:24
Message-ID: d5f60f0c0803120859l5a1c961bub628bf415f2f5f73@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)harts(dot)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/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-03-12 16:03:02 Re: ERROR: text search configuration "pg_catalog.english" does not exist
Previous Message Dave Page 2008-03-12 15:53:57 PostgreSQL user documentation wiki open for business