From: Simon Riggs <simon@2ndquadrant.com>
To: Dan Gorman <dgorman@hi5.com>
Cc: Toru SHIMOGAKI <shimogaki.toru@oss.ntt.co.jp>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: PITR Backups
Date: Fri, 22 Jun 2007 12:38:09 +0100
Message-ID: <1182512289.9276.220.camel@silverbirch.site> (raw)
In-Reply-To: <31812EEE-22E7-41CD-B70F-CE861681BABC@hi5.com>
References: <7E0807EE-B970-4869-A248-B838E42AD9EE@hi5.com>
<9761.1182472005@sss.pgh.pa.us>
<467B3459.9030808@oss.ntt.co.jp>
<1182509748.9276.178.camel@silverbirch.site>
<31812EEE-22E7-41CD-B70F-CE861681BABC@hi5.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: simon@2ndquadrant.com, dgorman@hi5.com, shimogaki.toru@oss.ntt.co.jp, tgl@sss.pgh.pa.us
Subject: Re: PITR Backups
In-Reply-To: <1182512289.9276.220.camel@silverbirch.site>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox