From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | Arjen van der Meijden <acm(at)tweakers(dot)net> |
Cc: | "'Randal L(dot) Schwartz'" <merlyn(at)stonehenge(dot)com>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: fairly current mysql v postgresql comparison need for |
Date: | 2003-03-24 20:08:42 |
Message-ID: | Pine.LNX.4.33.0303241304390.23928-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 24 Mar 2003, Arjen van der Meijden wrote:
> > [mailto:pgsql-general-owner(at)postgresql(dot)org] Namens scott.marlowe
> > Verzonden: maandag 24 maart 2003 19:26
>
> > Oh, and another thing. How do you do hot backups of a MySQL database
> > running Innodb tables? Better get out the checkbook for some closed
> > source software.
> Please elaborate what you see as a hot backup tool?
For MySQL you need a special tool to backup innodb tables "hot". i.e.
while transactions are running or the database is in use. For Postgresql,
hot backups as well as cold are handled by pg_dump. The elaboration on
the tool needed is here:
http://www.mysql.com/doc/en/Backing_up.html
> Is that, for postgresql, the pg_dump tool? In that case, mysql has the
> same. Mysqldump works fine with innodb-tables as well as for myisam
> tables.
As long as there aren't any transactions pending while you run it. It
does have issues then. The hotbackuptool that MySQL comes with is
explicitly documented by the mysql folks as NOT working for innodb tables.
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Mascari | 2003-03-24 20:26:50 | Re: fairly current mysql v postgresql comparison need for |
Previous Message | Robert Treat | 2003-03-24 20:05:07 | Re: postgresql newsgroups (comp.databases.postgresql.*) |