Skip site navigation (1) Skip section navigation (2)

Re: PITR Backups

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Koichi Suzuki <suzuki(dot)koichi(at)oss(dot)ntt(dot)co(dot)jp>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Toru SHIMOGAKI <shimogaki(dot)toru(at)oss(dot)ntt(dot)co(dot)jp>, Dan Gorman <dgorman(at)hi5(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: PITR Backups
Date: 2007-06-25 14:31:49
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
Koichi Suzuki <suzuki(dot)koichi(at)oss(dot)ntt(dot)co(dot)jp> writes:
> Year, I agree we should carefully follow how Done really did a backup. 
> My point is PostgreSQL may have to extend the file during the hot backup 
> to write to the new block.  It is slightly different from Oracle's case. 
>   Oracle allocates all the database space in advance so that there could 
> be no risk to modify the metadata on the fly.  In our case, because SAN 
> based storage snapshot is device level, not file system level, even a 
> file system does not know that the snapshot is being taken and we might 
> encounter the case where metadata and/or user data are not consistent. 
> Such snapshot (whole filesystem) might be corrupted and cause file 
> system level error.

Surely a hot-backup technique that cannot even produce a consistent
state of filesystem metadata is too broken to be considered a backup
technique at all.

AFAIK, actually workable methods of this type depend on filesystem
cooperation, and are able to produce coherent snapshots of the logical
(not necessarily physical) filesystem content at a specific instant.

			regards, tom lane

In response to


pgsql-performance by date

Next:From: Gregory StarkDate: 2007-06-25 15:00:25
Subject: Re: PITR Backups
Previous:From: Tom LaneDate: 2007-06-25 14:24:30
Subject: Re: Slow indexscan

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group