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

Re: PITR Backups

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "Dan Gorman" <dgorman(at)hi5(dot)com>
Cc: "Toru SHIMOGAKI" <shimogaki(dot)toru(at)oss(dot)ntt(dot)co(dot)jp>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>,<pgsql-performance(at)postgresql(dot)org>
Subject: Re: PITR Backups
Date: 2007-06-22 11:38:09
Message-ID: 1182512289.9276.220.camel@silverbirch.site (view raw or flat)
Thread:
Lists: pgsql-performance
On Fri, 2007-06-22 at 04:10 -0700, Dan Gorman wrote:
> This snapshot is done at the LUN (filer) level, postgres is un-aware  
> we're creating a backup, so I'm not sure how pg_start_backup() plays  
> into this ...

Postgres *is* completely unaware that you intend to take a backup, that
is *exactly* why you must tell the server you intend to make a backup,
using pg_start_backup() and pg_stop_backup(). That way Postgres will
flush its buffers, so that they are present on storage when you make the
backup.

Is the procedure for Oracle or any other transactional RDBMS any
different? 

-- 
  Simon Riggs             
  EnterpriseDB   http://www.enterprisedb.com



In response to

Responses

pgsql-performance by date

Next:From: Dan GormanDate: 2007-06-22 11:51:19
Subject: Re: PITR Backups
Previous:From: Dan GormanDate: 2007-06-22 11:10:36
Subject: Re: PITR Backups

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