| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Pierre Frédéric Caillaud <lists(at)peufeu(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: "Hot standby"? |
| Date: | 2009-08-11 22:04:05 |
| Message-ID: | 4A81EAD5.8010700@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> Incidentally, we billed pg_dump as hot backup at some point.
It *is* "hot backup" as in taken while the database is running and fully
accessible.
> mysql calls "mysqlhotcopy" a script that locks and flushes all tables,
> then makes a copy of the database directory (all queries being locked
> out while this is in progress, of course).
Which is actually 'cold backup'; it's only "hot" compared to earlier
MySQLs where you had to shut the db down. So it's sort of a "lukewarm
backup".
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2009-08-11 22:06:54 | Re: Why is vacuum_freeze_min_age 100m? |
| Previous Message | Alvaro Herrera | 2009-08-11 22:02:45 | Re: Re: pgsql: Ship documentation without intermediate tarballs Documentation |