From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
---|---|
To: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: File system snapshots for multiple file systems |
Date: | 2008-04-07 19:03:41 |
Message-ID: | 36e682920804071203y646cffcq352795e77fbedc50@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Apr 7, 2008 at 2:58 PM, Heikki Linnakangas
<heikki(at)enterprisedb(dot)com> wrote:
> Incidentally, I looked at this stuff just a couple of days ago, and it
> occurred to me that we really should make it easier to take a hot backup
> with that mechanism. We shouldn't require setting up archive_command, and
> WAL archiving, if all you want is to take a backup from a live system. From
> user point of view, it should be a matter of:
>
> 1. call pg_start_backup('foo')
> 2. tar/etc. the whole data directory, except for pg_xlog
> 3. tar pg_xlog
> 4. call pg_stop_backup()
>
> If we just made sure that we don't delete or recycle any WAL files while
> the backup is being taken, that would work, right?
Or checkpoint, yes? I don't see tar backing up large (100+GB)
databases in < 5 minutes.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
499 Thornall Street, 2nd Floor | jonah(dot)harris(at)enterprisedb(dot)com
Edison, NJ 08837 | http://www.enterprisedb.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2008-04-07 19:04:26 | Re: COPY Transform support |
Previous Message | Heikki Linnakangas | 2008-04-07 18:58:34 | Re: File system snapshots for multiple file systems |