Re: File system snapshots for multiple file systems

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: tomas(at)tuxteam(dot)de, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, 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-08 16:42:27
Message-ID: 2741.1207672947@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
> What I was complaining/suggesting is that we should make what you did to
> actually work, because it's a lot simpler. And as Jonah pointed out,
> we'd need to inhibit checkpoints between pg_start_backup() and
> pg_stop_backup() to make it work.

I don't think that follows --- what you'd need is to prevent the
checkpoints from removing/recycling old WAL files, but you can still
allow a checkpoint to occur. Any subsequent recovery from the backup
would need to replay from the checkpoint identified by the backup label
file anyway.

Whether it's a good idea or not is a bit debatable though. I'm
concerned about the WAL partition filling up (--> PANIC), especially
if you forget to pg_stop_backup after getting your backup.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2008-04-08 16:59:56 Re: [PATCHES] libpq type system 0.9a
Previous Message Alvaro Herrera 2008-04-08 16:34:13 Re: temp tables should not have pg_shdepend entries